-
Notifications
You must be signed in to change notification settings - Fork 11
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.
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
decision: up-alert-rules #224
base: main
Are you sure you want to change the base?
Conversation
Metrics not received from host '{{ $labels.instance }}'. This is likely due to an issue with an itermediate metrics agent. | ||
``` | ||
|
||
## Rationale |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the rationale we should explicitly address:
- Why per charm and not just once in prometheus / mimir?
- Should
up
alert be in prom andabsent
per charm? - How should aggregators such as gagent go about this. See also
up < 1 or absent(up)
in feat(alerting): detect flapping alerts grafana-agent-operator#148. - Scrape failed is different from host didn't send data.
- Missing of scrape targets vs missing of self, see https://github.com/canonical/prometheus-k8s-operator/blob/main/src/prometheus_alert_rules/prometheus_missing.rule
Hey @dstathis |
- name: HostHealth | ||
rules: | ||
- alert: HostUnreachable | ||
expr: up < 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this not a duplicate of the HostDown expression?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope. Difference is the "for" field and the severity
up-alert-rules ADR