Sentry vs New Relic

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Sentry
   Sentry✓fullprobed8/10

   A direct probe confirms Sentry serves a valid llms.txt at https://docs.sentry.io/llms.txt (HTTP 200) with a description of the docs, and Sentry also documents agent-oriented onboarding tooling (a CLI command that teaches Claude Code, Cursor, Codex, and Grok to install/configure Sentry) plus an official MCP server for agents to query docs and issues. Missing for 10: independent/community confirmation that an agent successfully consumes llms.txt end-to-end, and more detail on llms.txt content depth/coverage.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.sentry.io/llms.txt # Sentry Documentation > Sentry is a developer-first application monitoring pla…”
   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”

   proof ↗⚑ flag

   New Relic—none0/10

   A direct probe confirms llms.txt returns 404, and there's no evidence of agent-oriented docs designed for AI consumption; the MCP server is a separate integration mechanism, not agent-readable documentation. Missing for 10: an llms.txt file, any agent-oriented/markdown docs format, or evidence of AI agents successfully consuming New Relic docs directly.

   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.newrelic.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.newrelic.com/openapi.json, https://docs.newrelic.com/swagger.json, https://docs.newreli…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Sentry~partialprobed6/10

   Sentry ships an official CLI (sentry-cli) documented for managing releases, source maps, and debug files — tasks typically run headlessly in CI pipelines — and a web API for programmatic access to org/project data. However, the docs never explicitly frame these as 'CI automation' workflows, and there's no independent/hands-on confirmation of CI usage patterns like GitHub Actions integration examples. missing for 10: explicit CI/automation examples (e.g., GitHub Actions snippets), independent hands-on confirmation of headless CLI use in pipelines, and documentation of non-interactive/scripted auth flows.

   • [claimed-docs] “It’s primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “It's primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [probe] “official CLI documented at https://docs.sentry.io/cli/”
   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”

   proof ↗⚑ flag

   New Relic~partialprobed6/10

   New Relic ships an official CLI (newrelic-cli) for deployment markers and entity search, plus a GraphQL-based NerdGraph API, both of which are inherently scriptable/headless and usable in CI pipelines (e.g. recording deployment markers on release). However, there is no explicit CI/CD integration guide, pipeline example, or documented automation workflow tying these together for AI-native/agentic use. Missing for 10: explicit CI/CD pipeline documentation or examples, evidence of headless operation being a first-class supported workflow, and independent confirmation of CLI use in automated pipelines.

   • [github] “Entity Search: Search for entities across all your New Relic accounts”
   • [github] “Deployment Markers: Easily record an APM Application deployment within New Relic.”
   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [probe] “official CLI documented at https://github.com/newrelic/newrelic-cli”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Sentry—none0/10

   All evidence describes Sentry publishing its own MCP server so external AI assistants (Claude Code, Cursor, Codex, Grok) can call Sentry's tools — the reverse of this story, which asks whether Sentry itself can consume external MCP servers' tools. No evidence shows Sentry's Seer agent or any Sentry feature accepting/plugging in third-party MCP servers.

   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”

   proof ↗⚑ flag

   New Relic—none0/10

   Evidence shows New Relic ships an official MCP server so external AI tools can connect to New Relic's data (new-relic-docs-11, new-relic-docs-22, new-relic-probe-3) — this is the reverse direction (New Relic as MCP server, not MCP client). No evidence indicates New Relic's own AI assistant or platform can consume/plug in external MCP servers to use their tools.

   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”
   • [probe] “official MCP server documented at https://docs.newrelic.com/whats-new/2025/11/whats-new-11-05-mcp-server/”
   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Sentry✓fullprobed8/10

   Sentry documents an official MCP server (sentry-mcp) with an install command and integration with AI assistants for searching errors, triaging issues, and managing projects, and it's even listed as a pricing-tier feature ('MCP access'). Missing for 10: independent/hands-on verification of the MCP server working end-to-end and more detail on tool coverage/limitations.

   • [claimed-docs] “npx @sentry/ai install”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”
   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”
   • [claimed-docs] “For solo devs working on small projects... One user, Error Monitoring and Tracing, Alerts and notifications via email, 10 custom dashboards,…”

   proof ↗⚑ flag

   New Relic✓fullprobed8/10

   New Relic ships an official MCP server (documented Nov 2025) that connects AI development tools to New Relic's platform context, including converting plain-English questions into NRQL queries. This is first-party vendor documentation with a dedicated release note and probe-confirmed URL, but lacks independent/hands-on corroboration of the MCP server's reliability. Missing for 10: independent or hands-on validation of the MCP server, detail on setup/auth flow and supported tool integrations.

   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”
   • [probe] “official MCP server documented at https://docs.newrelic.com/whats-new/2025/11/whats-new-11-05-mcp-server/”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Sentry
   Sentry✓fullprobed7/10

   Sentry documents an official CLI (docs.sentry.io/cli) primarily for managing debug files, source maps, and releases, plus a separate npx @sentry/ai install command that configures AI assistants (Claude Code, Cursor, Codex, Grok) to use Sentry/MCP — both are official, first-party CLI tooling relevant to AI-native workflows. missing for 10: independent/hands-on corroboration of the CLI's AI-native usage, and clearer documentation of the AI-install CLI's full command surface beyond the single install command.

   • [claimed-docs] “It’s primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”
   • [probe] “official CLI documented at https://docs.sentry.io/cli/”
   • [claimed-docs] “npx @sentry/ai install”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”

   proof ↗⚑ flag

   New Relic~partialprobed6/10

   New Relic ships an official open-source CLI (newrelic-cli) supporting entity search, deployment markers, and platform configuration, confirmed via GitHub repo and probe. However, the evidence doesn't show AI-native features specific to the CLI itself (e.g., natural-language query support, agentic workflows are only documented for the separate MCP server/AI assistant, not the CLI). Missing for 10: documentation of AI-native/agentic capabilities within the CLI itself, independent hands-on reviews of the CLI, and details on how it integrates with AI coding agents.

   • [github] “Entity Search: Search for entities across all your New Relic accounts”
   • [github] “Deployment Markers: Easily record an APM Application deployment within New Relic.”
   • [probe] “official CLI documented at https://github.com/newrelic/newrelic-cli”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to New Relic
   Sentry✓fullprobed7/10

   Sentry publishes a documented public web API (docs.sentry.io/api/) for managing organizations, teams, and exporting data, and additionally ships an official MCP server that lets AI assistants search, triage, and manage Sentry programmatically. However, probes show no discoverable OpenAPI/swagger spec, limiting machine-readability for automated agent tooling. Missing for 10: a public OpenAPI/schema definition, independent hands-on verification of API usage by an AI agent.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   New Relic✓fullprobed8/10

   New Relic documents NerdGraph, a GraphQL API for querying data and configuring features, with an interactive explorer, plus an official CLI (newrelic-cli) that wraps API functionality for entity search and deployment markers. This constitutes a documented public API surface that can be driven programmatically outside the UI. Missing for 10: no discoverable OpenAPI/Swagger spec (probe found 404s) and no independent hands-on developer corroboration of NerdGraph usage beyond docs.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [github] “Entity Search: Search for entities across all your New Relic accounts”
   • [github] “Deployment Markers: Easily record an APM Application deployment within New Relic.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.newrelic.com/openapi.json, https://docs.newrelic.com/swagger.json, https://docs.newreli…”
   • [probe] “official CLI documented at https://github.com/newrelic/newrelic-cli”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Sentry—none0/10

   The evidence pack documents Sentry's general web API and MCP server for AI assistants, but nothing describes scoped or least-privilege API token/credential issuance mechanisms (e.g., granular permission scopes per token) for agent use. Missing for 10: documentation of scoped API token creation, per-agent permission granularity, or least-privilege credential controls.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”

   proof ↗⚑ flag

   New Relic—none0/10

   New Relic offers API access (NerdGraph, user keys) and an MCP server for AI tools, but no evidence describes scoped/least-privilege credential issuance specifically for agents (e.g., fine-grained API key scoping, role-based agent tokens). Missing for 10: documentation of scoped API key creation, least-privilege permission models for agent credentials, or agent-specific token management.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Sentry✓fullclaimed7/10

   Sentry provides official SDKs to 'drop in' across platforms (sentry-docs-12, sentry-docs-29) and specifically supports AI-agent monitoring via SDK-based agent tracing (sentry-docs-13), plus OpenTelemetry-based ingestion for building custom instrumentation (sentry-docs-8, sentry-docs-25). This gives AI-native developers first-party SDK material to build against for both traditional and agentic use cases. Missing for 10: independent/hands-on developer corroboration of SDK integration experience, and deeper documentation specifically framed for AI-native build workflows beyond agent tracing marketing copy.

   • [claimed-docs] “Drop in the [SDK](https://sentry.io/platforms/). No agents to install. No performance surprises.”
   • [claimed-docs] “Drop in the SDK. No agents to install. No performance surprises.”
   • [claimed-docs] “Agent tracing helps you catch unexpected output issues, bad tool calls and visualize the spend and performance across all your agents.”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK or through a pipeline tool like the Ope…”
   • [claimed-docs] “Monitor in five lines”

   proof ↗⚑ flag

   New Relic✓fullprobed7/10

   New Relic ships official first-party agents/SDKs for Go, Java, .NET, Node.js, PHP, Python, and Ruby, plus a GraphQL-based NerdGraph API with an interactive API explorer, OpenTelemetry instrumentation support, and an official CLI (newrelic-cli), giving developers multiple official, documented ways to build against the platform. Missing for 10: independent/hands-on corroboration of SDK developer experience and no explicit AI-native SDK features (e.g., no OpenAPI spec found, llms.txt 404).

   • [claimed-docs] “Monitor application performance across your stack. We've got agents for Go, Java, .NET, Node.js, PHP, Python, and Ruby.”
   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “Instrument your service with OpenTelemetry and gain platform-agnostic observability.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [github] “Entity Search: Search for entities across all your New Relic accounts”
   • [probe] “official CLI documented at https://github.com/newrelic/newrelic-cli”
   • [probe] “PROBE llms.txt: HTTP 404 at https://docs.newrelic.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.newrelic.com/openapi.json, https://docs.newrelic.com/swagger.json, https://docs.newreli…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Sentry
   Sentry~partialclaimed5/10

   Sentry's Alerts explicitly support calling webhooks as an action when issues match rules, which allows subscribing to events (e.g., new issues) programmatically, and this is exposed alongside Slack/other integrations. However, there is no evidence of a dedicated, documented webhook subscription API or AI-native/agentic framing (e.g., no mention of structured payload docs, event types catalog, or AI agent use of webhooks) — the MCP server is a separate pull-based interface, not webhook push. Missing for 10: dedicated webhook API/event-type documentation, AI-agent-specific webhook use cases, and independent confirmation of webhook reliability for automation.

   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [claimed-docs] “Send a notification to your team's Slack channel when a new issue is created.”

   proof ↗⚑ flag

   New Relic—none0/10

   The evidence pack shows alerts, dashboards, NerdGraph API, MCP server, and CLI capabilities, but no mention of webhook subscriptions for events or any pub/sub-style event notification mechanism for external systems. Alerts docs mention notifications but do not describe webhook subscription APIs. Missing for 10: any documentation of a webhooks feature, webhook configuration API, or event subscription endpoint.

   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”
   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry ships Seer, an AI agent embedded in the product that automatically root-causes issues, answers ad-hoc questions about telemetry, reviews PRs, and proposes fixes directly inside Sentry's dashboards/issues UI, going beyond simple search to generate actionable insights and suggestions. This is documented first-party across multiple docs pages (autofix, code review, PR creation, Q&A) though corroboration is only vendor docs, not independent hands-on reports. missing for 10: independent/hands-on validation of Seer's insight quality and no community testimony confirming accuracy of AI-generated root-cause suggestions.

   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage. PR Creation: Use Autofix to generate a code …”
   • [claimed-docs] “Have Seer review your code changes in GitHub or GitLab, catching bugs before merging.”
   • [claimed-docs] “Code Review: Have Seer review your code changes in GitHub or GitLab, catching bugs before merging.”
   • [claimed-docs] “Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent and code reviewer.”
   • [claimed-docs] “Automatically root-cause any issue”

   proof ↗⚑ flag

   New Relic✓fullclaimed7/10

   New Relic AI (docs-9, docs-10) provides in-product AI assistant for plain-language querying, troubleshooting suggestions, and query help, plus an MCP server (docs-11, docs-22) that converts natural language to NRQL for insights. This is first-party documented but lacks independent/hands-on corroboration of quality or depth of insights generated. Missing for 10: independent user validation of AI insight quality, detail on proactive/automated insight generation beyond query assistance, and depth of anomaly-detection or automated root-cause AI features.

   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”
   • [claimed-docs] “If you're struggling to get a query to work, ask our AI assistant to help you.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Sentry
   Sentry✓fullclaimed7/10

   Sentry's Seer/Autofix explicitly runs autonomously in the background: it 'automatically scans issues as they come into Sentry, finding root causes, and automating triage' and can 'generate a code fix and create a PR' without manual triggering, plus alert rules that fire automatically on new issues. This is well documented first-party but missing for 10: independent/hands-on validation of Autofix's autonomous reliability and any scheduling/cron-style automation beyond issue-triggered workflows.

   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage. PR Creation: Use Autofix to generate a code …”
   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”
   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent and code reviewer.”

   proof ↗⚑ flag

   New Relic~partialclaimed4/10

   New Relic's alerting system lets you define thresholds and notification rules that run continuously in the background without further manual intervention (new-relic-docs-5, new-relic-docs-21/25), which is a basic autonomous background automation. However, the 'ai-native/agentic' framing (AI assistant, MCP server) is described as an interactive query/troubleshooting helper (new-relic-docs-9/10) or a connector for external AI tools (new-relic-docs-11/22) rather than an autonomous agent that itself sets up and runs background tasks. Missing for 10: evidence of AI-driven workflows/agents that autonomously configure or execute actions (not just user-defined alert rules), a documented automation/workflow engine beyond alerting, and independent corroboration that these run unattended reliably.

   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”
   • [claimed-docs] “NRQL can help you: Create a new chart ... Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Sentry✓fullclaimed7/10

   Sentry ships a built-in AI agent (Seer/Seer Agent) that users can delegate tasks to directly inside the product: automatically scanning issues and root-causing them, generating fixes and PRs (Autofix), reviewing code changes, and answering ad-hoc questions about telemetry (Seer Agent) — all documented as first-party in-product features rather than an external tool. missing for 10: independent/hands-on validation of Seer's task delegation accuracy and reliability (only vendor docs are cited, no community confirmation of Seer specifically).

   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Have Seer review your code changes in GitHub or GitLab, catching bugs before merging.”
   • [claimed-docs] “Code Review: Have Seer review your code changes in GitHub or GitLab, catching bugs before merging.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”
   • [claimed-docs] “Catch critical issues before you merge and fix them when they hit prod with Seer, our debugging agent and code reviewer.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage. PR Creation: Use Autofix to generate a code …”
   • [claimed-docs] “Assign Sentry Agent to Linear issues, debug with Seer.”

   proof ↗⚑ flag

   New Relic✓fullclaimed7/10

   New Relic docs describe a built-in AI assistant (New Relic AI) that lets users ask questions in plain language, troubleshoot issues, explore telemetry data, and get help building NRQL queries directly inside the product. This matches the story of delegating tasks to an in-product AI assistant, though evidence is vendor-documentation only with no independent hands-on verification of task delegation depth or reliability. Missing for 10: independent/community corroboration of the assistant's real-world task delegation capability and quality, and more detail on the scope of tasks it can autonomously perform beyond Q&A/query help.

   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”
   • [claimed-docs] “If you're struggling to get a query to work, ask our AI assistant to help you.”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to New Relic
   Sentry✓fullprobed7/10

   Sentry ships an official MCP server (`npx @sentry/ai install`) that lets AI assistants search errors, analyze performance, triage issues, and manage projects via natural language, plus a Seer AI agent that answers free-form questions about telemetry and automates triage/PR creation. This directly supports operating Sentry through natural-language commands from AI tools like Claude Code, Cursor, Codex, and Grok. Missing for 10: independent/hands-on validation of the MCP or Seer NL interactions actually working reliably in practice, and no detail on breadth/limits of supported natural-language operations.

   • [claimed-docs] “npx @sentry/ai install”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [claimed-docs] “One command teaches Claude Code, Cursor, Codex, and Grok how to install and configure Sentry for you.”
   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”

   proof ↗⚑ flag

   New Relic✓fullprobed8/10

   New Relic AI lets users ask questions, troubleshoot, and explore telemetry in plain language, and the new MCP server explicitly converts natural-language questions into NRQL queries to retrieve results without requiring NRQL expertise. This directly delivers natural-language operation of the product for querying and troubleshooting. Missing for 10: independent/hands-on validation of the natural-language assistant's accuracy and broader coverage beyond querying (e.g., configuring alerts or dashboards via NL commands).

   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”
   • [claimed-docs] “If you're struggling to get a query to work, ask our AI assistant to help you.”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [probe] “official MCP server documented at https://docs.newrelic.com/whats-new/2025/11/whats-new-11-05-mcp-server/”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to New Relic
   Sentry—none0/10

   Evidence confirms Sentry has an API and API docs (sentry-docs-14, sentry-docs-20) but nothing shows an interactive reference with runnable/try-it-out examples; a direct probe for OpenAPI/Swagger specs at docs.sentry.io returned 404 for all candidate paths, suggesting no such interactive spec is exposed.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   New Relic~partialprobed5/10

   New Relic documents a NerdGraph API explorer for experimenting with its GraphQL API (new-relic-docs-20), which functions as an interactive, runnable reference for that API, but there's no evidence of a broader interactive API reference (e.g., REST API explorer/Swagger UI) covering the full platform, and probes show no OpenAPI spec or llms.txt exposed. Missing for 10: a comprehensive interactive reference across all New Relic APIs (not just NerdGraph), OpenAPI/Swagger-based explorer, and independent/hands-on confirmation of the explorer's usability.

   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.newrelic.com/openapi.json, https://docs.newrelic.com/swagger.json, https://docs.newreli…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Sentry—none0/10

   Sentry documents a REST API (sentry-docs-14/20) but no evidence shows a downloadable OpenAPI/Swagger spec; a direct probe for common OpenAPI paths (openapi.json, swagger.json, etc.) returned 404 across the board (sentry-probe-2), confirming no machine-readable spec is exposed.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   New Relic—none0/10

   New Relic's primary API is NerdGraph (GraphQL), and explicit probes show no OpenAPI/swagger spec is served at any standard path (404s), with no other evidence of a downloadable machine-readable spec.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.newrelic.com/openapi.json, https://docs.newrelic.com/swagger.json, https://docs.newreli…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Sentry—none0/10

   Sentry documents a public web API for account-level resources (sentry-docs-14, sentry-docs-20) but there is no evidence of API versioning scheme or a documented deprecation policy; a probe for an OpenAPI/versioned spec came back 404 across all candidate paths (sentry-probe-2), suggesting no formal versioned/deprecation documentation is exposed.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   New Relic—none0/10

   Evidence shows NerdGraph API and NerdGraph explorer exist, but there is no documented API versioning scheme or deprecation policy; probes confirm no OpenAPI spec is discoverable, and no docs mention version numbers, sunset timelines, or breaking-change guarantees. Missing for 10: documented API versioning scheme, explicit deprecation/sunset policy, changelog or migration guide for breaking changes.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.newrelic.com/openapi.json, https://docs.newrelic.com/swagger.json, https://docs.newreli…”

   proof ↗⚑ flag

Agent integration

1. ai-native userHave an external agent query metrics, logs, and traces through documented APIs to debug production

   weight 3 · round to New Relic
   Sentry✓fullprobed8/10

   Sentry ships an official MCP server allowing AI agents to search errors, analyze performance, and query telemetry (sentry-docs-2, sentry-probe-3), plus a documented REST API for managing and exporting data (sentry-docs-14/20), OTLP ingestion for traces/logs (sentry-docs-8/25), and trace explorer for span queries (sentry-docs-9). Missing for 10: independent/hands-on third-party validation of the MCP server's debugging effectiveness and a discoverable OpenAPI spec (probe found 404s for openapi.json).

   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”
   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “You can now explore span samples, visualize span attributes, and aggregate your data with flexible queries and filters.”
   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   New Relic✓fullprobed9/10

   New Relic exposes NerdGraph, a documented GraphQL API for querying metrics, logs, and traces, plus NRQL for structured queries, and now an official MCP server that lets external AI agents connect and convert natural-language questions into NRQL for troubleshooting production issues. This directly matches the story of an external agent querying telemetry through documented APIs to debug production. Missing for 10: independent hands-on validation of the MCP server/API reliability from third parties beyond vendor docs.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”
   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”
   • [probe] “official MCP server documented at https://docs.newrelic.com/whats-new/2025/11/whats-new-11-05-mcp-server/”

   proof ↗⚑ flag

Ai investigation

1. ai-native userGet AI-generated summaries of incidents and alert context for responders

   weight 2 · round to Sentry
   Sentry~partialclaimed6/10

   Sentry's Seer/Autofix feature automatically scans incoming issues, finds root causes, and automates triage, effectively generating AI context for responders (sentry-docs-5, sentry-docs-30, sentry-docs-17, sentry-docs-31, sentry-docs-15). However, evidence never explicitly frames this as an 'incident summary' or shows it delivered within alert notifications (Slack/PagerDuty) themselves, and there's no independent/hands-on validation of summary quality. Missing for 10: explicit incident/alert summary format, integration of AI summary into alert payloads, and third-party corroboration of usefulness.

   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically root-cause any issue”
   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”
   • [claimed-docs] “Suspect commits, stack traces, and PR comments.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage. PR Creation: Use Autofix to generate a code …”

   proof ↗⚑ flag

   New Relic~partialclaimed5/10

   New Relic AI (docs-9, docs-10) lets users ask questions and troubleshoot issues in plain language, and the MCP server (docs-11, docs-22) exposes platform context to AI tools, which supports AI-assisted incident triage — but no evidence explicitly shows auto-generated incident summaries or alert-specific responder context. Missing for 10: explicit incident-summary generation feature, alert-context packaging for responders, and independent/hands-on confirmation of this specific workflow.

   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”
   • [claimed-docs] “If you're struggling to get a query to work, ask our AI assistant to help you.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”

   proof ↗⚑ flag

2. ai-native userHave the platform's AI investigate an alert or error and propose a probable root cause

   weight 3 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry's Seer/Autofix feature explicitly scans incoming issues, finds root causes, and automates triage, directly matching the story of AI investigating alerts and proposing probable causes, with additional capability to answer telemetry questions and generate PR fixes. missing for 10: independent/hands-on verification of Autofix's accuracy and no third-party corroboration of root-cause quality.

   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically root-cause any issue”
   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage. PR Creation: Use Autofix to generate a code …”

   proof ↗⚑ flag

   New Relic~partialclaimed5/10

   New Relic AI is documented to let users 'ask questions, troubleshoot issues, and explore telemetry data using plain language' and the MCP server converts natural-language questions into NRQL queries, which supports AI-assisted investigation of issues, but the evidence never explicitly describes an AI that proactively investigates a specific alert/error and outputs a proposed root cause. Missing for 10: explicit documentation of an automated root-cause-analysis workflow tied to alerts/errors, hands-on/independent confirmation that the AI assistant produces accurate root-cause conclusions rather than just query help.

   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”
   • [claimed-docs] “If you're struggling to get a query to work, ask our AI assistant to help you.”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”

   proof ↗⚑ flag

Ai querying

1. ai-native userAsk questions of my telemetry in natural language and get a real query or chart back

   weight 2 · round to New Relic
   Sentry~partialprobed6/10

   Sentry's Seer Agent explicitly supports natural-language querying of telemetry ('Ask any question about your application and Seer Agent finds the right telemetry to answer it'), and the MCP server lets AI assistants search errors and performance data conversationally. However, evidence doesn't clearly confirm it returns a 'real query or chart' artifact (vs. just an answer/summary), and there's no independent/hands-on corroboration of this specific NL-to-query flow. Missing for 10: concrete example of NL question producing an actual saved query or chart output, independent verification of accuracy/usefulness.

   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”
   • [claimed-docs] “You can now explore span samples, visualize span attributes, and aggregate your data with flexible queries and filters.”

   proof ↗⚑ flag

   New Relic✓fullclaimed8/10

   New Relic AI explicitly lets users ask questions, troubleshoot, and explore telemetry in plain language, and can help generate/fix NRQL queries; the new MCP server converts natural-language questions directly into NRQL and returns results, tying into chart/dashboard capabilities. missing for 10: independent/hands-on validation of natural-language-to-chart accuracy and no community corroboration of the AI assistant's real-world reliability.

   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”
   • [claimed-docs] “If you're struggling to get a query to work, ask our AI assistant to help you.”
   • [claimed-docs] “Ask questions in plain English, and the MCP server converts them to NRQL to get results—even if you're not a NRQL expert.”
   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”
   • [claimed-docs] “Through our UI you can build and share tailored user-friendly charts and visualizations.”

   proof ↗⚑ flag

Alert automation

1. ai-native userPoint alert notifications at webhooks that trigger automated remediation or agents

   weight 2 · round to Sentry
   Sentry✓fullprobed7/10

   Sentry Alerts explicitly support webhooks as an action alongside notifications/tickets/integrations (sentry-docs-21), and its MCP server plus Autofix/Seer automation give a clear path to have alerts trigger agent-driven remediation. However, there's no concrete documented example or independent confirmation of a webhook wired directly into an autonomous remediation/agent pipeline end-to-end. Missing for 10: a worked example connecting an alert webhook to an agent/remediation workflow, and independent/hands-on validation of this specific pattern.

   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [probe] “official MCP server documented at https://docs.sentry.io/product/sentry-mcp/”

   proof ↗⚑ flag

   New Relic—none0/10

   The evidence pack describes generic alerting configuration (thresholds, notification recipients) and a GraphQL API (NerdGraph) for configuring some features, but nowhere explicitly mentions webhook notification channels or integration with remediation/automation agents via webhooks. Given New Relic is an observability/alerting platform, this is a fair and applicable axis, but no direct evidence confirms webhook-triggered automation exists.

   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”
   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”

   proof ↗⚑ flag

Alerting

1. sreAlert on any telemetry signal with routing, grouping, and silencing of notifications

   weight 3 · round to Sentry
   Sentry~partialclaimed6/10

   Sentry's Alerts feature supports rule-based routing to Slack, webhooks, and other integrations for new issues (sentry-docs-3, sentry-docs-21, sentry-docs-32, sentry-intdir-1), and the Issues page implies built-in grouping of similar events (sentry-docs-10, sentry-docs-36). However, the evidence centers on error/issue-level alerting rather than 'any telemetry signal' — no explicit mention of alerting on traces, spans, or custom metrics despite OTel ingestion (sentry-docs-8, sentry-docs-9), and there's no documented mute/snooze/silencing capability for notifications. Missing for 10: explicit silencing/snoozing of alerts, alert rules spanning traces/metrics/logs beyond issues, and independent confirmation of grouping/routing behavior in practice.

   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Send a notification to your team's Slack channel when a new issue is created.”
   • [claimed-docs] “This page allows you to filter by properties such as browser, device, impacted users, or whether an error is unhandled.”
   • [claimed-docs] “Learn how to use Sentry's Issues page, where you can see and start to debug errors and performance problems that are affecting your applicat…”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “You can now explore span samples, visualize span attributes, and aggregate your data with flexible queries and filters.”
   • [claimed-docs] “Be notified of issues where you work with our Slack integration.”

   proof ↗⚑ flag

   New Relic~partialclaimed5/10

   New Relic docs confirm NRQL-based alerting on any telemetry signal and thresholds with notification routing ("who is notified and how"), but the evidence pack contains no explicit mention of alert grouping or silencing/muting mechanisms. Missing for 10: documented grouping of related alerts, muting/silencing rules, and incident routing workflows with independent corroboration.

   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”
   • [claimed-docs] “NRQL can help you: Create a new chart ... Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”

   proof ↗⚑ flag

2. sreEnable anomaly or outlier detection that surfaces problems without hand-written thresholds

   weight 1 · round drawn
   Sentry—none0/10

   Evidence shows Sentry alerts are rule-based ('pre-defined rules', 'notification when a new issue is created') and Seer/Autofix focuses on root-causing issues after they occur, not on anomaly/outlier detection that replaces hand-written thresholds. No documentation mentions statistical or ML-based anomaly detection for alerting/SLOs.

   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”

   proof ↗⚑ flag

   New Relic—none0/10

   The evidence pack describes only threshold-based alerting ('you define the thresholds that if exceeded mean an issue') and NRQL-based alerts, with no mention of anomaly/outlier/baseline detection features that surface issues without hand-written thresholds.

   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”
   • [claimed-docs] “NRQL can help you: Create a new chart ... Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “Set up NRQL-based alerts (our primary and most powerful type of alert)”

   proof ↗⚑ flag

Slos

1. sreDefine SLOs with error budgets and burn-rate alerts

   weight 2 · round to New Relic
   Sentry—none0/10

   The evidence pack shows Sentry's alerting is rule-based (new issue notifications, webhooks, Slack) and covers dashboards, issues, and AI-driven root-causing, but there is no mention of SLO definitions, error budgets, or burn-rate alerting anywhere in the docs or community evidence. This is a fair capability to ask of an application monitoring platform, but nothing in the pack demonstrates it.

   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Sentry's Dashboards provide you with a broad overview of your application's health by allowing you to navigate through error and performance…”
   • [claimed-docs] “Dashboards are made up of one or more widgets, and each widget visualizes one or more dataset.”
   • [claimed-docs] “Learn how to use Sentry's Issues page, where you can see and start to debug errors and performance problems that are affecting your applicat…”

   proof ↗⚑ flag

   New Relic✓fullclaimed8/10

   New Relic's Service Level Management explicitly supports defining and consuming SLIs/SLOs, and NRQL-based alerts (its 'primary and most powerful' alert type) can be layered to implement burn-rate style alerting on top of SLO data. Missing for 10: explicit first-party documentation of a native 'error budget burn-rate alert' template/wizard (as some competitors have) and independent/hands-on confirmation of this specific workflow beyond docs.

   • [claimed-docs] “With New Relic, you can define and consume service level indicators (SLIs) and service level objectives (SLOs) for your applications.”
   • [claimed-docs] “you can define and consume service level indicators (SLIs) and service level objectives (SLOs) for your applications”
   • [claimed-docs] “NRQL can help you: Create a new chart ... Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to New Relic
   Sentry~partialclaimed3/10

   Sentry's web API is documented as usable to 'manage and export data' across organizations/teams programmatically, which could support bulk operations, but there is no explicit evidence of bulk issue actions (e.g., bulk resolve/merge/ignore many issues at once) or bulk API endpoints tailored for AI-native workflows. Missing for 10: explicit bulk-action UI/API documentation, evidence of batch processing across many issues/items, and any hands-on confirmation of bulk operation support.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”

   proof ↗⚑ flag

   New Relic~partialclaimed5/10

   NerdGraph GraphQL API and the newrelic-cli support programmatic/bulk operations like entity search across all accounts, and NRQL/dashboards can operate over aggregated data sets, but there's no explicit documentation of bulk create/update/delete operations across many items (e.g., bulk alert config, bulk entity tagging) as a first-class feature. missing for 10: explicit bulk-operation endpoints/examples (batch create/update/delete across many entities), hands-on evidence of bulk workflows succeeding at scale.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [github] “Entity Search: Search for entities across all your New Relic accounts”
   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry's Alerts system explicitly triggers automated actions (notifications, ticket creation, webhooks, integrations) when issues match pre-defined rules, and Autofix/Seer automates triage, root-causing, and even PR creation on incoming events. This is a well-documented, core rules-based automation capability, though it's not specifically 'AI-native' rule authoring (e.g., natural language rule definition) and lacks independent hands-on verification of the automation firing reliably. Missing for 10: independent/hands-on evidence of automation triggering correctly, and natural-language/AI-native rule definition rather than standard rule builder.

   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage. PR Creation: Use Autofix to generate a code …”
   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”

   proof ↗⚑ flag

   New Relic✓fullclaimed7/10

   New Relic's alerting system lets users define thresholds/conditions (including powerful NRQL-based conditions) and specify who/how to notify when those conditions are breached, which is the core of automated rule-triggered actions on events (new-relic-docs-5, new-relic-docs-3/21/25). missing for 10: evidence of richer automated remediation/workflow actions (e.g., auto-scaling, ticket creation, custom webhooks) beyond notification routing, and independent/hands-on confirmation that alert rules reliably trigger actions in production.

   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”
   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”
   • [claimed-docs] “NRQL can help you: Create a new chart ... Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “Set up NRQL-based alerts (our primary and most powerful type of alert)”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Sentry—none0/10

   Sentry's evidence shows event-triggered alerts, dashboards, Seer/Autofix triage, and MCP integration, but nothing about scheduling recurring jobs or workflows (e.g., cron-based automation or scheduled AI workflows) for AI-native users. Alerts (sentry-docs-3, sentry-docs-21) fire on issue events, not on a schedule, and no cron/scheduling feature is documented in this pack.

   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Autofix: Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Connects AI assistants to Sentry for searching errors, analyzing performance, triaging issues, reading documentation, and managing projects …”

   proof ↗⚑ flag

   New Relic—none0/10

   New Relic's evidence pack shows synthetic monitoring (docs-19) and alerting/dashboards, but there is no documentation of a general job/workflow scheduler, cron-like automation, or AI-native recurring workflow execution capability tied to its MCP server or NerdGraph API. The axis is plausible for a monitoring platform (e.g., scheduled synthetic checks), but no evidence confirms recurring job/workflow scheduling as a user-facing automation feature.

   • [claimed-docs] “Simulate end-user activity and API calls from locations around the world, so you can find problems before your users do.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”
   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Sentry—none0/10

   Sentry ships automation-like features (Alerts rules, Autofix/Seer triage) but the evidence pack contains no mention of version history, review workflows, or rollback capabilities for these automations. Absence of evidence for an applicable capability yields 'none'.

   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage.”
   • [claimed-docs] “Automatically scan issues as they come into Sentry, finding root causes, and automating triage. PR Creation: Use Autofix to generate a code …”

   proof ↗⚑ flag

   New Relic—none0/10

   The evidence pack shows NerdGraph API and CLI for configuring alerts/dashboards, but nothing about versioning, reviewing, or rolling back automations (e.g., alert configs, workflows) — no changelog, diff/review UI, or rollback mechanism is documented.

   ⚑ flag

Cost

1. sreSee what my observability spend is, attribute it to teams or services, and catch usage spikes before the bill

   weight 3 · round drawn
   Sentry—none0/10

   The evidence pack shows Sentry's product dashboards for error/performance data and general pricing tiers, but contains no mention of billing/usage spend visibility, cost attribution to teams or services, or spike alerts on observability spend — a capability Sentry does document elsewhere (e.g. quota management, spike protection) but which is absent from this evidence set. missing for 10: spend/cost dashboards, per-team/service cost attribution, usage spike alerting or quota-based billing alerts.

   • [claimed-docs] “Sentry's [Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/) provide you with a broad overview of your applicatio…”
   • [claimed-docs] “Sentry's Dashboards provide you with a broad overview of your application's health by allowing you to navigate through error and performance…”
   • [claimed-docs] “For solo devs working on small projects... One user, Error Monitoring and Tracing, Alerts and notifications via email, 10 custom dashboards,…”

   proof ↗⚑ flag

   New Relic—none0/10

   There is no evidence of a New Relic feature for attributing observability ingest/spend to specific teams or services, nor of proactive spend/usage-spike alerting on New Relic's own billing (the closest hit, new-relic-docs-15, is about monitoring customers' cloud/K8s spend, not New Relic's own consumption). Multiple community reports directly describe the opposite experience — unexpected multi-x ingest spikes and bill surges that were only discovered after the fact (new-relic-comm-4, new-relic-comm-5, new-relic-comm-8, new-relic-comm-9), with no mention of a dashboard or alert that would have caught them beforehand.

   • [claimed-docs] “Gain real-time visibility into multi-cloud and Kubernetes spend.”
   • [community] “New Relic wants to capture as much data as possible so that they can charge you as much as possible. I run a small environment (~20 small VM…”
   • [community] “Reminds me of when they intentionally enabled JFR on every single java process. Roughly sextupled our ingest (and associated costs) until we…”
   • [community] “I love NewRelic, but their pricing always baffled me. When we added it to our QA, UAT, and Staging envs, they started wanting to bill us as …”
   • [community] “We also run our infrastructure with redundancy, so we got billed for every region & availability zone, they wanted it to be crazy expensive.”

   proof ↗⚑ flag

2. srePredict costs from transparent published per-signal pricing without talking to sales

   weight 1 · round to Sentry
   Sentry~partialclaimed4/10

   Sentry has a public pricing page listing tiers and included features (e.g., 'solo dev' tier with error monitoring, dashboards, MCP access) and mentions of enterprise-only features like SAML+SCIM, suggesting some self-serve cost transparency, but no evidence shows actual per-signal (per-event/per-transaction) unit rates or a cost calculator that would let an SRE precisely forecast spend without contacting sales for higher tiers. Missing for 10: explicit per-unit/per-signal pricing figures, a public cost calculator, and confirmation that enterprise-tier pricing (SAML/SCIM) is available without sales engagement.

   • [claimed-docs] “For solo devs working on small projects... One user, Error Monitoring and Tracing, Alerts and notifications via email, 10 custom dashboards,…”
   • [claimed-docs] “SAML + SCIM support”

   proof ↗⚑ flag

   New Relic!disputedcontradicted4/10

   New Relic does publish some pricing info (100GB free ingest tier) on its pricing page, giving a baseline for self-service cost estimation without sales contact, but multiple independent community reports describe billing as opaque and unpredictable in practice—per-user pricing changes causing 20x bill increases, environments/redundant AZs billed as extra 'production' instances, and ingest spikes (e.g. JFR enabled by default) sextupling costs unexpectedly. This directly contradicts the 'predict costs transparently' premise even though a published price list exists. Missing for 10: detailed per-signal (e.g., per-host, per-user, per-GB-by-data-type) pricing breakdown, and evidence that published prices reliably predict actual bills without support intervention.

   • [claimed-docs] “100 GB of free data ingest/month”
   • [claimed-docs] “Sign up for free access with our perpetual free tier and 100 GB/month of data ingest included.”
   • [community] “When they changed their billing to be per user our bill went up 20x for no additional value... APM hasn't seen a single new feature in the 5…”
   • [community] “New Relic wants to capture as much data as possible so that they can charge you as much as possible. I run a small environment (~20 small VM…”
   • [community] “Reminds me of when they intentionally enabled JFR on every single java process. Roughly sextupled our ingest (and associated costs) until we…”
   • [community] “I love NewRelic, but their pricing always baffled me. When we added it to our QA, UAT, and Staging envs, they started wanting to bill us as …”
   • [community] “We also run our infrastructure with redundancy, so we got billed for every region & availability zone, they wanted it to be crazy expensive.”

   proof ↗⚑ flag

Sampling

1. developerControl trace/log sampling and retention tiers to manage data volume deliberately

   weight 2 · round to New Relic
   Sentry—none0/10

   The evidence pack covers OTLP ingestion, dashboards, alerts, and AI features, but contains no mention of configurable sample rates for traces/errors/logs, retention period settings, or data volume/quota controls that would let a developer deliberately manage data volume. Pricing tier docs (sentry-docs-27) mention plan limits like 'custom dashboards' but not retention or sampling knobs.

   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK or through a pipeline tool like the Ope…”
   • [claimed-docs] “For solo devs working on small projects... One user, Error Monitoring and Tracing, Alerts and notifications via email, 10 custom dashboards,…”

   proof ↗⚑ flag

   New Relic~partialcommunity4/10

   There is only indirect evidence: community reports mention disabling automatic log forwarding via env vars and manually turning off JFR-driven ingest spikes, implying some data-volume control exists, and the free tier caps ingest at 100GB/month. However, no first-party documentation describes explicit trace sampling rules, log drop filters, or configurable data retention tiers as a deliberate developer-facing feature. missing for 10: dedicated docs on trace/log sampling rate configuration, NRQL drop-filter rules, and retention tier selection; independent confirmation that these controls work as intended.

   • [community] “Setting NEW_RELIC_APPLICATION_LOGGING_ENABLED=false and NEW_RELIC_APPLICATION_LOGGING_FORWARDING_ENABLED=false disables the newly-default au…”
   • [community] “New Relic wants to capture as much data as possible so that they can charge you as much as possible. I run a small environment (~20 small VM…”
   • [community] “Reminds me of when they intentionally enabled JFR on every single java process. Roughly sextupled our ingest (and associated costs) until we…”
   • [claimed-docs] “100 GB of free data ingest/month”
   • [claimed-docs] “Sign up for free access with our perpetual free tier and 100 GB/month of data ingest included.”

   proof ↗⚑ flag

As code

1. developerDefine dashboards and alerts as code (JSON models, Terraform, or API) and provision them repeatably

   weight 3 · round to New Relic
   Sentry—none0/10

   Evidence confirms Sentry has dashboards, alerts, and a general web API for managing org-level resources (sentry-docs-14, sentry-docs-20, sentry-docs-21, sentry-docs-22), but there is no mention of a Terraform provider, JSON-based dashboard/alert definitions, or any documented workflow for provisioning dashboards/alerts as code repeatably.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Sentry's Dashboards provide you with a broad overview of your application's health by allowing you to navigate through error and performance…”

   proof ↗⚑ flag

   New Relic~partialclaimed5/10

   NerdGraph is documented as a GraphQL API that can 'configure some New Relic features' and has an API explorer, implying dashboards/alerts could be provisioned programmatically, and the newrelic-cli exists for some automation tasks. However, the evidence pack never explicitly documents JSON dashboard definition files, a Terraform provider, or alerts-as-code workflows — dashboards are described mainly as built through the UI. Missing for 10: explicit Terraform provider docs, JSON dashboard schema/export-import examples, and alert-as-code API examples beyond generic NerdGraph mention.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”
   • [claimed-docs] “Through our UI you can build and share tailored user-friendly charts and visualizations.”
   • [github] “Entity Search: Search for entities across all your New Relic accounts”
   • [github] “Deployment Markers: Easily record an APM Application deployment within New Relic.”

   proof ↗⚑ flag

Dashboards

1. sreBuild shareable dashboards with rich visualization types and template variables

   weight 2 · round to New Relic
   Sentry~partialclaimed5/10

   Sentry docs confirm dashboards with multiple widgets that visualize datasets and support navigating error/performance data across projects, plus pricing tiers referencing '10 custom dashboards', showing dashboard-building capability exists. However there is no evidence of template variables or explicit 'shareable dashboard' functionality in the pack. Missing for 10: template variables support, explicit shareable-link/export mechanism, and independent corroboration of rich visualization variety.

   • [claimed-docs] “Sentry's [Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/) provide you with a broad overview of your applicatio…”
   • [claimed-docs] “Sentry's Dashboards provide you with a broad overview of your application's health by allowing you to navigate through error and performance…”
   • [claimed-docs] “Dashboards are made up of one or more widgets, and each widget visualizes one or more dataset.”
   • [claimed-docs] “For solo devs working on small projects... One user, Error Monitoring and Tracing, Alerts and notifications via email, 10 custom dashboards,…”

   proof ↗⚑ flag

   New Relic~partialclaimed7/10

   Docs confirm New Relic dashboards support rich visualizations built via UI/NRQL and can be publicly shared via live dashboard URLs, satisfying most of the story. However, evidence does not explicitly mention template variables on dashboards, and there is no independent/hands-on corroboration of the dashboard-building experience (community evidence focuses on pricing/UI complaints unrelated to dashboard features). Missing for 10: explicit documentation of template variables support, independent verification of dashboard usability/quality.

   • [claimed-docs] “Through our UI you can build and share tailored user-friendly charts and visualizations.”
   • [claimed-docs] “Share dashboards with stakeholders outside your New Relic organization via publicly accessible live dashboard URLs.”
   • [claimed-docs] “Through our UI you can build and share tailored user-friendly charts and visualizations. Go to our dashboard capability to gather and chart …”
   • [claimed-docs] “Share dashboards with stakeholders outside your New Relic organization via publicly accessible live dashboard URLs”
   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”

   proof ↗⚑ flag

Local dev

1. developerSpin up a local or dev instance of the platform to test instrumentation and dashboards

   weight 1 · round to Sentry
   Sentry~partialcommunity6/10

   Sentry documents an official self-hosted setup ('run all of Sentry on your own server, without paying anything') with a minimal out-of-the-box configuration suitable for testing instrumentation and dashboards (sentry-docs-11, -26, -37), and community reports confirm self-hosted instances can run reliably for real use (sentry-comm-2). However, other community evidence indicates self-hosting is heavy/complex in practice (containers multiplying, high memory use, founder admitting it's 'awful to self-host' for most users) which undercuts a quick lightweight dev-spin-up experience (sentry-comm-4, sentry-comm-5, sentry-comm-9). missing for 10: a documented lightweight docker-compose/dev-mode quick-start distinct from full production self-host, and first-party evidence of a fast/minimal local dev workflow specifically for instrumentation testing.

   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases. This version comes with no guarantees or dedicat…”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases... without paying anything.”
   • [community] “I have run the self-hosted version of Sentry for a couple years at my job now and it has worked fantastically... The self-hosted version is …”
   • [community] “Sentry founder (zeeg) acknowledges: 'its 100% a valid complaint that the entire thing is awful today to self-host, and most people dont need…”
   • [community] “We also found the same problem as OP with self hosting sentry. Each release would unleash more containers and consume more memory until we c…”
   • [community] “also in recent news: 'I almost died for a full Sentry database' - a story about self-hosted Sentry database issues nearly taking down produc…”

   proof ↗⚑ flag

   New Relic—none0/10

   New Relic is delivered as a hosted SaaS platform; none of the docs describe a way to run a local or self-hosted dev instance, and community evidence explicitly notes the 'removal of development mode & support' as a past feature that is no longer offered, confirming there is no current local/dev instance capability.

   • [community] “Removal of development mode & support. The 'improved' price model. Their new UI is buggy as hell and they refuse to fix it. Every month or s…”

   proof ↗⚑ flag

Self host

1. sreRun the full observability stack self-hosted in production with documented architecture and upgrade path

   weight 2 · round to Sentry
   Sentry!disputedcontradicted5/10

   Sentry documents a full self-hosted stack with an upgrade/relocation path (sentry-docs-11, sentry-docs-26, sentry-docs-37, sentry-docs-38) and one long-term operator reports it as 'rock-solid' (sentry-comm-2), but the Sentry founder himself concedes self-hosting is 'awful today' for most users, and independent reports describe runaway container/memory growth and a near-production-down database incident (sentry-comm-4, sentry-comm-5, sentry-comm-9), directly contradicting the polished 'documented architecture and upgrade path' claim. Missing for 10: authoritative architecture diagrams/capacity planning docs, resolution of the operational scaling complaints, and a clearer first-party upgrade guide addressing the reported migration pain.

   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases. This version comes with no guarantees or dedicat…”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases... without paying anything.”
   • [claimed-docs] “If you're self-hosting Sentry and want to know how to switch to Sentry SaaS, check out this live workshop to learn more about our relocation…”
   • [community] “I have run the self-hosted version of Sentry for a couple years at my job now and it has worked fantastically... The self-hosted version is …”
   • [community] “Sentry founder (zeeg) acknowledges: 'its 100% a valid complaint that the entire thing is awful today to self-host, and most people dont need…”
   • [community] “We also found the same problem as OP with self hosting sentry. Each release would unleash more containers and consume more memory until we c…”
   • [community] “also in recent news: 'I almost died for a full Sentry database' - a story about self-hosted Sentry database issues nearly taking down produc…”

   proof ↗⚑ flag

   New Relic—none0/10

   New Relic is documented as a SaaS platform (agents forward data to New Relic-hosted cloud) with no self-hosted deployment architecture, upgrade path, or on-prem installation docs anywhere in the evidence. Community commentary explicitly notes New Relic controls 'where the server is' and that on-prem APM remains an underserved market they don't address, confirming no self-hosted offering exists.

   • [community] “They don’t care that much about open source agent, but they do care about where the server is... there is still a huge underserved market fo…”
   • [claimed-docs] “By default, our APM agents do two things: add metadata to your logs, which gives you logs in context (ability to see logs data in various re…”
   • [claimed-docs] “100 GB of free data ingest/month”

   proof ↗⚑ flag

Change tracking

1. developerCorrelate regressions with deploys and configuration changes via release or change tracking

   weight 2 · round drawn
   Sentry~partialclaimed6/10

   Sentry's CLI documentation confirms release and source-map management tied to deploys, and 'suspect commits' links issues directly to the code change that introduced them, supporting deploy/change correlation for regressions. However, the evidence pack lacks explicit documentation of Sentry's release health dashboards, regression comparison across releases, or deploy markers on trend graphs, which would be needed to fully substantiate this story. Missing for 10: explicit release-health/regression-by-release dashboard docs, deploy-marker overlay on charts, independent/hands-on confirmation of this workflow.

   • [claimed-docs] “It’s primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “It's primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “Suspect commits, stack traces, and PR comments.”
   • [claimed-docs] “Agent tracing helps you catch unexpected output issues, bad tool calls and visualize the spend and performance across all your agents.”

   proof ↗⚑ flag

   New Relic~partialclaimed6/10

   New Relic's CLI supports recording deployment markers (change tracking) that appear alongside APM data, and NRQL/dashboards/alerts can be used to correlate metrics around deploy times, but the evidence pack lacks documentation of a dedicated change-tracking UI feature, automatic regression detection tied to deploys, or config-change tracking beyond deployment markers. missing for 10: dedicated change-tracking/regression-correlation UI docs, evidence of automatic config-change tracking, independent confirmation of deploy correlation workflow.

   • [github] “Deployment Markers: Easily record an APM Application deployment within New Relic.”
   • [claimed-docs] “NRQL can help you: Create a new chart ... Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”

   proof ↗⚑ flag

Incidents

1. sreDeclare and track incidents with timelines, on-call schedules, and escalation policies

   weight 2 · round to Sentry
   Sentry~partialclaimed4/10

   Sentry's Alerts can trigger notifications, webhooks, and ticket creation when issues occur (sentry-docs-21, sentry-docs-3), and it integrates with incident.io for incident management (sentry-intdir-9), giving some incident-response linkage. However there is no evidence of native on-call scheduling, escalation policies, or built-in incident timeline tracking within Sentry itself — these rely on third-party tools like incident.io/PagerDuty. Missing for 10: native on-call schedule builder, escalation policy configuration, and first-party incident timeline/postmortem tracking.

   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [claimed-docs] “Manage Sentry issues from within incident.io”

   proof ↗⚑ flag

   New Relic~partialclaimed3/10

   New Relic's alerting docs mention defining thresholds and who is notified (new-relic-docs-5, new-relic-docs-25), which touches escalation/notification, but there is no evidence of a dedicated incident timeline view, on-call scheduling, or formal escalation-policy management comparable to a dedicated incident-response tool. Missing for 10: documented incident timeline tracking, on-call schedule configuration, and escalation policy chains/rotations.

   • [claimed-docs] “You define the data to watch, the thresholds that if exceeded mean an issue, who is notified, and how.”
   • [claimed-docs] “Set up NRQL-based alerts (our primary and most powerful type of alert)”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to New Relic
   Sentry~partialprobed3/10

   Sentry documents a web API for managing account-level resources (orgs, teams, data export) via docs.sentry.io/api, but there is no evidence of full UI/API parity — no OpenAPI/swagger spec was discoverable (probe returned 404s across all candidate paths), and no documentation claims that every UI action (dashboards, alerts, issue triage, Seer/Autofix workflows) is exposed via API. missing for 10: explicit parity claim, discoverable API spec/reference covering all UI features, evidence that alerts/dashboards/Seer actions are API-manageable, independent confirmation of completeness.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.sentry.io/openapi.json, https://docs.sentry.io/swagger.json, https://docs.sentry.io/api…”

   proof ↗⚑ flag

   New Relic~partialprobed5/10

   NerdGraph GraphQL API and CLI expose query, alerting, dashboard, and SLO configuration, but New Relic's own docs state NerdGraph lets you 'configure some New Relic features' — explicitly not full UI parity. No evidence every UI workflow (e.g., full dashboard builder, entity management edge cases) is API-exposed, and openapi probes 404 confirming no fully documented spec of complete surface. Missing for 10: explicit confirmation of 1:1 API/UI feature parity, comprehensive OpenAPI spec, and independent verification of coverage gaps.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [github] “Entity Search: Search for entities across all your New Relic accounts”
   • [github] “Deployment Markers: Easily record an APM Application deployment within New Relic.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.newrelic.com/openapi.json, https://docs.newrelic.com/swagger.json, https://docs.newreli…”
   • [probe] “official CLI documented at https://github.com/newrelic/newrelic-cli”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Sentry
   Sentry~partialcommunity6/10

   Sentry provides API endpopoints explicitly for exporting account/org data (sentry-docs-14, sentry-docs-20) and is fully open-source with a self-hosted option (sentry-docs-11, sentry-docs-26), plus documented relocation tooling to migrate between self-hosted and SaaS (sentry-docs-38), which supports an 'exit and self-run' path. However, there's no explicit documentation of bulk data export in specific open formats (e.g., JSON/CSV data dumps) or a dedicated 'export all your data' feature, and community evidence notes self-hosting is operationally painful (sentry-comm-4, sentry-comm-5), undercutting the ease of the 'leave' path. missing for 10: explicit bulk export format documentation, dedicated data portability/export feature, hands-on confirmation that self-host migration preserves all data losslessly.

   • [claimed-docs] “You can use the APIs to manage account-level resources, like organizations and teams, as well as manage and export data.”
   • [claimed-docs] “The Sentry web API is used to access the Sentry platform programmatically. You can use the APIs to manage account-level resources, like orga…”
   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases. This version comes with no guarantees or dedicat…”
   • [claimed-docs] “If you're self-hosting Sentry and want to know how to switch to Sentry SaaS, check out this live workshop to learn more about our relocation…”
   • [community] “We're huge fans of Sentry and have it deeply integrated in our products. The fully open source nature has helped us a ton with these advance…”
   • [community] “Sentry founder (zeeg) acknowledges: 'its 100% a valid complaint that the entire thing is awful today to self-host, and most people dont need…”
   • [community] “We also found the same problem as OP with self hosting sentry. Each release would unleash more containers and consume more memory until we c…”

   proof ↗⚑ flag

   New Relic~partialcommunity3/10

   New Relic exposes a GraphQL-based NerdGraph API and NRQL query language that could be used to pull data out programmatically, and it supports OpenTelemetry for ingestion, but there is no documented bulk 'export all my data' feature, no data-portability/exit tooling, and community comments note New Relic 'cares about where the server is' implying lock-in to their platform. missing for 10: dedicated bulk export/backup feature, explicit open-format export guarantee, independent confirmation of full data portability on exit.

   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “Instrument your service with OpenTelemetry and gain platform-agnostic observability.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [community] “They don’t care that much about open source agent, but they do care about where the server is... there is still a huge underserved market fo…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Sentry
   Sentry!disputedcontradicted5/10

   Sentry's self-hosted docs and community praise (sentry-docs-11/26/37, sentry-comm-1) describe it as open source and inspectable, but a separate community report explicitly cites a licensing shift toward closed-source components as 'a very disappointing development,' contradicting a blanket open-license claim (sentry-comm-3). Missing for 10: explicit license name/terms in evidence, confirmation of which components remain open vs BSL-restricted, and resolution of the community dispute.

   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases. This version comes with no guarantees or dedicat…”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases... without paying anything.”
   • [community] “We're huge fans of Sentry and have it deeply integrated in our products. The fully open source nature has helped us a ton with these advance…”
   • [community] “This is a very disappointing development. I was hoping to implement Sentry for a side project I have been working on, now I will have to fin…”

   proof ↗⚑ flag

   New Relic—none0/10

   New Relic's core platform is closed-source SaaS; evidence only shows an open-source CLI (newrelic-cli) and agents, not the product's source under an open license, and no evidence of the core platform's source being available.

   • [github] “Entity Search: Search for entities across all your New Relic accounts”
   • [github] “Deployment Markers: Easily record an APM Application deployment within New Relic.”
   • [community] “They don’t care that much about open source agent, but they do care about where the server is... there is still a huge underserved market fo…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Sentry
   Sentry!disputedcontradicted5/10

   Sentry documents open self-hosting (develop.sentry.dev/self-hosted) as fully free and functional, and one HN user reports years of rock-solid self-hosted operation. However, this is concretely contradicted by Sentry's own founder acknowledging 'its 100% a valid complaint that the entire thing is awful today to self-host,' plus independent reports of runaway container/memory consumption and a near-production-outage from a full self-hosted database — real hands-on evidence that self-hosting is operationally painful despite being documented as viable. missing for 10: no first-party acknowledgment/mitigation of the operational complaints, no evidence of AI-specific self-host tooling parity (e.g., Seer/MCP features working identically in self-hosted vs SaaS).

   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases. This version comes with no guarantees or dedicat…”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases... without paying anything.”
   • [claimed-docs] “If you're self-hosting Sentry and want to know how to switch to Sentry SaaS, check out this live workshop to learn more about our relocation…”
   • [community] “I have run the self-hosted version of Sentry for a couple years at my job now and it has worked fantastically... The self-hosted version is …”
   • [community] “Sentry founder (zeeg) acknowledges: 'its 100% a valid complaint that the entire thing is awful today to self-host, and most people dont need…”
   • [community] “We also found the same problem as OP with self hosting sentry. Each release would unleash more containers and consume more memory until we c…”
   • [community] “also in recent news: 'I almost died for a full Sentry database' - a story about self-hosted Sentry database issues nearly taking down produc…”

   proof ↗⚑ flag

   New Relic—none0/10

   New Relic is documented throughout as a SaaS platform (agents forwarding data to New Relic's cloud, hosted dashboards, cloud-based NRQL/NerdGraph APIs) with no mention of a self-hostable core product. A community comment explicitly notes New Relic doesn't offer on-premise deployment ('they do care about where the server is... huge underserved market for on-premise APMs'), confirming the absence.

   • [community] “They don’t care that much about open source agent, but they do care about where the server is... there is still a huge underserved market fo…”
   • [claimed-docs] “100 GB of free data ingest/month”
   • [claimed-docs] “Sign up for free access with our perpetual free tier and 100 GB/month of data ingest included.”

   proof ↗⚑ flag

Otel

1. developerSend telemetry directly over OTLP with first-class OpenTelemetry support

   weight 3 · round to Sentry
   Sentry✓fullclaimed8/10

   Sentry documents native OTLP ingestion for traces and logs directly from an OTel SDK or via a Collector pipeline, confirming first-class OpenTelemetry support without requiring Sentry-specific SDK instrumentation. Missing for 10: independent/hands-on corroboration of OTLP ingestion working in practice, and details on completeness (e.g., metrics support, semantic convention mapping).

   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK or through a pipeline tool like the Ope…”

   proof ↗⚑ flag

   New Relic~partialclaimed6/10

   New Relic docs explicitly promote OpenTelemetry instrumentation for platform-agnostic observability, confirming OTLP/OTel support as a first-class ingestion path alongside native agents. However, evidence lacks technical detail on OTLP endpoint configuration, semantic-convention mapping fidelity, or independent hands-on validation of OTLP data quality. Missing for 10: detailed OTLP endpoint/setup docs, community/hands-on confirmation of OTLP ingestion working well, and specifics on semantic convention compatibility.

   • [claimed-docs] “Instrument your service with OpenTelemetry and gain platform-agnostic observability.”

   proof ↗⚑ flag

2. sreInstrument once with open standards and switch backends without re-instrumenting my code

   weight 2 · round to Sentry
   Sentry~partialclaimed5/10

   Sentry documents ingesting OpenTelemetry traces and logs via OTLP, either directly from an OTel SDK or through the OTel Collector, which supports instrumenting with open standards, but Sentry's own marketing pushes its proprietary SDK ('Drop in the SDK. No agents to install') as the primary path rather than OTel-native instrumentation. There is no documentation or independent evidence discussing seamless backend-switching or avoiding vendor lock-in once instrumented via OTel. Missing for 10: explicit guidance/tutorials on pure-OTel-only instrumentation, documentation of multi-backend portability, and independent confirmation that switching away from Sentry works without re-instrumentation.

   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK or through a pipeline tool like the Ope…”
   • [claimed-docs] “Drop in the [SDK](https://sentry.io/platforms/). No agents to install. No performance surprises.”
   • [claimed-docs] “Drop in the SDK. No agents to install. No performance surprises.”

   proof ↗⚑ flag

   New Relic~partialclaimed4/10

   New Relic docs confirm OpenTelemetry support ('Instrument your service with OpenTelemetry and gain platform-agnostic observability'), which addresses the open-standards instrumentation ask, but the evidence pack otherwise emphasizes proprietary APM agents, NRQL, and NerdGraph as the primary ingestion/analysis path, with no detail on OTLP endpoint configuration, semantic-convention parity, or documented ease of switching backends without re-instrumenting. Missing for 10: detailed OTel onboarding/ingestion docs, evidence of vendor-neutral backend portability, and independent/hands-on confirmation that OTel-instrumented apps get full feature parity vs proprietary agents.

   • [claimed-docs] “Instrument your service with OpenTelemetry and gain platform-agnostic observability.”
   • [claimed-docs] “Monitor application performance across your stack. We’ve got agents for Go, Java, .NET, Node.js, PHP, Python, and Ruby.”
   • [claimed-docs] “Monitor application performance across your stack. We've got agents for Go, Java, .NET, Node.js, PHP, Python, and Ruby.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Sentry
   Sentry~partialclaimed4/10

   Sentry's self-hosted option (sentry-docs-11/26/37) lets an org run Sentry entirely on its own infrastructure, which indirectly gives control over data location/residency, but the evidence pack contains no explicit SaaS region-selection (e.g., EU vs US hosting) or data-residency policy documentation. Missing for 10: explicit region/data-residency options for the hosted SaaS product, official compliance/residency documentation, and confirmation of choice at signup.

   • [claimed-docs] “How you can run all of Sentry on your own server, without paying anything.”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases. This version comes with no guarantees or dedicat…”
   • [claimed-docs] “Sentry offers and maintains a minimal setup that works out-of-the-box for simple use cases... without paying anything.”

   proof ↗⚑ flag

   New Relic—none0/10

   The evidence pack contains no mention of region selection, EU/US data center choice, or data residency controls; community comments only note latency issues from non-US access, not an actual data-locality control. Since this is a plausible axis for a SaaS observability platform, absence of evidence yields 'none'.

   • [community] “New Relic is especially slow because of the added latency of the trans-oceanic network hop [for non-US users]. The developers generally avoi…”
   • [community] “They don’t care that much about open source agent, but they do care about where the server is... there is still a huge underserved market fo…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Sentry—none0/10

   No evidence in the pack addresses AI-model training data usage, opt-out controls, or any privacy policy statement about excluding customer data from AI/ML training — this is an applicable privacy-posture question but entirely unevidenced.

   ⚑ flag

   New Relic—none0/10

   No evidence in the pack addresses data usage for AI model training or an opt-out/data-privacy control for that purpose; the AI-related docs describe New Relic AI assistant features and MCP server, not training data policies. Missing for 10: any privacy policy, data processing agreement, or opt-out mechanism specifically regarding AI training use of customer data.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Sentry—none0/10

   No evidence pack items address data retention policies, retention period configuration, or data deletion controls for AI-native usage; nothing about GDPR/data deletion requests, retention settings, or PII scrubbing controls specific to AI features is present. missing for 10: documentation on configurable retention periods, data deletion APIs/workflows, and AI-specific data handling/retention controls.

   ⚑ flag

   New Relic—none0/10

   No evidence pack items address data retention policies, deletion controls, or privacy/compliance configuration for AI-native users; the pack covers monitoring, dashboards, alerts, and MCP/AI query features but nothing on retention/deletion controls.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Sentry—none0/10

   No evidence pack items address telemetry opt-out or usage-tracking controls for AI-native users of Sentry; nothing documents a privacy/telemetry opt-out mechanism.

   ⚑ flag

   New Relic—none0/10

   No documentation addresses whether New Relic's AI features (New Relic AI assistant, MCP server) track usage/telemetry or provide an opt-out; the only related evidence (community tip on disabling APM log-forwarding via env vars) concerns application log collection, not AI-native usage tracking.

   • [community] “Setting NEW_RELIC_APPLICATION_LOGGING_ENABLED=false and NEW_RELIC_APPLICATION_LOGGING_FORWARDING_ENABLED=false disables the newly-default au…”
   • [claimed-docs] “It allows you to ask questions, troubleshoot issues, and explore telemetry data using plain language.”
   • [claimed-docs] “This update provides a standardized, scalable way to connect your favorite AI development tools directly to the rich context of the New Reli…”

   proof ↗⚑ flag

Analysis

1. developerGroup and filter by high-cardinality fields (user id, request id) without pre-aggregating or defining indexes first

   weight 2 · round to Sentry
   Sentry~partialclaimed6/10

   Sentry's Trace Explorer and Issues page let developers filter/aggregate by arbitrary properties like impacted users, browser, or device with 'flexible queries and filters' without needing pre-defined dashboards or indexes (sentry-docs-9, sentry-docs-10, sentry-docs-36). This implies ad-hoc high-cardinality filtering (e.g. user id) is supported, but the evidence never explicitly addresses request-id-level grouping, cardinality limits, or performance at scale. Missing for 10: explicit documentation of high-cardinality tag/attribute indexing behavior, request-id grouping examples, and independent/hands-on confirmation of performance with high-cardinality fields.

   • [claimed-docs] “You can now explore span samples, visualize span attributes, and aggregate your data with flexible queries and filters.”
   • [claimed-docs] “This page allows you to filter by properties such as browser, device, impacted users, or whether an error is unhandled.”
   • [claimed-docs] “Learn how to use Sentry's Issues page, where you can see and start to debug errors and performance problems that are affecting your applicat…”

   proof ↗⚑ flag

   New Relic~partialcommunity3/10

   NRQL is described as a flexible ad-hoc query language for exploring telemetry data and building charts/alerts (new-relic-docs-3, new-relic-docs-21, new-relic-docs-25), which implies some ability to filter/group on arbitrary attributes, but nothing in the evidence explicitly claims support for high-cardinality fields like user id or request id, or states that no pre-aggregation/indexing is required. A community report even notes 'constant problems with metric names exploding' (new-relic-comm-11), hinting at cardinality friction in practice. missing for 10: explicit documentation of high-cardinality attribute support, confirmation that NRQL/NRDB requires no schema/index definition for arbitrary fields, and hands-on evidence of filtering by user id/request id at scale.

   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”
   • [claimed-docs] “NRQL can help you: Create a new chart ... Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [community] “I've long preferred New Relic as well - it always seemed the most natural to use; the information that was important was easy to find... I'v…”

   proof ↗⚑ flag

Errors

1. developerSee application errors grouped into issues with stack traces, release tracking, and regression detection

   weight 2 · round to Sentry
   Sentry✓fullcommunity9/10

   Sentry's core product docs directly describe issue grouping with filtering, stack traces/suspect commits, release/source map tracking via Sentry CLI, and regression detection surfaced through the Issues page and alerting on new issues. Community evidence (HN) corroborates real-world use of core error monitoring at scale, though it focuses more on self-hosting operational concerns than the grouping/regression UX specifically. missing for 10: independent hands-on account specifically validating regression detection and issue-grouping accuracy (most community commentary is about self-hosting ops, not this exact workflow).

   • [claimed-docs] “This page allows you to filter by properties such as browser, device, impacted users, or whether an error is unhandled.”
   • [claimed-docs] “Learn how to use Sentry's Issues page, where you can see and start to debug errors and performance problems that are affecting your applicat…”
   • [claimed-docs] “Suspect commits, stack traces, and PR comments.”
   • [claimed-docs] “It’s primarily used for managing debug information files for iOS, Android, release and source maps management, as well as code mappings for …”
   • [claimed-docs] “Sentry's Alerts take action when issues in your organization match pre-defined rules. An alert can send notifications, create tickets, call …”
   • [claimed-docs] “Send a notification to your team's Slack channel when a **new** issue is created.”
   • [community] “We're huge fans of Sentry and have it deeply integrated in our products. The fully open source nature has helped us a ton with these advance…”
   • [community] “I have run the self-hosted version of Sentry for a couple years at my job now and it has worked fantastically... The self-hosted version is …”

   proof ↗⚑ flag

   New Relic—none0/10

   The evidence pack covers APM agent instrumentation, NRQL querying, dashboards, and deployment markers, but nowhere mentions error grouping into issues, stack trace capture, or regression detection — the core elements of this story. Missing for 10: any documentation of an 'errors inbox' or issue-grouping UI, stack trace capture, or regression detection tied to deployments/releases.

   • [claimed-docs] “Monitor application performance across your stack. We've got agents for Go, Java, .NET, Node.js, PHP, Python, and Ruby.”
   • [github] “Deployment Markers: Easily record an APM Application deployment within New Relic.”
   • [claimed-docs] “Our log management solution provides deeper visibility into application and infrastructure performance data (events, errors, traces, and mor…”

   proof ↗⚑ flag

Query language

1. developerAnalyze telemetry ad hoc with a documented query language

   weight 3 · round to New Relic
   Sentry~partialclaimed5/10

   Sentry's Trace Explorer explicitly supports 'flexible queries and filters' over span data, and the Issues page supports filtering by properties like browser, device, and error status, indicating ad hoc telemetry analysis capability. However, no evidence cites a formally documented query language (e.g., search syntax reference) the way other analytics tools do — the pack only shows filtering/dashboard UIs, not a named/documented query grammar. Missing for 10: explicit docs on Sentry's search/query syntax reference, examples of complex ad hoc queries, and independent validation of query language usability.

   • [claimed-docs] “You can now explore span samples, visualize span attributes, and aggregate your data with flexible queries and filters.”
   • [claimed-docs] “This page allows you to filter by properties such as browser, device, impacted users, or whether an error is unhandled.”
   • [claimed-docs] “Sentry's [Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/) provide you with a broad overview of your applicatio…”

   proof ↗⚑ flag

   New Relic✓fullclaimed9/10

   NRQL is a well-documented query language for ad hoc analysis (creating charts, troubleshooting, alerts), with an API explorer for experimentation via NerdGraph, and even an AI assistant to help construct queries. Missing for 10: independent hands-on validation of NRQL usability beyond vendor docs (community comments focus on cost/UI issues rather than the query language itself).

   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”
   • [claimed-docs] “NRQL can help you: Create a new chart ... Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “Set up NRQL-based alerts (our primary and most powerful type of alert)”
   • [claimed-docs] “NerdGraph is our GraphQL-format API that lets you query New Relic data and configure some New Relic features.”
   • [claimed-docs] “An easy way to experiment with the NerdGraph API is to use the NerdGraph API explorer.”
   • [claimed-docs] “If you're struggling to get a query to work, ask our AI assistant to help you.”

   proof ↗⚑ flag

Correlation

1. developerJump from a trace span to its correlated logs and metrics to debug a request end to end

   weight 2 · round to New Relic
   Sentry~partialclaimed5/10

   Sentry ingests OTel traces and logs (sentry-docs-8/25) and offers a Trace Explorer for span samples (sentry-docs-9), and Seer Agent claims to 'find the right telemetry' to answer questions (sentry-docs-31), suggesting some cross-telemetry correlation. However, there is no explicit documentation of a UI workflow to click from a specific span directly into correlated logs or metrics for end-to-end debugging. Missing for 10: explicit trace-to-log/metric drill-down UI documentation, metrics correlation evidence, and independent/hands-on confirmation of this specific navigation flow.

   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “You can now explore span samples, visualize span attributes, and aggregate your data with flexible queries and filters.”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK or through a pipeline tool like the Ope…”
   • [claimed-docs] “Ask any question about your application and Seer Agent finds the right telemetry to answer it.”

   proof ↗⚑ flag

   New Relic✓fullclaimed7/10

   New Relic's docs explicitly describe 'logs in context' where APM agents add metadata to logs enabling users to 'see logs data in various relevant places in our platform,' directly supporting jumping from traces to correlated logs, and log management ties together events, errors, and traces to reduce MTTR. Missing for 10: no independent/hands-on account specifically demonstrating the trace-span-to-log-and-metric pivot in the UI, and no detail on metrics correlation beyond logs-in-context.

   • [claimed-docs] “By default, our APM agents do two things: add metadata to your logs, which gives you logs in context (ability to see logs data in various re…”
   • [claimed-docs] “Use our APM agents to report logs. ... it lets you easily report application logs, with no additional third-party solutions required.”
   • [claimed-docs] “Our log management solution provides deeper visibility into application and infrastructure performance data (events, errors, traces, and mor…”
   • [claimed-docs] “Get visibility into hosts, containers, providers, network, and infrastructure.”

   proof ↗⚑ flag

Instrumentation

1. sreInstrument hosts, containers, Kubernetes, and cloud services through vendor-maintained agents and integrations

   weight 2 · round to New Relic
   Sentry~partialclaimed3/10

   Sentry's core model is SDK-based instrumentation ('No agents to install') and it does support OTLP ingestion from OTel SDKs or collector pipelines, which could pick up some infrastructure telemetry, but there is no evidence of vendor-maintained host agents, container agents, or a Kubernetes-specific integration/operator for infra-level SRE monitoring. Missing for 10: dedicated host agent, container/Kubernetes operator or integration, cloud-service-specific vendor agents, and any independent confirmation of infra-level (non-application) monitoring.

   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK or through a pipeline tool like the Ope…”
   • [claimed-docs] “Drop in the [SDK](https://sentry.io/platforms/). No agents to install. No performance surprises.”
   • [claimed-docs] “Drop in the SDK. No agents to install. No performance surprises.”

   proof ↗⚑ flag

   New Relic✓fullcommunity7/10

   New Relic docs confirm vendor-maintained APM agents for major languages, infrastructure monitoring for hosts/containers/providers/network, OpenTelemetry support, Kubernetes/cloud cost visibility, and Lambda serverless monitoring—covering the breadth of hosts, containers, K8s, and cloud services the story asks for. However, community reports flag real friction (fragile in-cluster collection services, a logging-agent bug that dropped logs) suggesting operational rough edges rather than pure vendor-doc perfection. Missing for 10: independent hands-on validation of Kubernetes-specific agent reliability, dedicated K8s integration docs beyond generic infra visibility, and confirmation that in-cluster collection issues have been resolved.

   • [claimed-docs] “Monitor application performance across your stack. We've got agents for Go, Java, .NET, Node.js, PHP, Python, and Ruby.”
   • [claimed-docs] “Instrument your service with OpenTelemetry and gain platform-agnostic observability.”
   • [claimed-docs] “Gain real-time visibility into multi-cloud and Kubernetes spend.”
   • [claimed-docs] “Monitor your serverless AWS Lambda functions using both CloudWatch data and code-level instrumentation.”
   • [claimed-docs] “Get visibility into hosts, containers, providers, network, and infrastructure.”
   • [community] “currently using NR, but it's slow, expensive and the in-cluster collection services are frustratingly fragile.”
   • [community] “New Relic's logging agent had a bug that lost a good portion of our logs for a few months last year. Support were extremely lethargic about …”

   proof ↗⚑ flag

Signals

1. sreCollect metrics, logs, and traces in one platform and pivot between them with shared context

   weight 3 · round to New Relic
   Sentry~partialclaimed5/10

   Sentry documents ingesting OpenTelemetry traces and logs via OTLP and provides a Trace Explorer plus dashboards that span error and performance data, giving some cross-signal navigation, but there is no explicit documentation of a dedicated metrics pillar (time-series metrics) or of pivoting with shared context across metrics, logs, and traces the way a dedicated observability platform would. Missing for 10: explicit metrics ingestion/storage capability, and documented shared-context correlation/pivoting UI linking metrics, logs, and traces together.

   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK”
   • [claimed-docs] “Sentry can ingest OpenTelemetry traces and logs via OTLP endpoints, either directly from an OTel SDK or through a pipeline tool like the Ope…”
   • [claimed-docs] “You can now explore span samples, visualize span attributes, and aggregate your data with flexible queries and filters.”
   • [claimed-docs] “Sentry's [Dashboards](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/) provide you with a broad overview of your applicatio…”
   • [claimed-docs] “Sentry's Dashboards provide you with a broad overview of your application's health by allowing you to navigate through error and performance…”
   • [claimed-docs] “Dashboards are made up of one or more widgets, and each widget visualizes one or more dataset.”
   • [claimed-docs] “Learn how to use Sentry's Issues page, where you can see and start to debug errors and performance problems that are affecting your applicat…”

   proof ↗⚑ flag

   New Relic✓fullcommunity7/10

   New Relic's docs describe a single platform combining APM metrics (docs-1), OpenTelemetry traces (docs-4), infrastructure metrics (docs-31), and logs explicitly linked 'in context' with APM/trace data via automatic metadata tagging (docs-23, docs-29, docs-30), plus NRQL/dashboards to query and visualize across all these data types from 'anywhere in the platform' (docs-3, docs-7, docs-26). This directly matches the SRE story of unified metrics/logs/traces with cross-navigation. Missing for 10: independent/hands-on confirmation that pivoting between telemetry types is seamless in practice, and community feedback instead raises UI slowness/confusion (comm-13, comm-14) and a past logs-forwarding bug (comm-1) that temper full confidence without rising to a concrete contradiction of the unification claim itself.

   • [claimed-docs] “Monitor application performance across your stack. We've got agents for Go, Java, .NET, Node.js, PHP, Python, and Ruby.”
   • [claimed-docs] “Instrument your service with OpenTelemetry and gain platform-agnostic observability.”
   • [claimed-docs] “Use our APM agents to report logs. ... it lets you easily report application logs, with no additional third-party solutions required.”
   • [claimed-docs] “Our log management solution provides deeper visibility into application and infrastructure performance data (events, errors, traces, and mor…”
   • [claimed-docs] “By default, our APM agents do two things: add metadata to your logs, which gives you logs in context (ability to see logs data in various re…”
   • [claimed-docs] “Get visibility into hosts, containers, providers, network, and infrastructure.”
   • [claimed-docs] “NRQL can help you: Create a new chart, Answer a specific question for the purpose of troubleshooting or business analysis, Set up NRQL-based…”
   • [claimed-docs] “Through our UI you can build and share tailored user-friendly charts and visualizations.”
   • [claimed-docs] “Through our UI you can build and share tailored user-friendly charts and visualizations. Go to our dashboard capability to gather and chart …”
   • [community] “I used New Relic for the first time at my current job, and while the service it provides to our team is invaluable, the UI is slow and very …”
   • [community] “currently using NR, but it's slow, expensive and the in-cluster collection services are frustratingly fragile.”

   proof ↗⚑ flag