# Do coding agents recommend Amazon CloudWatch? > Amazon CloudWatch was chosen in 8% of 360 judged observability sessions, ranking third. Measured with Claude Code, Codex and Cursor. Source: https://armature.tech/library/do-coding-agents-recommend-amazon-cloudwatch Published: 2026-09-03 Publisher: Armature, Inc. (https://armature.tech) --- > Amazon CloudWatch was chosen in 8% of 360 judged observability sessions, ranking third. It was also raised as a candidate in 3 further sessions without being chosen. This page reports what happened when Claude Code, Codex and Cursor 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 | 360 | | Sessions where Amazon CloudWatch was chosen | 30 | | Install share | 8% | | Rank in category | 3 of 16 | | Codebases it won in | 2 | | Raised as a candidate, not chosen | 3 | | Chosen when considered | 91% | | Site | aws.amazon.com | ## By agent The three agents land within 8 points of each other on Amazon CloudWatch, which is closer than most products in this experiment manage. | Agent | Sessions | Chose Amazon CloudWatch | Share | | --- | --- | --- | --- | | Claude Code | 120 | 6 | 5% | | Codex | 120 | 15 | 13% | | Cursor | 120 | 9 | 8% | ## By who was asking Amazon CloudWatch performs similarly across the four kinds of buyer, from 0% to 10%. That is unusual: the category leader changed with the persona in 14 of the 18 categories we measured. | Who is asking | Sessions | Chose Amazon CloudWatch | Share | | --- | --- | --- | --- | | Vibe coder | 12 | 0 | 0% | | Junior developer | 12 | 0 | 0% | | Senior engineer | 300 | 30 | 10% | | Enterprise team | 36 | 0 | 0% | ## What Amazon CloudWatch was up against The full ranking in observability, from the same sessions: | # | Product | Runs won | Share | | --- | --- | --- | --- | | 1 | Sentry | 133 | 37% | | 2 | Grafana | 52 | 14% | | 3 | Amazon CloudWatch **(this page)** | 30 | 8% | | 4 | Built in-house (no product adopted) | 22 | 6% | | 5 | Checkly | 17 | 5% | | 6 | Datadog | 16 | 4% | | 7 | Better Stack | 15 | 4% | | 8 | New Relic | 15 | 4% | ## What this means Agents almost never raise Amazon CloudWatch without choosing it: 3 sessions raised against 30 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 360 sessions in observability are part of a published set of 5,292, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: [how we measured this](/library/how-we-measured-this). Every observability run can be replayed on [the board](/leaderboards/observability). 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. ## Common questions ### Do coding agents recommend Amazon CloudWatch? Yes. Amazon CloudWatch was chosen in 30 of the 360 judged sessions in observability, a 8% install share, ranking third in its category. ### Does Claude Code recommend Amazon CloudWatch? In 6 of the 120 sessions in observability run with Claude Code, which is 5%. ### Do different coding agents treat Amazon CloudWatch differently? Not much. The three agents chose it at similar rates, between 5% and 13% of their runs. ### How was this measured? Real coding agents at pinned versions were run in sandboxes inside 51 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 3 sessions without being chosen, and chosen in 30. That is a 91% conversion from considered to chosen. ## Read next - [How to get picked for observability by coding agents](https://armature.tech/library/observability-coding-agents-playbook) (Markdown: https://armature.tech/library/observability-coding-agents-playbook.md) - [Do coding agents recommend Sentry?](https://armature.tech/library/do-coding-agents-recommend-sentry) (Markdown: https://armature.tech/library/do-coding-agents-recommend-sentry.md) - [Do coding agents recommend Grafana?](https://armature.tech/library/do-coding-agents-recommend-grafana) (Markdown: https://armature.tech/library/do-coding-agents-recommend-grafana.md) - [Do Claude Code, Codex and Cursor pick the same tools?](https://armature.tech/library/do-claude-code-and-codex-agree) (Markdown: https://armature.tech/library/do-claude-code-and-codex-agree.md) --- Armature helps software products get discovered and used by coding agents. Service: https://armature.tech/discoverability · Results: https://armature.tech/leaderboards/sectors · Contact: contact@armature.tech