A dashboard exists

The service has a dashboard showing its traffic, errors and latency at a glance.

LowChecked automatically

Applies to:
Every service
Rule id:
observability.dashboards-defined

Why it matters

During an incident the first question is "what changed, and when?". A dashboard that already exists answers it in seconds. Building one while the service is down does not.

How to apply it

  • Start with rate, errors and duration for the service as a whole, then per endpoint or consumer.
  • Add the saturation signals that matter for this service: queue depth, connection pool use, database latency.
  • Mark deploys on the graphs.
  • Dashboards are listed in the Dashboards section of the MICROSERVICE.md.

Example

"orders: overview" with request rate, error rate, p50/p99 latency, consumer lag on orders.order-placed and deploy markers.

References

Checklists with this rule

Related agent skill: observability

  • Alerts are defined

    The service has alerts on symptoms its users would notice, each one actionable.

    HighChecked automatically

  • An availability objective is set

    The service has a stated availability target, so "is it reliable enough?" has an answer.

    HighChecked automatically

  • Consumer lag is monitored

    The service measures how far behind its consumers are and alerts before the delay hurts users.

    HighChecked by hand

  • A p99 latency target is set

    The service states how fast its slowest normal requests should be.

    MediumChecked automatically

  • Distributed tracing is on

    Requests carry a trace context through the service, so one request can be followed across services.

    MediumChecked automatically