fixup! BB-311 add oplog populator alerts

scality · Jan 6, 2023 · 3620ec9 · 3620ec9
1 parent cced49f
commit 3620ec9
Showing 1 changed file with 0 additions and 28 deletions.
diff --git a/monitoring/oplog-populator/alerts.test.yaml b/monitoring/oplog-populator/alerts.test.yaml
@@ -50,31 +50,3 @@ tests:
               zenko_service: backbeat-oplog-populator
               description: "Oplog populator failed to configure connector"
               summary: "Oplog populator couldn't update kafka connect connector"
-
-  - name: Metastore Change Stream Lag
-    interval: 1m
-    input_series:
-      - series: oplog_populator_acknowledgement_lag_sec_bucket{job="artesca-data-backbeat-oplog-populator-headless",namespace="zenko", le="1"}
-        values: 50+10x4 100+10x4 150+10x6
-      - series: oplog_populator_acknowledgement_lag_sec_bucket{job="artesca-data-backbeat-oplog-populator-headless",namespace="zenko", le="10"}
-        values: 100+100x4 1500+1000x4 11500+10000x6
-      - series: oplog_populator_acknowledgement_lag_sec_count{job="artesca-data-backbeat-oplog-populator-headless",namespace="zenko"}
-        values: 100+100x16
-      - series: oplog_populator_acknowledgement_lag_sec_sum{job="artesca-data-backbeat-oplog-populator-headless",namespace="zenko"}
-        values: 590 6230 77940
-    alert_rule_test:
-      - alertname: OplogPopulatorMetastoreChangeStreamLagThreshold
-        eval_time: 5m
-        exp_alerts: []
-      - alertname: OplogPopulatorMetastoreChangeStreamLagThreshold
-        eval_time: 11m
-        exp_alerts: []
-      - alertname: OplogPopulatorMetastoreChangeStreamLagThreshold
-        eval_time: 16m
-        exp_alerts:
-          - exp_labels:
-              severity: critical
-            exp_annotations:
-              zenko_service: backbeat-oplog-populator
-              description: "Oplog populator metastore change stream lag is too big"
-              summary: "Oplog populator configuration lag is above threshold"