ServiceLatencyP95High

# ServiceLatencyP95High

Larkspur Grocers is fictional. This note explains the alert. It is not an incident report. It does not record a page, a customer impact, or an MTTR.

## Signal

- Severity: `warning`
- Team: `platform`
- Pending duration (`for`): 10m

```promql
max by (service) (service_route:http_request_duration_seconds:p95_5m)
> on (service)
service:http_latency_p95_threshold_seconds:constant
```

## What the condition means

The worst route p95 is above the per-service constant recorded in service:http_latency_p95_threshold_seconds:constant. Thresholds are not copied into the alert.

## What an on-call would check

1. Read the expression above and the recording rules it uses.
2. Compare it with the promtool unit tests in `tests/rules/`. Every alert except Watchdog has a firing case and a non-firing case.
3. The annotation `runbook_url` is `https://runbooks.larkspur.example/ServiceLatencyP95High`. That host is a placeholder. This file is the copy in the repo.
4. This stack does not page anyone. Receivers use `*_file` credential paths and `example.invalid`.

返回告警目录