Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide & Define Service Metrics #72

Open
reid-spencer opened this issue Feb 13, 2024 · 0 comments
Open

Decide & Define Service Metrics #72

reid-spencer opened this issue Feb 13, 2024 · 0 comments

Comments

@reid-spencer
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant