Bug Description
Assume a COS Lite is storing telemetry for another model and that Grafana Agent machine 2/stable is the agent collecting telemetry and pushing it into COS Lite. If that model is destroyed before the relation between Grafana Agent and Prometheus is removed, then the alert rules forward through GA to Prom remains on Prom's disk. As a result, since the model is destroyed, alerts such as HostMetricsMissing keep getting triggered.
To Reproduce
- Deploy COS Lite.
- Deploy a machine model with GA 2/stable in it and relate GA to Prom over a CMR.
- Destroy the model.
- Alerts such as HostMetricsMissing for the Grafana Agent that was destroyed will remain on disk in Prometheus.
Environment
TBC.
Relevant log output
Additional context
No response
Bug Description
Assume a COS Lite is storing telemetry for another model and that Grafana Agent machine 2/stable is the agent collecting telemetry and pushing it into COS Lite. If that model is destroyed before the relation between Grafana Agent and Prometheus is removed, then the alert rules forward through GA to Prom remains on Prom's disk. As a result, since the model is destroyed, alerts such as HostMetricsMissing keep getting triggered.
To Reproduce
Environment
TBC.
Relevant log output
Additional context
No response