Issues
- Components monitoring and alertingPMM-12752Resolved issue: PMM-12752
- [BE] Backup metrics and alert rule templatePMM-12384Resolved issue: PMM-12384Artem Gavrilov
- Make `Fired Alerts` and `Templates` tabs visible for users with the Viewer rolePMM-12242Resolved issue: PMM-12242Matej Kubinec
- Alerting: Allow to create template copyPMM-11791
- Update grafana.ini domain parameter on PMM Public Address setting changePMM-11770Resolved issue: PMM-11770Michael Okoko
- Autorefresh page with firing alertsPMM-11230Resolved issue: PMM-11230Fábio Da Silva
- Let user upload multiple alert rule templates using CreateTemplate API endpoint in Alerting.PMM-11206Resolved issue: PMM-11206Artem Gavrilov
- Remove Integrated Alerting APIs, models and code.PMM-11079Resolved issue: PMM-11079Artem Gavrilov
- Deprecate Integrated Alerting APIPMM-11078Resolved issue: PMM-11078Michael Okoko
- Fired alerts has wrong summaryPMM-10810Resolved issue: PMM-10810Artem Gavrilov
- Create Grafana alert rule with Percona template.PMM-10452Resolved issue: PMM-10452
- Investigate Grafana 8 alerting featuresPMM-9313Resolved issue: PMM-9313Artem Gavrilov
- Alerting: Imporve templates parsing error messagesPMM-9023
- Integrated alerting Improvements( Add search option for alert rules and Modified Username display)PMM-8228Resolved issue: PMM-8228
- Add validation to Alert Rules Templates which were created from YAML filesPMM-7209Artem Gavrilov
15 of 15
There should be a method to check the health of the individual components within PMM. The goal is to have a mechanism that alerts when a component fails. This includes PostgreSQL, Clickhouse, VictoriaMetrics, Grafana, etc. An alert identifying the issue would also be useful so the customer is aware. This may need to be done via HA since a PMM component being down may mean alerting may not be feasible.