Skip to content

Commit a710097

Browse files
committed
chore(webapp): drop an alert rule whose metric has no producer
The rule watched a counter that no code emits, so it could never fire. A rule pinned at empty is indistinguishable from a healthy one that found nothing.
1 parent ad9c11d commit a710097

1 file changed

Lines changed: 0 additions & 13 deletions

File tree

docker/config/alerts/snapshot-store.yml

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -22,19 +22,6 @@ groups:
2222
than task failure. Turn the snapshotStoreMode flag down to off, which takes effect
2323
without a deploy, then investigate the Redis endpoint.
2424
25-
- alert: SnapshotStoreQuarantineFailing
26-
# A quarantine that cannot be applied leaves a run's Redis head permanently behind Postgres.
27-
expr: sum(rate(run_engine_snapshot_store_quarantine_total{outcome="failed"}[10m])) > 0
28-
for: 15m
29-
labels:
30-
severity: page
31-
annotations:
32-
summary: "Execution-snapshot keyspaces cannot be quarantined"
33-
description: >-
34-
A divergent Redis head could not be dropped, so that run keeps a head that is behind
35-
Postgres. Do not move the dial to redis-read while this is firing: a frozen head is
36-
served as if it were current.
37-
3825
- alert: SnapshotStoreSweepNotCompleting
3926
# The sweep is the only reaper for orphaned keyspaces. Its absence is silent by nature.
4027
expr: sum(increase(run_engine_snapshot_store_sweep_pass_total{outcome="completed"}[24h])) == 0

0 commit comments

Comments
 (0)