Stop switching tools to find answers: Grafana Assistant now works across 30+ data sources

When you’re the on-call engineer and something breaks, you can quickly find yourself deep in a series of tools you don’t regularly use—switching tabs, copying query results, and manually stitching together a picture of what’s happening and why.

People are increasingly turning to AI to get around this, but the results can be a mixed bag.

For example, many of today’s observability, data warehousing, or project management tools come equipped with powerful AI assistants that can help you get answers quicker. But those assistants can only see the data they were built on top of. Alternatively, you could extend the AIs through MCPs or built-in integrations, but those connections don’t configure or maintain themselves. 

As a result, AI that is designed to reduce the cognitive load of juggling multiple tools ends up adding another silo to an already fragmented stack. 

We think there’s a better way.

At Grafana Labs, we’ve always had a “big tent” philosophy. You don’t have to migrate your data or standardize on a single vendor. Grafana connects to the tools and data sources your teams already trust and surfaces everything together. And now we’re extending that same promise to AI with Grafana Assistant. 

Extending Assistant to more than 30 data sources

Getting an answer usually means opening several tools and piecing the story together yourself. Assistant collapses that into one step: ask it a question, and it searches across whatever you’re already using to find the answer, rather than you doing the searching.

Assistant is built on Grafana’s native data source architecture. Instead of asking you to bring your data to it, it comes to your data. It currently supports more than 30 data sources, so if your teams are already querying those sources in Grafana (either through Grafana Cloud or Grafana 13), Assistant can now reason over, query, and visualize from them, too.

Observability platforms you already run

Similar Posts

Leave a Reply