# Knowledge Graph as context for LLMs: demonstrating decisive RCA and faster production performance

DevFeed: [Knowledge Graph as context for LLMs: demonstrating decisive RCA and faster production performance](<https://devfeed.tech/articles/knowledge-graph-as-context-for-llms-demonstrating-decisive-rca-and-faster-production-performance-8591.md>)

Original publisher: [Read original article](<https://grafana.com/blog/knowledge-graph-as-context-for-llms-demonstrating-decisive-rca-and-faster-production-performance/>)

Author: Sarah Constant

Published: 2026-09-12T11:22:06.456390Z

Content type: article

Language: en

Sources: [Grafana Labs blog on Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Large Language Model](<https://devfeed.tech/topics/llm.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [incident](<https://devfeed.tech/topics/incident.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [observability ai agents](<https://devfeed.tech/topics/observability-ai-agents.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [incident](<https://devfeed.tech/tags/incident.md>), [knowledge-graph](<https://devfeed.tech/tags/knowledge-graph.md>), [llms](<https://devfeed.tech/tags/llms.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>)

## AI overview

The article reports Grafana Labs experiments testing whether providing AI agents with Grafana Cloud's Knowledge Graph improves incident debugging compared with raw telemetry alone. In one incident replayed 16 times per approach, Knowledge Graph context led to the correct root cause 15 times, versus once with raw telemetry. The article also describes challenges including misleading signals, unsupported confident answers, and inconsistent investigations, arguing that well-structured context matters more than context-window size alone.

## Source excerpt

On the product team here at Grafana Labs, we consider AI agents our users, too. That's why we set out to test how well agents can debug incidents across the full stack, and how much better they perform with Grafana Cloud's Knowledge Graph vs. using raw telemetry alone. Our early results are promising. In one real incident we replayed 16 times each way, an agent with Knowledge Graph context found the correct root cause 15 times, compared with just once using raw telemetry alone. Along the way, we also uncovered some of the challenges that still stand in the way of reliable AI-assisted debugging, from chasing the wrong signals to confidently making things up and producing inconsistent answers. We're still early, but our findings point to an important idea. The industry's shorthand right now is that a bigger context window will lead to better outputs. Our findings suggest it's not just about more context; it's about structuring your data well enough to serve the right context. Here's a look at what we've learned so far, as we continue to experiment out in the open and bring you along, the Grafana Labs way. Giving an agent access to telemetry is just the beginning Give a current-generation model like Opus 4.8 access to your raw telemetry during a live incident, and it genuinely starts to figure things out: querying metrics and logs, forming a hypothesis, and checking it. We have watched it work on our own incidents, and it does it affordably. But if you run software at scale, where uptime is business-critical and large teams share the responsibility, a better model alone doesn't get you all the way there for debugging. From analyzing how LLMs do root-cause analysis on our own infrastructure, and from speaking to our customers, we've uncovered three problems that get in the way: The further the cause is from the alert, the more likely the model is to get it wrong. An agent may confidently make things up when it doesn't have the evidence it needs. The same investigation c