New Relic vs SigNoz

Agent access

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

   weight 2 · round to SigNoz
   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

   SigNoz✓fullprobed9/10

   SigNoz hosts a live llms.txt (probe-verified HTTP 200) plus a docs.md variant and a dedicated skill.md that explicitly teaches AI coding assistants to work with SigNoz docs and queries, directly matching the agent-oriented docs story. missing for 10: no independent/community corroboration of agents actually using llms.txt successfully.

   • [probe] “PROBE llms.txt: HTTP 200 at https://signoz.io/llms.txt # SigNoz > SigNoz Cloud brings your traces, metrics, and logs into one OpenTelemetry…”
   • [probe] “PROBE docs-md: HTTP 200 at https://signoz.io/docs/introduction/.md # Welcome to SigNoz Docs Learn about SigNoz, an open-source observabilit…”
   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”

   proof ↗⚑ flag

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

   weight 2 · round to New Relic
   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

   SigNoz~partialclaimed5/10

   SigNoz can run self-hosted via Docker/Kubernetes (signoz-gh-1) and supports service accounts for programmatic API access explicitly intended for CI/CD pipelines and automation scripts (signoz-docs-22), which supports headless/CI usage. However, there's no direct evidence of a CLI tool, headless-mode flags, or CI-specific automation guides/examples showing SigNoz itself being run or controlled in a CI pipeline. missing for 10: dedicated CLI or headless-mode documentation, explicit CI pipeline examples/integration guides, evidence of automated non-interactive deployment/test workflows.

   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”
   • [claimed-docs] “Service accounts provide a secure way to grant programmatic API access to SigNoz without tying credentials to individual users. Use them for…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   SigNoz—none0/10

   All AI/MCP evidence shows SigNoz exposing its own MCP server so external agents (Claude, Cursor, Copilot) can call SigNoz's tools — the reverse of the story, which asks whether SigNoz itself can consume external MCP servers' tools. No evidence shows SigNoz acting as an MCP client plugging in third-party MCP servers.

   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [probe] “official MCP server documented at https://signoz.io/docs/ai/signoz-mcp-server/”
   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”

   proof ↗⚑ flag

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

   weight 3 · round to SigNoz
   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

   SigNoz✓fullprobed9/10

   SigNoz publishes an official MCP server documented at signoz.io/docs/ai/signoz-mcp-server, explicitly designed to connect agents like Claude, Cursor, and Copilot for natural language access to metrics, logs, traces, and alerts, with concrete use-cases documented. missing for 10: independent/hands-on third-party confirmation of the MCP server working in practice.

   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Tune a Noisy Alert”
   • [claimed-docs] “Dashboard Creation from Natural Language”
   • [probe] “official MCP server documented at https://signoz.io/docs/ai/signoz-mcp-server/”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to New Relic
   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

   SigNoz—none0/10

   The evidence pack documents MCP server support, Agent Skills, and dashboards-as-code, but no official SigNoz CLI is mentioned anywhere in the docs or GitHub materials. Absence of evidence for this applicable axis yields 'none'.

   ⚑ flag

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

   weight 3 · round to New Relic
   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

   SigNoz~partialprobed4/10

   SigNoz references programmatic API access indirectly — service accounts for CI/CD and automation (signoz-docs-22), dashboards manageable 'as code' (signoz-docs-16), and JSON editing 'without going through the API' implying an API exists (signoz-docs-17) — but there is no dedicated, discoverable public API reference or OpenAPI spec; a direct probe for openapi.json/swagger.json returned 404 on all candidate paths (signoz-probe-3). Missing for 10: a published API reference/spec, example API calls/auth docs, and independent confirmation that the API is usable end-to-end by external agents.

   • [claimed-docs] “Service accounts provide a secure way to grant programmatic API access to SigNoz without tying credentials to individual users. Use them for…”
   • [claimed-docs] “Manage dashboards as code”
   • [claimed-docs] “Edit a dashboard as JSON: read, copy, download or hand-edit the whole spec in the app, without going through the API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://signoz.io/openapi.json, https://signoz.io/swagger.json, https://signoz.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 2 · round to SigNoz
   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

   SigNoz~partialclaimed6/10

   SigNoz documents service accounts for programmatic API access decoupled from individual users, explicitly for automation/integrations, and a role-based access control system where roles group specific transactions/permissions — together this supports issuing scoped, non-personal credentials suitable for an agent. However there's no direct documentation tying this specifically to AI agents or showing a least-privilege scope tailored for the MCP/agent integration (which itself is documented separately). Missing for 10: explicit guidance/example on scoping a service account's role minimally for an AI agent's MCP access, and any independent/hands-on confirmation of least-privilege enforcement.

   • [claimed-docs] “Roles are the core unit of access control in SigNoz. A role groups transactions together — when a principal is assigned a role, they receive…”
   • [claimed-docs] “Service accounts provide a secure way to grant programmatic API access to SigNoz without tying credentials to individual users. Use them for…”
   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to New Relic
   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

   SigNoz~partialclaimed6/10

   SigNoz documents building on official OpenTelemetry SDKs to send traces, logs, and metrics (signoz-docs-1, signoz-docs-6, signoz-docs-10, signoz-docs-23), and even LLM/gen_ai telemetry flows through standard OTel SDKs. However, these are OpenTelemetry-standard SDKs rather than a SigNoz-specific SDK, and there's no dedicated language-by-language SDK reference or independent developer corroboration of the SDK experience. Missing for 10: a SigNoz-specific SDK/API client library beyond OTel instrumentation, and independent hands-on validation of SDK ergonomics.

   • [claimed-docs] “Send Traces and APM Data”
   • [claimed-docs] “Collect logs from files, stdout, FluentBit/FluentD/Logstash, OpenTelemetry SDKs, HTTP endpoints, and cloud services.”
   • [claimed-docs] “Collect metrics from applications, infrastructure, and existing Prometheus setups. SigNoz also derives APM metrics from traces automatically…”
   • [claimed-docs] “Your application emits gen_ai.* spans and metrics through standard OpenTelemetry libraries, exports them over OTLP, and SigNoz stores and qu…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   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

   SigNoz—none0/10

   The evidence pack describes alerting on logs/metrics and API access via service accounts, but never mentions webhook-based event subscriptions or outbound webhook notifications for alerts or other events. This is a fair axis for an observability platform (alert routing commonly uses webhooks), but no evidence confirms the capability exists.

   ⚑ flag

