The Cost of Context-Sharing in Incident Response
When a critical alert fires, every second counts. Engineers typically turn to their AI assistant for help, asking something like, “Why is the checkout service slow?” But without pre-loaded context, the assistant must first discover the environment: which data sources are connected, what services are running, how they interact, which metrics and labels are relevant, and where logs reside. This initial discovery phase can consume precious minutes—time that should be spent on actual troubleshooting. Each new conversation essentially starts from scratch, forcing users to re-share details about their infrastructure.
Grafana Assistant’s Persistent Knowledge Base
Grafana Assistant, an agentic observability assistant, eliminates this repetitive context-sharing. Instead of learning on demand, it proactively studies your infrastructure and builds a persistent knowledge base before you ever ask a question. By the time you need answers, it already knows what services are running, how they are connected, and where to look for relevant data. This preloaded context allows you to dive straight into troubleshooting, saving valuable time during incidents.
How the Knowledge Base is Built
Assistant works in the background with zero configuration. A swarm of AI agents continuously performs the following tasks:
- Data source discovery: It identifies all connected Prometheus, Loki, and Tempo data sources in your Grafana Cloud stack.
- Metrics scans: Agents query Prometheus sources in parallel to discover services, deployments, and infrastructure components.
- Enrichments via logs and traces: Loki and Tempo data are correlated with metrics, adding context about log formats, trace structures, and service dependencies.
- Structured knowledge generation: For each discovered service group, agents produce documentation covering five areas: what the service is, its key metrics and labels, how it’s deployed, its dependencies, and its typical behavior.
Think of it as giving the assistant a map of your world before it starts answering questions. This map is continuously updated as infrastructure changes.
Benefits for Incident Response
With a pre-built knowledge base, conversations become faster and more accurate. When you ask about a service, the assistant knows instantly that your payment system talks to three downstream services, that its latency metrics live in a specific Prometheus source, and that its logs are structured JSON in Loki. No fumbling through data source discovery.
This speed is especially critical during incidents. Even experienced engineers can shave minutes off response time when context is preloaded. But the functionality shines for teams where not everyone has the full infrastructure picture. A developer investigating an issue in their own service can ask about upstream dependencies and get accurate answers, even if they have never looked at those systems before.
Conclusion
Grafana Assistant’s proactive approach to infrastructure awareness transforms incident response. By eliminating the need for context-sharing, it helps teams focus on solving problems rather than discovering their environment. This persistent knowledge base ensures that every conversation—from troubleshooting to routine queries—starts with the information you need, right when you need it.