NewsCloud & DevOpsDeveloper Tools

Grafana 13.2: AI Alerting, Database Observability Now

Grafana 13.2 dashboard showing alert rules, database observability, and AI assistant features
Grafana 13.2 ships a rebuilt alert rule list, natural-language database observability, and alert enrichment GA.

Grafana 13.2 shipped August 18 with three changes that affect the pre-incident workflow: a fully rebuilt alert rule list, natural-language database observability through the AI assistant, and alert enrichment now GA in Grafana Cloud. None of these are minor polish. Here is what changed and what to configure before your next outage.

The Alert Rule List Is a Different Page Now

The old alert rule page was widely disliked. It loaded everything at once, filtered slowly, and became unusable at scale—teams managing tens of thousands of rules were dealing with several-second lag on every interaction. Grafana rebuilt it from scratch.

The new page has two views. Grouped arranges rules by namespace, which is how most teams think about alert ownership. List shows every rule across all groups in a flat, searchable table backed by a new paginated API—search and filter are now instant regardless of how many rules you have.

There is also a new inline Alerts tab on every panel. Open any panel, go to the Alerts tab, and you see every alert rule tied to that panel with color-coded status. No more cross-referencing alert lists with dashboard panels manually.

If you manage alerts with automation or bookmark deep links into the alert list, check those paths after upgrading. The Grafana alerting announcement covers what moved.

Ask Your Database What It Is Doing

Database Observability has been generally available since April 2026, but the 13.2 timeframe brought the integration that makes it actually convenient: you can now ask Grafana Assistant natural-language questions against your live MySQL and PostgreSQL telemetry.

Ask “What are my worst-performing queries?” and you get the top 10 ranked by latency across both databases, with calls, errors, latency, and rows examined per query. Click for an AI-generated diagnosis and you get a fix recommendation grounded in your live Prometheus and Loki data—not a generic suggestion. The recommendations are dialect-specific: a slow PostgreSQL query might get a partial index suggestion; the same pattern in MySQL gets a prefix index with an appropriate key length.

This requires Grafana Cloud with the Database Observability add-on enabled. If you are already running Database Observability, the AI layer is on by default in the Assistant. If not, the agent-based install takes about fifteen minutes and the AI integration is available immediately after.

Alert Enrichment Is GA and Most Teams Will Skip It

Alert enrichment reached general availability in Grafana Cloud on August 24. It does one thing: adds context to alert notifications before they reach the on-call developer. Not after the developer opens Grafana. Before.

Each enrichment runs the moment an alert fires and attaches its output to the notification. That context travels with the alert through whatever contact point you use—PagerDuty, Slack, a webhook. The developer gets the notification and already has context to start diagnosing.

There are three enrichment types. Data Source Query runs a Grafana query and appends the result. LLM explanation generates a plain-language description of the alert condition. Investigation link starts a Grafana Assistant investigation and adds the link to the payload.

Setup is at Alerting > Settings > Alert Enrichment. You need the alert.enrichments:write permission. The minimum useful configuration is one Data Source Query enrichment on your highest-traffic alert rule—something like “top error rate services in the last five minutes.” That single enrichment pays for the setup time the first time it fires during an incident at 3 AM.

Git Sync Gets Enterprise and GitLab Support

Two Git Sync changes land in 13.2 that matter to enterprise teams. GitHub Enterprise (both Server and Cloud) is now supported, so organizations on self-hosted GitHub can use Git Sync for dashboard-as-code. GitLab and Bitbucket webhooks are now available, enabling real-time push-triggered sync instead of scheduled polling. Commit authoring defaults to the signed-in Grafana user’s name and email, which makes the diff history usable.

Before You Upgrade

One plugin deprecation to check: config.apps and config.panels from @grafana/runtime are deprecated and removed in 13.2. If you maintain custom Grafana plugins, search your plugin code for those properties before pushing the upgrade button. The official Grafana 13.2 upgrade guide lists the full set of changes.

The full 13.2 feature list is in the release announcement. Alert Enrichment is the feature most teams will configure sometime in the next incident’s post-mortem, after discovering they should have set it up beforehand. Set it up now.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

    Your email address will not be published. Required fields are marked *

    More in:News