Agentic features

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

   weight 2 · round to New Relic
   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

   SigNoz~partialprobed6/10

   SigNoz doesn't ship a built-in AI-insights panel, but it does provide an official MCP server plus Agent Skills that let external AI agents (Claude, Cursor, Copilot) query SigNoz's traces/logs/metrics/alerts in natural language, with documented use-cases like investigating post-deploy changes, tuning noisy alerts, and generating dashboards from prompts. This delivers AI-generated insight/suggestion capability tied to SigNoz data, though it depends on an external agent rather than a native in-app assistant. Missing for 10: a first-party embedded AI chat/insight widget inside the SigNoz UI itself, and independent/hands-on evidence of these AI use-cases actually working.

   • [claimed-docs] “Your application emits gen_ai.* spans and metrics through standard OpenTelemetry libraries, exports them over OTLP, and SigNoz stores and qu…”
   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”
   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Tune a Noisy Alert”
   • [claimed-docs] “Dashboard Creation from Natural Language”
   • [probe] “official MCP server documented at https://signoz.io/docs/ai/signoz-mcp-server/”

   proof ↗⚑ flag

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

   weight 2 · round to New Relic
   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

   SigNoz—none0/10

   SigNoz provides alerting, dashboards, and MCP/agent-skill integrations for querying and modifying observability data, but there is no evidence of autonomous background automations (e.g., scheduled agent workflows, self-triggering remediation, or agentic loops running without human invocation). The MCP server and agent skills require an external agent to be actively invoked, not autonomous background operation. missing for 10: evidence of autonomous/scheduled background automation execution, agent-triggered workflows without human prompting, any autonomous remediation or monitoring loop.

   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”
   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Tune a Noisy Alert”
   • [claimed-docs] “Dashboard Creation from Natural Language”
   • [claimed-docs] “Set up alerts on log patterns, counts, or attribute values.”

   proof ↗⚑ flag

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

   weight 3 · round to New Relic
   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

   SigNoz—none0/10

   SigNoz's AI-related evidence describes an MCP server that lets external AI assistants (Claude, Cursor, Copilot) query SigNoz data — this is SigNoz acting as a tool for outside agents, not a built-in assistant embedded in the product itself that a user could delegate tasks to. No evidence of a native in-app AI assistant/chat feature exists in the pack.

   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”
   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Tune a Noisy Alert”
   • [claimed-docs] “Dashboard Creation from Natural Language”

   proof ↗⚑ flag

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

   weight 2 · round to New Relic
   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

   SigNoz✓fullprobed7/10

   SigNoz documents an official MCP server enabling Claude/Cursor/Copilot and other AI agents to query metrics, logs, traces, and alerts via natural language, plus published 'Agent Skills' and explicit use cases like 'Dashboard Creation from Natural Language' and 'Investigate What Changed After a Deploy'. missing for 10: independent/hands-on user reports confirming the MCP/natural-language workflow works reliably in practice, and coverage of edge cases beyond documented use cases.

   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”
   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Dashboard Creation from Natural Language”
   • [probe] “official MCP server documented at https://signoz.io/docs/ai/signoz-mcp-server/”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to New Relic
   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

   SigNoz—none0/10

   No evidence of an interactive API reference with runnable examples; the OpenAPI probe explicitly found all candidate spec paths returning 404, and no docs mention a Swagger/Redoc-style interactive playground.

   • [probe] “PROBE openapi: all candidate paths 404 (https://signoz.io/openapi.json, https://signoz.io/swagger.json, https://signoz.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   SigNoz—none0/10

   A direct probe for OpenAPI/Swagger spec endpoints returned 404 across all candidate paths, and no evidence pack item references a downloadable machine-readable API spec despite mentions of programmatic API access via service accounts.

   • [probe] “PROBE openapi: all candidate paths 404 (https://signoz.io/openapi.json, https://signoz.io/swagger.json, https://signoz.io/api/openapi.json, …”
   • [claimed-docs] “Service accounts provide a secure way to grant programmatic API access to SigNoz without tying credentials to individual users. Use them for…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   SigNoz—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; the openapi.json probe returned 404s across candidate paths and no docs mention API versioning/deprecation practices.

   • [probe] “PROBE openapi: all candidate paths 404 (https://signoz.io/openapi.json, https://signoz.io/swagger.json, https://signoz.io/api/openapi.json, …”

   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
   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

   SigNoz✓fullprobed8/10

   SigNoz documents a first-party MCP server that connects AI agents (Claude, Cursor, Copilot) for natural language access to metrics, logs, traces, and alerts, plus Agent Skills teaching assistants to query traces/logs/metrics and use cases like 'Investigate What Changed After a Deploy'. This directly enables an external agent to query metrics/logs/traces to debug production via a documented interface. Missing for 10: independent hands-on validation of MCP server reliability/accuracy, and a discoverable OpenAPI spec (probe found only 404s for standard OpenAPI paths) for direct API access outside MCP.

   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”
   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Tune a Noisy Alert”
   • [claimed-docs] “Dashboard Creation from Natural Language”
   • [probe] “official MCP server documented at https://signoz.io/docs/ai/signoz-mcp-server/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://signoz.io/openapi.json, https://signoz.io/swagger.json, https://signoz.io/api/openapi.json, …”

   proof ↗⚑ flag

Ai investigation

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

   weight 2 · round drawn
   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

   SigNoz~partialprobed5/10

   SigNoz doesn't natively generate incident summaries, but it exposes an MCP server so external AI agents (Claude, Cursor, Copilot) can query alerts/traces/logs/metrics in natural language, and documents use-cases like 'Investigate What Changed After a Deploy' and 'Tune a Noisy Alert' that resemble AI-assisted incident context gathering. This relies on connecting a third-party AI agent rather than a built-in summarization feature purpose-built for responders. Missing for 10: a native, first-party 'incident summary' or alert-context generator inside the SigNoz UI, and independent evidence of responders actually using this for real incidents.

   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Tune a Noisy Alert”
   • [probe] “official MCP server documented at https://signoz.io/docs/ai/signoz-mcp-server/”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   SigNoz~partialprobed5/10

   SigNoz ships an official MCP server that lets external AI agents (Claude, Cursor, Copilot) query traces/logs/metrics/alerts, and documents use-cases like 'Investigate What Changed After a Deploy' and 'Tune a Noisy Alert' which map to root-cause style investigation flows. However, this is not a built-in platform AI that autonomously investigates alerts and proposes a root cause — it depends on a third-party AI client driving the investigation via MCP, and there's no evidence of automated, unprompted root-cause analysis. Missing for 10: a native/first-party AI investigation feature independent of external agents, concrete example output of a proposed root cause, and independent verification of the use-case workflow's effectiveness.

   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Tune a Noisy Alert”
   • [probe] “official MCP server documented at https://signoz.io/docs/ai/signoz-mcp-server/”

   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 drawn
   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

   SigNoz✓fullprobed8/10

   SigNoz ships an official MCP server enabling natural-language access to metrics, logs, traces, and alerts, plus published Agent Skills that let AI assistants generate queries and dashboards, with a documented use case specifically titled 'Dashboard Creation from Natural Language.' Missing for 10: independent/hands-on verification that natural language queries reliably produce correct charts/queries in practice.

   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”
   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [claimed-docs] “Dashboard Creation from Natural Language”
   • [probe] “official MCP server documented at https://signoz.io/docs/ai/signoz-mcp-server/”

   proof ↗⚑ flag

Alert automation

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

   weight 2 · round drawn
   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

   SigNoz—none0/10

   The evidence pack documents alert creation from dashboards and logs, and separately documents an MCP server for AI agents to query SigNoz, but nowhere shows alert notification channels (webhooks) that can trigger external remediation or agent workflows. No citation ties alerting to webhook-based outbound triggers.

   ⚑ flag

Alerting

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

   weight 3 · round to New Relic
   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

   SigNoz~partialclaimed3/10

   Evidence confirms SigNoz supports creating alerts on logs and seeding alerts from dashboard panels (covering metrics/traces), suggesting alerting across signal types, but nothing in the pack addresses notification routing, grouping, or silencing mechanisms. missing for 10: alert routing/notification channel configuration, alert grouping logic, silencing/muting functionality, any independent corroboration of alerting behavior.

   • [claimed-docs] “Set up alerts on log patterns, counts, or attribute values.”
   • [claimed-docs] “Drill down from any panel: jump into the underlying logs and traces, break out by an attribute, create an alert seeded from the panel, or do…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   SigNoz—none0/10

   No evidence of anomaly/outlier detection features (e.g., seasonal baselining, ML-based alerting) in the docs; alerting is described only in terms of thresholds, log counts, or patterns (signoz-docs-9), not statistical anomaly detection. The AI/MCP use-cases mention 'Tune a Noisy Alert' but this is a natural-language assistant workflow, not automated anomaly detection replacing thresholds.

   ⚑ flag

Slos

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

   weight 2 · round to New Relic
   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

   SigNoz—none0/10

   The evidence pack covers SigNoz's tracing, logs, metrics, dashboards, alerting on log/metric values, and IAM, but nowhere mentions a dedicated SLO management feature, error budget tracking, or burn-rate alerting — a capability common in mature observability platforms. Since this is a fair capability for an observability platform to offer, absence of evidence means 'none' rather than 'na'.

   • [claimed-docs] “Set up alerts on log patterns, counts, or attribute values.”
   • [claimed-docs] “Use the Metrics Explorer to query and visualize data with a visual builder or advanced query languages like PromQL and ClickHouse SQL.”
   • [claimed-docs] “Drill down from any panel: jump into the underlying logs and traces, break out by an attribute, create an alert seeded from the panel, or do…”

   proof ↗⚑ flag

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

   weight 2 · round to New Relic
   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

   SigNoz~partialprobed3/10

   SigNoz provides programmatic access via service accounts for automation/CI-CD (signoz-docs-22) and an MCP server / Agent Skills that let AI agents create/modify dashboards, alerts, and queries (signoz-docs-24, signoz-docs-25), which implies scriptable, potentially bulk automation. However, there is no explicit documentation of a bulk-operations feature (e.g., batch update/delete across many dashboards, alerts, or items in one call) or an OpenAPI spec confirming such endpoints (signoz-probe-3 shows no discoverable OpenAPI). Missing for 10: explicit bulk/batch API endpoints, documented bulk create/update/delete workflows, and independent evidence of bulk operations being used in practice.

   • [claimed-docs] “Service accounts provide a secure way to grant programmatic API access to SigNoz without tying credentials to individual users. Use them for…”
   • [claimed-docs] “SigNoz publishes Agent Skills that teach AI coding assistants to work with SigNoz: search the docs, generate queries over traces, logs, and …”
   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://signoz.io/openapi.json, https://signoz.io/swagger.json, https://signoz.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 3 · round to New Relic
   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

   SigNoz~partialclaimed4/10

   SigNoz documents alert rules based on log patterns, counts, or attribute values, and lets you seed an alert from any dashboard panel, showing rule-based triggering on events. However, there is no evidence of configurable downstream 'actions' (webhooks, auto-remediation, workflow triggers) beyond alert notification, nor of an automation/rules engine tied to arbitrary event conditions. Missing for 10: documentation of action/integration types (e.g., webhook, auto-remediation, external automation triggers), evidence of a general-purpose rules engine beyond alerting, and independent confirmation of this working in practice.

   • [claimed-docs] “Set up alerts on log patterns, counts, or attribute values.”
   • [claimed-docs] “Drill down from any panel: jump into the underlying logs and traces, break out by an attribute, create an alert seeded from the panel, or do…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   SigNoz—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ 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
   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

   SigNoz—none0/10

   The evidence pack contains extensive documentation on traces, logs, metrics, dashboards, and alerting, but nothing about cost/spend visibility, per-team or per-service cost attribution, ingestion volume tracking, or spike/budget alerting on observability usage itself. A passing mention of 'usage-based' pricing on the marketing page does not constitute a cost-attribution or spend-monitoring feature.

   • [probe] “PROBE llms.txt: HTTP 200 at https://signoz.io/llms.txt # SigNoz > SigNoz Cloud brings your traces, metrics, and logs into one OpenTelemetry…”

   proof ↗⚑ flag

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

   weight 1 · round to New Relic
   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

   SigNoz—none0/10

   Evidence only shows a vague fragment mentioning 'Simple usage-base[d]' pricing on the marketing snippet (signoz-probe-1), with no actual per-signal pricing page, rate table, or cost calculator cited anywhere in the docs or GitHub evidence. Nothing shows an SRE could self-serve a cost estimate without contacting sales.

   • [probe] “PROBE llms.txt: HTTP 200 at https://signoz.io/llms.txt # SigNoz > SigNoz Cloud brings your traces, metrics, and logs into one OpenTelemetry…”

   proof ↗⚑ flag

Sampling

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

   weight 2 · round to New Relic
   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

   SigNoz—none0/10

   The evidence pack covers ingestion, dashboards, alerts, IAM, and AI features but contains no mention of trace/log sampling controls or configurable retention tiers for cost management. Missing for 10: sampling configuration docs, retention policy/TTL settings, tiered storage or data-volume cost controls.

   ⚑ flag

As code

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

   weight 3 · round to SigNoz
   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

   SigNoz~partialprobed6/10

   SigNoz docs explicitly describe managing dashboards as code and editing the full dashboard spec as JSON, plus service accounts for programmatic/CI-CD API access, which supports repeatable provisioning. However there is no evidence of a Terraform provider, and the alerts side is only shown as UI-driven ('create an alert seeded from the panel') with no dedicated alerts-as-JSON or alerts API documentation; an OpenAPI spec probe also returned 404s, suggesting the API is not well-documented publicly. Missing for 10: Terraform provider/integration, explicit alerts-as-code documentation, public API/OpenAPI reference.

   • [claimed-docs] “Manage dashboards as code”
   • [claimed-docs] “Edit a dashboard as JSON: read, copy, download or hand-edit the whole spec in the app, without going through the API.”
   • [claimed-docs] “Service accounts provide a secure way to grant programmatic API access to SigNoz without tying credentials to individual users. Use them for…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://signoz.io/openapi.json, https://signoz.io/swagger.json, https://signoz.io/api/openapi.json, …”

   proof ↗⚑ flag

Dashboards

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

   weight 2 · round to SigNoz
   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

   SigNoz✓fullclaimed8/10

   SigNoz docs describe seven panel types with a live editor, dynamic/query/custom/textbox template variables, and a public sharing flow that generates a URL anyone can open, directly matching the story's requirements. missing for 10: independent/hands-on corroboration of dashboard sharing and variable usability, and detail on visualization richness beyond panel count.

   • [claimed-docs] “Build panels in a dedicated editor: seven panel types with a live preview, switchable mid-edit without losing your formatting, units or thre…”
   • [claimed-docs] “Filter everything with variables: dynamic, query, custom and textbox variables.”
   • [claimed-docs] “Publish a dashboard publicly: a separate flow that generates a public URL anyone can open without logging in.”
   • [claimed-docs] “Manage dashboards as code”

   proof ↗⚑ flag

Local dev

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

   weight 1 · round to SigNoz
   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

   SigNoz~partialcommunity6/10

   SigNoz is explicitly self-hostable via Docker/Kubernetes/Linux and ships full instrumentation, dashboard, and trace/log/metric tooling suitable for local testing (signoz-gh-1, signoz-docs-2–17). However, hands-on community reports describe a heavy docker-compose stack, Windows install friction, and disproportionate container overhead for small/dev use, indicating the local spin-up experience is not as smooth as vendor docs imply (signoz-comm-1, signoz-comm-2, signoz-comm-4). Missing for 10: a documented lightweight/dev-mode single-binary or minimal-container setup, and confirmation these friction points have been resolved.

   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”
   • [claimed-docs] “Follow a single request across all microservices with a flamegraph view that shows every span, its duration, and parent-child relationships.”
   • [claimed-docs] “Build panels in a dedicated editor: seven panel types with a live preview, switchable mid-edit without losing your formatting, units or thre…”
   • [community] “Wanted to give signoz a try, but the sheer amount of services in the docker-compose file discouraged me, especially having to reconfigure th…”
   • [community] “I tried installation on Windows 10 via Rancher-Desktop using 'other platform' docs but ran into issues with dependencies on sh/bash. Are the…”
   • [community] “I would love to self host this for a small project, but looking at the self hosting option, there's more containers there than my whole appl…”

   proof ↗⚑ flag

Self host

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

   weight 2 · round to SigNoz
   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

   SigNoz~partialcommunity5/10

   SigNoz is confirmed self-hostable via Docker/Kubernetes/Linux with 'full control of your data plane' (signoz-gh-1), but the evidence pack contains no documentation specifically addressing production architecture guidance or an upgrade path. Community reports (signoz-comm-1, signoz-comm-4) describe the self-hosted docker-compose stack as having an overwhelming number of services requiring significant reconfiguration effort, undercutting the 'documented architecture' claim, and open-core licensing questions (signoz-comm-5) add operational ambiguity for production SRE use. Missing for 10: explicit production architecture/reference-deployment docs, documented version upgrade/migration procedures, and independent confirmation that production self-hosting is smooth at scale.

   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”
   • [community] “Wanted to give signoz a try, but the sheer amount of services in the docker-compose file discouraged me, especially having to reconfigure th…”
   • [community] “I would love to self host this for a small project, but looking at the self hosting option, there's more containers there than my whole appl…”
   • [community] “All content that resides under the 'ee/' directory of this repository, if that directory exists, is licensed under the license defined in 'e…”

   proof ↗⚑ flag

Change tracking

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

   weight 2 · round to New Relic
   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

   SigNoz~partialclaimed4/10

   SigNoz has an AI use-case doc titled 'Investigate What Changed After a Deploy' (signoz-docs-26) suggesting some deploy-correlation workflow via natural language/AI querying, but there's no dedicated deployment/release marker feature, annotation on dashboards, or explicit change-tracking/version-tagging mechanism documented. missing for 10: deploy/release marker or annotation feature on dashboards and graphs, explicit config-change tracking, first-party or independent evidence of the deploy-investigation workflow actually working end-to-end.

   • [claimed-docs] “Investigate What Changed After a Deploy”
   • [claimed-docs] “Drill down from any panel: jump into the underlying logs and traces, break out by an attribute, create an alert seeded from the panel, or do…”

   proof ↗⚑ flag

Incidents

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

   weight 2 · round to New Relic
   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

   SigNoz—none0/10

   SigNoz provides observability (traces, logs, metrics, dashboards, alerts) but the evidence pack shows no incident management features—no incident declaration, timelines, on-call schedules, or escalation policies are documented anywhere.

   ⚑ flag

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

   weight 2 · round to New Relic
   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

   SigNoz~partialprobed4/10

   SigNoz documents programmatic access via service accounts for CI/CD and automation, dashboards-as-code, and an MCP server that lets AI agents query metrics/logs/traces/alerts in natural language, showing some API-first design intent. However there is no evidence of a discoverable OpenAPI spec (probe found only 404s) and docs explicitly call out JSON dashboard editing as a path that bypasses the API, implying UI-only affordances (e.g., public dashboard publishing) that aren't confirmed to have API equivalents. missing for 10: a published OpenAPI/API reference proving full coverage, explicit confirmation that every UI action (public dashboard publish, alert tuning, log pipeline edits) is also exposed via API.

   • [claimed-docs] “Manage dashboards as code”
   • [claimed-docs] “Edit a dashboard as JSON: read, copy, download or hand-edit the whole spec in the app, without going through the API.”
   • [claimed-docs] “Service accounts provide a secure way to grant programmatic API access to SigNoz without tying credentials to individual users. Use them for…”
   • [claimed-docs] “Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://signoz.io/openapi.json, https://signoz.io/swagger.json, https://signoz.io/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 3 · round to SigNoz
   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

   SigNoz~partialcommunity6/10

   SigNoz is open-source, self-hostable, and built on OpenTelemetry standards, with data stored in ClickHouse and dashboards exportable as JSON, which supports data portability and open formats. However, there's no explicit documentation of a full bulk data export mechanism (traces/logs/metrics) for migrating away, and part of the product is open-core (ee/ licensed separately per community reports), which complicates a clean 'export everything and leave' story. missing for 10: explicit bulk export/backup tooling for traces-logs-metrics, clarity on ee-only features not being portable, independent confirmation of successful full data migration out of SigNoz.

   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”
   • [claimed-docs] “Manage dashboards as code”
   • [claimed-docs] “Edit a dashboard as JSON: read, copy, download or hand-edit the whole spec in the app, without going through the API.”
   • [community] “All content that resides under the 'ee/' directory of this repository, if that directory exists, is licensed under the license defined in 'e…”

   proof ↗⚑ flag

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

   weight 2 · round to SigNoz
   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

   SigNoz!disputedcontradicted5/10

   SigNoz's GitHub repo is publicly described as free/open-source and readable (signoz-gh-1), but a community discussion points out that the 'ee/' directory of the same repository is licensed separately under a different (non-open) license, making the project open-core rather than fully open-source (signoz-comm-5). This means not all of the source a user can read is under an open license, directly contradicting the blanket 'open-source' framing. missing for 10: clear first-party statement of exact OSS license for core vs. proprietary terms for ee/, and confirmation whether ee/ source is even publicly readable.

   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”
   • [community] “All content that resides under the 'ee/' directory of this repository, if that directory exists, is licensed under the license defined in 'e…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to SigNoz
   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

   SigNoz~partialcommunity6/10

   SigNoz is confirmed open-source and self-hostable via Docker/Kubernetes/Linux with full data-plane control (signoz-gh-1), but community reports describe self-hosting as heavy (many containers), tricky on Windows, and note an open-core split (ee/ directory under separate license), which undercuts a clean 'self-host the core product' experience. missing for 10: independent confirmation of ease/reliability of self-hosting at scale, clarity on which features require the ee/ (non-open-source) component, resolution of platform-specific setup issues.

   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”
   • [community] “Wanted to give signoz a try, but the sheer amount of services in the docker-compose file discouraged me, especially having to reconfigure th…”
   • [community] “I tried installation on Windows 10 via Rancher-Desktop using 'other platform' docs but ran into issues with dependencies on sh/bash. Are the…”
   • [community] “I would love to self host this for a small project, but looking at the self hosting option, there's more containers there than my whole appl…”
   • [community] “All content that resides under the 'ee/' directory of this repository, if that directory exists, is licensed under the license defined in 'e…”

   proof ↗⚑ flag

Otel

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

   weight 3 · round to SigNoz
   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

   SigNoz✓fullprobed8/10

   SigNoz is explicitly OpenTelemetry-native, with docs and probes confirming OTLP ingestion for traces, logs, and metrics, plus LLM-specific OTel spans/metrics via OTLP. missing for 10: no independent hands-on benchmark of OTLP ingestion reliability/performance, and no explicit mention of supported OTLP protocol variants (gRPC/HTTP) or SDK compatibility matrix.

   • [claimed-docs] “Send Traces and APM Data”
   • [claimed-docs] “Collect logs from files, stdout, FluentBit/FluentD/Logstash, OpenTelemetry SDKs, HTTP endpoints, and cloud services.”
   • [claimed-docs] “Collect metrics from applications, infrastructure, and existing Prometheus setups. SigNoz also derives APM metrics from traces automatically…”
   • [claimed-docs] “Your application emits gen_ai.* spans and metrics through standard OpenTelemetry libraries, exports them over OTLP, and SigNoz stores and qu…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://signoz.io/llms.txt # SigNoz > SigNoz Cloud brings your traces, metrics, and logs into one OpenTelemetry…”
   • [probe] “PROBE docs-md: HTTP 200 at https://signoz.io/docs/introduction/.md # Welcome to SigNoz Docs Learn about SigNoz, an open-source observabilit…”

   proof ↗⚑ flag

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

   weight 2 · round to SigNoz
   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

   SigNoz~partialclaimed6/10

   SigNoz is explicitly OpenTelemetry-native, accepting OTLP traces/logs/metrics from standard SDKs, and is positioned as a Datadog-migration target that lets teams run both platforms in parallel while migrating signal-by-signal, implying backend portability. However, there is no explicit documentation or evidence of vendor-neutral instrumentation guidance (e.g., using vanilla OTel SDKs/collector config to swap exporters without touching app code), nor any independent confirmation that switching backends is truly a config-only change. missing for 10: explicit docs on OTel Collector-based backend-agnostic instrumentation, guidance on avoiding vendor-specific SDK lock-in, and independent verification that backend switching requires no re-instrumentation.

   • [claimed-docs] “Send Traces and APM Data”
   • [claimed-docs] “Complete guide to migrating from Datadog to SigNoz. How to migrate metrics, traces/APM, logs, dashboards, and alerts.”
   • [claimed-docs] “The process can be done incrementally—you can migrate one signal type at a time while running both platforms in parallel.”
   • [claimed-docs] “Bridge Solution: Datadog Receiver”
   • [claimed-docs] “Your application emits gen_ai.* spans and metrics through standard OpenTelemetry libraries, exports them over OTLP, and SigNoz stores and qu…”

   proof ↗⚑ flag

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

   weight 2 · round to SigNoz
   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

   SigNoz~partialprobed6/10

   SigNoz can be self-hosted entirely within a user's own infrastructure (Docker/Kubernetes/Linux), giving explicit 'full control of your data plane' which inherently lets a user choose the storage region/jurisdiction. However, there is no evidence describing region-selection options for SigNoz Cloud (the managed offering) or any explicit data-residency/compliance documentation (e.g., EU vs US region choice, GDPR statements). Missing for 10: cloud-region selection UI/docs, explicit data-residency/compliance certifications, and confirmation that self-hosted deployment fully satisfies residency requirements without extra config.

   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://signoz.io/llms.txt # SigNoz > SigNoz Cloud brings your traces, metrics, and logs into one OpenTelemetry…”

   proof ↗⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   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

   SigNoz—none0/10

   The evidence pack shows SigNoz can be self-hosted with 'full control of your data plane' (signoz-gh-1), but there is no documentation of specific retention period configuration, TTL settings, or data deletion/export controls anywhere in the pack. missing for 10: explicit retention/TTL configuration docs, data deletion or purge APIs, data export/portability controls.

   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   SigNoz—none0/10

   No evidence pack item mentions any telemetry/usage-data collection by SigNoz itself, nor any opt-out/privacy setting for such tracking; the product is self-hosted and open-source, which is relevant context but not documented proof of an opt-out mechanism.

   ⚑ 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 New Relic
   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

   SigNoz!disputedcontradicted5/10

   Docs claim traces/logs can be searched and filtered by any span attribute or log field, including arbitrary high-cardinality values like user_id/request_id, without requiring pre-defined indexes (signoz-docs-3, signoz-docs-7). However, community hands-on reports on SigNoz's ClickHouse schema find that accessing map attributes (the mechanism used for flexible, high-cardinality fields) is 10-50x slower than regular columns, indicating real performance limitations for exactly this use case (signoz-comm-6, signoz-comm-7). Missing for 10: first-party benchmarks or documentation addressing high-cardinality query performance, and confirmation that no manual indexing/materialized views are needed in practice.

   • [claimed-docs] “Search and filter traces by service, operation, duration, or any span attribute.”
   • [claimed-docs] “Search, filter, and analyze logs with List, Time Series, and Table views. Stream live logs in real time.”
   • [community] “What schema does SigNoz use with Clickhouse? ...I found out that accessing map attributes is much slower (10-50x) compared to regular column…”
   • [community] “Keeping Vector out of the benchmark game shows that Signoz couldn't beat it.”

   proof ↗⚑ flag

Errors

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

   weight 2 · round drawn
   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

   SigNoz—none0/10

   The evidence pack shows SigNoz’s trace, log, metric, and dashboard capabilities but contains no mention of an error-issue grouping feature, stack-trace capture, release tracking, or regression detection — capabilities typical of dedicated error-tracking tools like Sentry. Since APM platforms commonly offer this kind of error tracking, the axis is applicable, but no evidence supports it here.

   ⚑ flag

Query language

1. developerAnalyze telemetry ad hoc with a documented query language

   weight 3 · round to New Relic
   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

   SigNoz✓fullclaimed7/10

   SigNoz documents a Metrics Explorer supporting PromQL and ClickHouse SQL query languages alongside a visual builder, plus search/filter query capabilities across traces and logs, giving developers a documented query language for ad hoc analysis. missing for 10: independent/hands-on corroboration of query language usage, and no dedicated docs page fully specifying ClickHouse SQL query syntax/limits within SigNoz.

   • [claimed-docs] “Use the Metrics Explorer to query and visualize data with a visual builder or advanced query languages like PromQL and ClickHouse SQL.”
   • [claimed-docs] “Search and filter traces by service, operation, duration, or any span attribute.”
   • [claimed-docs] “Search, filter, and analyze logs with List, Time Series, and Table views. Stream live logs in real time.”

   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
   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

   SigNoz~partialclaimed4/10

   SigNoz docs show trace flamegraphs (docs-2) and logs/metrics explorers as separate features, and dashboard panels can 'drill down' into underlying logs and traces (docs-14), but the evidence never explicitly describes jumping from an individual trace span to its correlated logs and metrics for end-to-end request debugging. missing for 10: explicit span-level 'view related logs' / 'view related metrics' action, hands-on confirmation of this correlation working in practice.

   • [claimed-docs] “Follow a single request across all microservices with a flamegraph view that shows every span, its duration, and parent-child relationships.”
   • [claimed-docs] “Drill down from any panel: jump into the underlying logs and traces, break out by an attribute, create an alert seeded from the panel, or do…”
   • [claimed-docs] “Search, filter, and analyze logs with List, Time Series, and Table views. Stream live logs in real time.”
   • [claimed-docs] “Use the Metrics Explorer to query and visualize data with a visual builder or advanced query languages like PromQL and ClickHouse SQL.”

   proof ↗⚑ flag

Instrumentation

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

   weight 2 · round to New Relic
   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

   SigNoz~partialcommunity5/10

   SigNoz documents OpenTelemetry-based ingestion for traces, logs, and metrics — including logs from files/stdout/FluentBit/cloud services and metrics from 'applications, infrastructure, and existing Prometheus setups' — and can be deployed via Docker/Kubernetes/Linux, but the evidence is thin on named vendor-maintained agents for specific cloud services or container/K8s workload instrumentation beyond generic OTel Collector mentions. A community report explicitly flags a documentation gap for basic host-level (CPU/Memory/Disk) metrics, directly undercutting the 'instrument hosts' part of the story. Missing for 10: dedicated docs/integrations pages for AWS/GCP/Azure service agents, container-runtime specific agents, and confirmation that host-level metrics are a first-class supported integration rather than a documented gap.

   • [claimed-docs] “Collect logs from files, stdout, FluentBit/FluentD/Logstash, OpenTelemetry SDKs, HTTP endpoints, and cloud services.”
   • [claimed-docs] “Collect metrics from applications, infrastructure, and existing Prometheus setups. SigNoz also derives APM metrics from traces automatically…”
   • [claimed-docs] “Send Traces and APM Data”
   • [github] “Free open-source SigNoz that runs in your own infrastructure. Deploy with Docker, Kubernetes, or Linux and keep full control of your data pl…”
   • [community] “This will be the 3rd or 4th time I have looked at the docs to figure out basic setup. Each time, I look for how it can report CPU/Memory/Dis…”

   proof ↗⚑ flag

Signals

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

   weight 3 · round to SigNoz
   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

   SigNoz✓fullprobed8/10

   SigNoz documents unified collection of traces (docs-2/3/4/5), logs (docs-6/7/8/9), and metrics (docs-10/11), all in one OpenTelemetry-native platform (probe-1), plus dashboard drill-down that pivots from a panel directly into underlying logs and traces for shared context (docs-14). This directly matches the SRE cross-signal pivoting story with strong first-party documentation. missing for 10: independent/hands-on validation of the cross-signal pivot UX itself (community evidence covers setup complexity and ClickHouse performance, not the pivot workflow), and no third-party corroboration of trace-to-log-to-metric correlation quality.

   • [claimed-docs] “Follow a single request across all microservices with a flamegraph view that shows every span, its duration, and parent-child relationships.”
   • [claimed-docs] “Collect logs from files, stdout, FluentBit/FluentD/Logstash, OpenTelemetry SDKs, HTTP endpoints, and cloud services.”
   • [claimed-docs] “Collect metrics from applications, infrastructure, and existing Prometheus setups. SigNoz also derives APM metrics from traces automatically…”
   • [claimed-docs] “Drill down from any panel: jump into the underlying logs and traces, break out by an attribute, create an alert seeded from the panel, or do…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://signoz.io/llms.txt # SigNoz > SigNoz Cloud brings your traces, metrics, and logs into one OpenTelemetry…”

   proof ↗⚑ flag