Skip to content

Fix alert_rules description #217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ioanalazea wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix alert_rules description #217

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 4 additions & 16 deletions charmcraft.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,22 +111,10 @@ config:
with the charm. Empty string (default) keeps the shipped rules.

Use this to customise severities, thresholds and `for:` durations, or to add or remove
alerts. The value must be a valid Prometheus rules file with a top-level `groups` key.
For example:

groups:
- name: NovaCompute
rules:
- alert: NovaComputeDown
expr: openstack_nova_agent_state{adminState="enabled"} == 0
for: 2m
labels:
severity: critical
annotations:
summary: Nova Compute Agent Down

Warning: Changing this option reloads the alert rules in Prometheus.
Any currently firing alerts that are removed by the new rules will be canceled
alerts. The value must be a valid Prometheus rules file.

Warning: Changing this option reloads the alert rules in Prometheus.
Any currently firing alerts that are removed by the new rules will be canceled
and reported to Alert Manager as resolved.

charm-libs:
Expand Down
Loading