You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The below example shows that prometheus-alert-overrider can't properly override a query with multiple metrics combined with OR.
The first metric is overridden fine, but the second one is not:
❯ cat bug-multiple-metrics-in-query.rules
groups:
- name: example
rules:
- alert: test
expr: 'probe_http_status_code <= 199 or probe_http_status_code >= 400'
- alert: test_override
override: ["test"]
expr: 'probe_http_status_code{instance="https://example.org"} <= 199 or probe_http_status_code{instance="https://example.org"} >= 400'
❯ prometheus_alert_overrider bug-multiple-metrics-in-query.rules
groups:
- name: example
rules:
- alert: test
expr: probe_http_status_code{instance!="https://example.org" <= 199 or probe_http_status_codeinstance="https://example.org"}
<= 199 or probe_http_status_code >= 400
- alert: test_override
expr: probe_http_status_code{instance="https://example.org"} <= 199 or probe_http_status_code{instance="https://example.org"}
>= 400
The text was updated successfully, but these errors were encountered:
The below example shows that prometheus-alert-overrider can't properly override a query with multiple metrics combined with OR.
The first metric is overridden fine, but the second one is not:
The text was updated successfully, but these errors were encountered: