You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before coding, let’s decide and define what metrics would be useful to both InfraSight and our application for observability purposes. The kinds of metrics supported are documented here: Metrics
We should consider tracking various rates (widgets per second) with Histogram metrics but only for things related to the business, like the number of orders processed per unit of time, the size of the input queues (mailbox size for actors, pending messages in Kafka, backlogged messages in an Akka stream, etc.).
The result should have at least one of each kind of metric (just for completeness testing) but mostly be Histograms.
The text was updated successfully, but these errors were encountered:
Before coding, let’s decide and define what metrics would be useful to both InfraSight and our application for observability purposes. The kinds of metrics supported are documented here: Metrics
We should consider tracking various rates (widgets per second) with Histogram metrics but only for things related to the business, like the number of orders processed per unit of time, the size of the input queues (mailbox size for actors, pending messages in Kafka, backlogged messages in an Akka stream, etc.).
The result should have at least one of each kind of metric (just for completeness testing) but mostly be Histograms.
The text was updated successfully, but these errors were encountered: