Orders API latency p95 above 2s
Priority high · orders · assignee Priya Sharma · prod
1. Telemetry is absent for the orders service in the incident window. i. Prometheus returns zero series for up{service=~"orders|orders.*"}, so service availability cannot be confirmed [E1]. ii. Loki returns zero log streams for orders/* labels, so error, exception, crash, and panic signals cannot be evaluated [E2]. iii. No matching Prometheus alerting rules or active alerts exist for this incident context [E3]. 2. The incident title reports orders API p95 latency above 2s, but no metric, log, or rule evidence is available to verify which component, deployment, or dependency is the source. 3. Given the complete absence of observability data, the immediate actionable finding is an evidence gap or connector/configuration issue: Prometheus/Loki query selectors, namespaces, or endpoints may be misconfigured, unavailable, or returning no matching streams. Prior postmortems for checkout and payment are low-similarity and do not inform this incident.
Actions
Ask about this incident
Chat with the agent in the context of this incident — RCA, evidence, and next actions.
Incident graphs
On-call
Configure PagerDuty or Opsgenie credentials to show on-call.