No monitoring for process and port
Bug #1870472 reported by
Xav Paice
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Prometheus Alertmanager Charm |
Fix Released
|
High
|
Xav Paice | ||
| Prometheus2 charm |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Although we can relate NRPE to the charm, we do not get any monitoring to ensure that the actual Prometheus and/or alertmanager services are alive, and listening on the correct port. This should be added to the nrpe relation.
Related branches
~xavpaice/charm-prometheus-alertmanager:add_nrpe_check
Merged
into
~prometheus-charmers/charm-prometheus-alertmanager:master
at
revision d50686a8be6aa804848dd18a05f409ad5fa7b54c
- Alvaro Uria (community): Approve
- Wouter van Bommel (community): Approve
-
Diff: 136 lines (+64/-1)5 files modifiedconfig.yaml (+14/-0)
layer.yaml (+5/-1)
metadata.yaml (+3/-0)
reactive/alertmanager.py (+19/-0)
unit_tests/test_reactive_alertmanager.py (+23/-0)
Revision history for this message
| Xav Paice (xavpaice) wrote | #1 |
| Changed in charm-prometheus-alertmanager: | |
| assignee: | nobody → Xav Paice (xavpaice) |
| Changed in charm-prometheus2: | |
| status: | New → Invalid |
| Changed in charm-prometheus-alertmanager: | |
| importance: | Undecided → High |
| status: | New → In Progress |
| Changed in charm-prometheus-alertmanager: | |
| status: | In Progress → Fix Released |
| milestone: | none → 20.05 |
To post a comment you must log in.
The Prometheus2 charm does include a check for the Prometheus http port, which is adequate to let folks know if there's a problem with the process (arguably better than just monitoring the presence of the process). I'll mark this invalid for Prometheus2.