Skip to content
This repository was archived by the owner on Feb 20, 2026. It is now read-only.
This repository was archived by the owner on Feb 20, 2026. It is now read-only.

Decide & Define Service Metrics #72

@reid-spencer

Description

@reid-spencer

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions