openstack/sunbeam-charms
Code Issues Proposed changes

Disconsider uuid for cinder alert rules

Browse Source 
The openstack exporter generates a new uuid for each scrape so
the alert is almost always pending because the changes on this
field.

The new rule do not consider the uuid, so the alerts can trigger
after 5 minutes

[0] https://github.com/openstack-exporter/openstack-exporter/pull/116

Change-Id: I4f60169cd558705544325e9a910857414402e82b
This commit is contained in:
Gabriel Cocenza 2024-09-02 17:25:00 -03:00
parent d6619680e1
commit bad692cdce
No known key found for this signature in database
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
charms/openstack-exporter-k8s/src/prometheus_alert_rules/cinder_rules.yaml
View File

@ -2,7 +2,7 @@ groups:
- name: Cinder
rules:
- alert: CinderStateWarning
expr: openstack_cinder_agent_state{adminState="disabled"}
expr: count without (uuid) (openstack_cinder_agent_state{adminState="disabled"}) > 0
for: 5m
labels:
severity: warning
@ -13,7 +13,7 @@ groups:
LABELS = {{ $labels }}
- alert: CinderStateCritical
expr: openstack_cinder_agent_state{adminState="enabled"} == 0
expr: count without (uuid) (openstack_cinder_agent_state{adminState="enabled"} == 0) > 0
for: 5m
labels:
severity: critical