Telemetry-driven development: How to gain confidence in your coding agents' behavior with gcx and Grafana MCP

elseif has not written about this yet · Grafana describes it this way

You’re about to click "Merge" on a PR, but you feel more anxious about it than you used to. Why? You did everything properly, by today’s standards: You used Claude to create a plan, giving it context from a GitHub issue and some Slack threads. You iterated on it a few times; Claude says it has the full picture. It feels ready, so you get Claude Code to implement the plan. You run a review agent against the diff and get some of those comments addressed. You start reading the diff, but it's long. You try to build a mental model of the changes and how they fit in with the system. A few more cycles of feedback and questions with Claude, and things feel … OK. So you create a PR. The AI review comes back all clean, and you get a "LGTM - ship it" from your teammate.So why do you still feel uneasy? Well, it's probably because you don’t know the code diff the same way you would if you’d typed it all out yourself. Before AI, we built our mental models of system changes as we wrote the changes, and we relied on those models to ensure the code we deployed behaved as expected. However, that all happens less often when AI is the one making the changes. Coding agents have increased the speed of d