clearspace

:red_circle: HIGH SEV · API Latency Critical
:fire: [TEST - IGNORE] ozone-api p95 latency alert - escalation test in progress
        &lt;|:chart_with_upwards_trend: graph&gt; · &lt;|:bar_chart: service dashboard&gt; · <https://clearspace.grafana.net/alerting/grafana/bfvp5cmujw8w0d/view?orgId=1|:rotating_light: alarm definition> · <https://clearspace.grafana.net/alerting/silence/new?alertmanager=grafana&amp;matcher=__alert_rule_uid__%3Dbfvp5cmujw8w0d&amp;matcher=environment%3Dproduction&amp;matcher=service%3Dapi&amp;matcher=severity%3Dcritical&amp;orgId=1|:no_bell: silence>

_THIS IS A DELIBERATE TEST OF THE ESCALATION PATH. Nothing is wrong with ozone-api.

The threshold has been temporarily lowered from 2000ms to 5ms and the pending period from 10m to 1m so the rule trips against the normal ~17ms baseline. It is expected to fire and to reach both Slack (#alarms-prod) and Linear On-Call (Prod).

RESTORE TO: threshold gt 2000, for 10m, and the original summary/description.

Original summary: 'ozone-api p95 latency above 2s - effectively unusable'_
Grafana vmain-281d1d0