Do coding agents recommend Amazon CloudWatch?
Amazon CloudWatch was chosen in 10% of 593 judged observability sessions, ranking third. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Amazon CloudWatch was chosen in 10% of 593 judged observability sessions, ranking third. It was also raised as a candidate in 2 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 Amazon CloudWatch. What an agent actually installed.
The numbers
| Category | Observability |
| Sessions in the category | 593 |
| Sessions where Amazon CloudWatch was chosen | 59 |
| Install share | 10% |
| Rank in category | 3 of 21 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 2 |
| Chosen when considered | 97% |
| Site | aws.amazon.com |
By agent
Claude Code, Codex, Cursor and Muse Code agree closely on Amazon CloudWatch, choosing it at rates within 4 points of each other. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Amazon CloudWatch | Share |
|---|---|---|---|
| Claude Code | 150 | 11 | 7% |
| Codex | 180 | 20 | 11% |
| Cursor | 150 | 15 | 10% |
| Grok Build CLI | 24 | 5 | 21% |
| Muse Code | 89 | 8 | 9% |
By who was asking
Amazon CloudWatch performs similarly across the four kinds of buyer, from 0% to 12%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose Amazon CloudWatch | Share |
|---|---|---|---|
| Vibe coder | 20 | 0 | 0% |
| Junior developer | 20 | 0 | 0% |
| Senior engineer | 493 | 59 | 12% |
| Enterprise team | 60 | 0 | 0% |
What Amazon CloudWatch was up against
The full ranking in observability, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Sentry | 211 | 36% |
| 2 | Grafana | 86 | 15% |
| 3 | Amazon CloudWatch (this page) | 59 | 10% |
| 4 | Built in-house (no product adopted) | 41 | 7% |
| 5 | Better Stack | 26 | 4% |
| 6 | Checkly | 25 | 4% |
| 7 | New Relic | 24 | 4% |
| 8 | Datadog | 24 | 4% |
What this means
Agents almost never raise Amazon CloudWatch without choosing it: 2 sessions raised against 59 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
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 Amazon CloudWatch: 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 Amazon CloudWatch?
Yes. Amazon CloudWatch was chosen in 59 of the 593 judged sessions in observability, a 10% install share, ranking third in its category.
Does Claude Code recommend Amazon CloudWatch?
In 11 of the 150 sessions in observability run with Claude Code, which is 7%.
Do different coding agents treat Amazon CloudWatch differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 7% and 11% of their runs.
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 Amazon CloudWatch considered but not chosen?
It was raised as a candidate in 2 sessions without being chosen, and chosen in 59. That is a 97% 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.