From the experiment

Do coding agents recommend Grafana?

Grafana was chosen in 15% of 593 judged observability sessions, ranking second. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.

Published October 14, 2026 Read as Markdown

Grafana was chosen in 15% of 593 judged observability sessions, ranking second. It was also raised as a candidate in 316 further sessions without being chosen.

This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in observability inside a realistic codebase. Not what a chat assistant says about Grafana. What an agent actually installed.

The numbers

CategoryObservability
Sessions in the category593
Sessions where Grafana was chosen86
Install share15%
Rank in category2 of 21
Codebases it won in6
Raised as a candidate, not chosen316
Chosen when considered21%
Sitegrafana.com

By agent

Claude Code, Codex, Cursor and Muse Code land within 14 points of each other on Grafana, which is closer than most products in this experiment manage. Grok Build CLI ran fewer than 30 sessions here, too few to compare.

AgentSessionsChose GrafanaShare
Claude Code1503725%
Codex1801911%
Cursor1501611%
Grok Build CLI24313%
Muse Code891112%

By who was asking

Grafana does much better with one kind of buyer than another. It won 60% of sessions asked as enterprise team and 0% of those asked as junior developer.

Who is askingSessionsChose GrafanaShare
Vibe coder2000%
Junior developer2000%
Senior engineer4935010%
Enterprise team603660%

What Grafana was up against

The full ranking in observability, from the same sessions:

#ProductRuns wonShare
1Sentry21136%
2Grafana (this page)8615%
3Amazon CloudWatch5910%
4Built in-house (no product adopted)417%
5Better Stack264%
6Checkly254%
7New Relic244%
8Datadog244%

What this means

A solid second or third position in a category means the agent is genuinely choosing rather than reaching automatically. That is a winnable position, because the inputs it uses can be changed.

The fastest gains are usually in the sessions that were nearly won: read them, find the step where the agent moved on, and fix that step.

Where these numbers come from

The 593 sessions in observability are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.

Every observability run can be replayed on the board.

If you work on Grafana: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.

<!-- generated by scripts/write-data-pages.mjs -->

Common questions

Do coding agents recommend Grafana?

Yes. Grafana was chosen in 86 of the 593 judged sessions in observability, a 15% install share, ranking second in its category.

Does Claude Code recommend Grafana?

In 37 of the 150 sessions in observability run with Claude Code, which is 25%.

Do different coding agents treat Grafana differently?

Yes, and by a wide margin. Claude Code chose it in 25% of its runs and Codex in 11%.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 110 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.

How often is Grafana considered but not chosen?

It was raised as a candidate in 316 sessions without being chosen, and chosen in 86. That is a 21% conversion from considered to chosen.

Where this comes from

Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages