What's new from Grafana Labs
Legacy Alertmanager configuration API endpoints changed
In Grafana v12.0, we deprecated several Alertmanager configuration API endpoints that rely on legacy single-tenant Alertmanager configuration semantics. In Grafana v13.0 we are removing or restricting access to them:
DELETE /api/alertmanager/grafana/config/api/v1/alertsis removed entirely.GET /api/alertmanager/grafana/config/api/v1/alertsis now restricted to admin users. AWarning: 299response header is included to help identify any remaining automated consumers. The endpoint will be fully removed in a future release.GET /api/alertmanager/grafana/config/historyis now restricted to admin users. The endpoint will be fully removed in a future release.POST /api/alertmanager/grafana/config/history/{id}/_activateis now restricted to admin users. The endpoint will be fully removed in a future release.POST /api/alertmanager/grafana/config/api/v1/receivers/testis removed entirely.
You are affected if
You use any of the following endpoints directly, for example in automation scripts or custom tooling:
DELETE /api/alertmanager/grafana/config/api/v1/alertsGET /api/alertmanager/grafana/config/api/v1/alertsGET /api/alertmanager/grafana/config/historyPOST /api/alertmanager/grafana/config/history/{id}/_activatePOST /api/alertmanager/grafana/config/api/v1/receivers/test
Migration
Use the Kubernetes-style resource APIs under notifications.alerting.grafana.app/v1beta1:
Related What's new posts