The inside scoop on alerting changes in Kubernetes Monitoring

Kubernetes Monitoring in Grafana Cloud now uses Grafana-managed alerts as the primary alerting system, moving away from data source-managed alerts handled by the Prometheus-compatible backend. This shift means that alert rules, initially preconfigured for monitoring issues like CPU throttling and node failures, are now evaluated and routed through Grafana Cloud's built-in alerting engine, which offers advanced features such as multi-data-source rules and RBAC. Users who reinstall the Kubernetes Monitoring app may experience changes in how alerts are managed, potentially affecting notification delivery due to the separate contact points and notification policies of the two alerting systems. To ensure a smooth transition, it is recommended to use the Update button for app upgrades and reconfigure notification routing in Grafana's Alertmanager if necessary. The import tool for migrating data source-managed rules to Grafana-managed ones does not apply to rules created by apps like Kubernetes Monitoring, requiring manual reconfiguration. Future setups in Grafana Cloud will not support data source-managed alerts, emphasizing the need to adapt to the Grafana-managed alerting platform.