New Relic OpenTelemetry

Name: New Relic OpenTelemetry
Brand: New Relic

Leader

Data for Engineers

Est 2007|Valuation $6.1B|Raised $385.3M

LinkedIn 188K|Website|Web traffic 1.3M|FTEs 3,034|HQ San Francisco, California, US

MarketsInfrastructure Monitoring Observability Platform Application Performance Monitoring (APM)

Published May 16, 2026

01Common complaints

- Cost-sensitive organizations without established telemetry governance: Without active management of span volume, log verbosity, and high-cardinality attributes, ingest-based costs can increase rapidly. - Organizations that require every advanced feature to work from pure OpenTelemetry data without vendor agents: Some vendor features are documented to require vendor agents or proprietary data sources. Evaluate specific feature compatibility before migrating instrumentation strategies. - Organizations that require a simple, fully transparent per-host sticker price with minimal negotiation: Some competitors publish more explicit per-host pricing; New Relic pricing often requires modeling and validation against expected telemetry volumes. - Very small teams seeking a low-effort, "set-and-forget" observability solution: The combination of New Relic and OTel Collector configuration can involve a learning curve and operational overhead compared with simpler APM offerings.

Deal disqualifiers (poor fit)

Organizations that require highly predictable costs with minimal ongoing governance.
Organizations that require fully self-hosted observability for strict data sovereignty and no managed SaaS.
Organizations with a large population of occasional users who require full UI access and where per-seat costs would be prohibitive.

Vendor-acknowledged limitations

Differences in span and metric naming can occur when using OpenTelemetry semantic conventions versus New Relic built-in instrumentation; this may require adjustments to dashboards and alerts.

Operational limitations (commonly encountered)

OpenTelemetry Collector configuration and scaling can be complex; community discussions report performance considerations and operational tradeoffs when deploying Collectors at scale.

Roadmap visibility

Public “What’s new” posts and release notes document historical OpenTelemetry support, but public roadmaps and delivery dates are typically not contractually guaranteed; verify roadmap and SLAs with the vendor account team for enterprise commitments.

02Why they buy

Differentiators supported by evidence

- NRDOT (New Relic Distribution of the OpenTelemetry Collector): A vendor-distributed Collector build and preconfigured pipelines intended to simplify Collector deployment when exporting to New Relic. - OpenTelemetry API support in New Relic agents: Allows organizations to use vendor-neutral instrumentation approaches while retaining access to New Relic agent features and platform functionality. - Platform UI that surfaces OpenTelemetry-instrumented services with APM-style features such as service maps and error views.

Where competitors may have an advantage

Datadog: Broader ecosystem of integrations and a large product suite; some proprietary features may require Datadog-specific instrumentation.
Dynatrace: Agent-driven automation and an explicit public pricing model for per-host scenarios.
Honeycomb and OTel-native providers: Perceived as culturally and technically more focused on OpenTelemetry-first approaches, which may benefit organizations that prioritize an OTel-native stack.

03Field reports

This section summarizes themes from public review platforms and community discussion. Quoted snippets from review platforms are paraphrased to reflect reviewer sentiment while avoiding promotional phrasing. Public, independently validated OpenTelemetry-specific ROI case studies were limited in available sources. Vendor-published whitepapers and reports reference OpenTelemetry usage and platform outcomes but are authored by the vendor and may not disclose methodological details. Examples of vendor-published material that reference OpenTelemetry or platform usage: - Vendor engineering playbooks and whitepapers describing internal practices and platform usage. - Vendor impact reports that reference usage of the OpenTelemetry distribution and OTLP usage. Critical evaluation guidance for procurement: - Treat vendor performance and ROI metrics as illustrative unless independently validated. - Request reference customers that use OpenTelemetry at similar scale. - Request a before/after ingest volume breakdown and evidence for MTTR, alert noise, and other operational metrics.

Review platform summaries

- Gartner Peer Insights: A substantial volume of reviews exists for the observability market. Reviewers note that dashboards and alerting can support monitoring workflows, while others raise setup complexity and variable support responsiveness across tiers. - TrustRadius: Aggregated sentiment is generally positive in platform summaries, with reviewers highlighting usability aspects of the UI and alerting; vendor/product summary cards indicate generally favorable ratings. - Capterra: Reviews include positive comments about integrations (for example, Heroku) and recurring complaints about pricing complexity and perceived cost for smaller organizations.

Community feedback (forums)

Community threads commonly emphasize concerns about pricing predictability and ingest costs, particularly when telemetry volumes grow unexpectedly.
Some community threads also indicate that functional capabilities meet many teams' needs but that cost governance is a frequent operational concern.

Why customers choose New Relic with OpenTelemetry (review themes)

Unified visibility across traces, metrics, and logs with integrated UI workflows.
Alerting and dashboarding features that reviewers say can support faster incident investigations.
Ability to instrument via OpenTelemetry while retaining access to New Relic’s platform features.

Why some customers leave or consider alternatives

Pricing increases or unpredictable bills, especially related to logs and ingest volume.
Friction around per-user licensing for broad organizational access.
Some users report dissatisfaction after UI or product redesigns or report learning curves during setup.

04Best fit

Company sizes

Mid-market to enterprise organizations (larger organizations with multiple engineering teams).
Startups and smaller teams can use free or entry-level tiers, but telemetry growth and cost predictability are key considerations.

Industries

Commonly represented industries in public reviews and references include software, fintech, retail/e-commerce, and SaaS providers, particularly those operating microservices and Kubernetes environments.

Roles and personas

Decision makers: VP Engineering, Head of SRE/Platform, IT Ops leadership.
Daily users: SREs, DevOps engineers, backend engineers, and on-call responders.

Pain points addressed

Consolidated debugging and investigation across traces, logs, and metrics.
Operational dashboards and alerting to assist incident analysis and response.

Qualification criteria (good fit)

Organizations seeking vendor-neutral instrumentation (OpenTelemetry) combined with a managed SaaS backend.
Organizations able to invest in telemetry governance (sampling, attribute controls, log routing) during deployment.

05The pitch

What the product does (core value proposition)

New Relic OpenTelemetry support is New Relic’s set of capabilities for ingesting, normalizing, and analyzing OpenTelemetry (OTel) telemetry—traces, metrics, and logs—inside the New Relic observability platform. It is an OTel ingestion and processing path into New Relic’s observability platform rather than a separate product SKU: - Native OTLP ingest into New Relic so OTel SDKs/Collector can export directly. - New Relic Distribution of the OpenTelemetry Collector (NRDOT) for New Relic-supported Collector builds and preconfigured pipelines. - APM-style user interface and workflows that surface OTel-instrumented services (service maps, error views, etc.). The vendor positions the offering as a way to reduce vendor lock-in for instrumentation while using New Relic as the analysis and user interface layer.

Target market and market positioning

Target users: SRE/DevOps teams, platform engineering, and application developers operating microservices, Kubernetes, and hybrid-cloud systems.
Positioning: combination of OpenTelemetry standards and a managed observability backend and UI. New Relic supports instrumentation via OTel, New Relic agents, or a hybrid approach while consolidating analysis and operational workflows in its backend.

Get a comprehensive analysis of New Relic OpenTelemetry including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published May 16, 2026

01Common complaints

Cost-sensitive organizations without established telemetry governance: Without active management of span volume, log verbosity, and high-cardinality attributes, ingest-based costs can increase rapidly.
Organizations that require every advanced feature to work from pure OpenTelemetry data without vendor agents: Some vendor features are documented to require vendor agents or proprietary data sources. Evaluate specific feature compatibility before migrating instrumentation strategies.
Organizations that require a simple, fully transparent per-host sticker price with minimal negotiation: Some competitors publish more explicit per-host pricing; New Relic pricing often requires modeling and validation against expected telemetry volumes.
Very small teams seeking a low-effort, "set-and-forget" observability solution: The combination of New Relic and OTel Collector configuration can involve a learning curve and operational overhead compared with simpler APM offerings.

Deal disqualifiers (poor fit)

Organizations that require highly predictable costs with minimal ongoing governance.
Organizations that require fully self-hosted observability for strict data sovereignty and no managed SaaS.
Organizations with a large population of occasional users who require full UI access and where per-seat costs would be prohibitive.

Vendor-acknowledged limitations

Differences in span and metric naming can occur when using OpenTelemetry semantic conventions versus New Relic built-in instrumentation; this may require adjustments to dashboards and alerts.

Operational limitations (commonly encountered)

OpenTelemetry Collector configuration and scaling can be complex; community discussions report performance considerations and operational tradeoffs when deploying Collectors at scale.

Roadmap visibility

Public “What’s new” posts and release notes document historical OpenTelemetry support, but public roadmaps and delivery dates are typically not contractually guaranteed; verify roadmap and SLAs with the vendor account team for enterprise commitments.

02Why they buy

Differentiators supported by evidence

NRDOT (New Relic Distribution of the OpenTelemetry Collector): A vendor-distributed Collector build and preconfigured pipelines intended to simplify Collector deployment when exporting to New Relic.
OpenTelemetry API support in New Relic agents: Allows organizations to use vendor-neutral instrumentation approaches while retaining access to New Relic agent features and platform functionality.
Platform UI that surfaces OpenTelemetry-instrumented services with APM-style features such as service maps and error views.

Where competitors may have an advantage

Datadog: Broader ecosystem of integrations and a large product suite; some proprietary features may require Datadog-specific instrumentation.
Dynatrace: Agent-driven automation and an explicit public pricing model for per-host scenarios.
Honeycomb and OTel-native providers: Perceived as culturally and technically more focused on OpenTelemetry-first approaches, which may benefit organizations that prioritize an OTel-native stack.

03Field reports

Public, independently validated OpenTelemetry-specific ROI case studies were limited in available sources. Vendor-published whitepapers and reports reference OpenTelemetry usage and platform outcomes but are authored by the vendor and may not disclose methodological details.

Examples of vendor-published material that reference OpenTelemetry or platform usage:

Vendor engineering playbooks and whitepapers describing internal practices and platform usage.
Vendor impact reports that reference usage of the OpenTelemetry distribution and OTLP usage.

Critical evaluation guidance for procurement:

Treat vendor performance and ROI metrics as illustrative unless independently validated.
Request reference customers that use OpenTelemetry at similar scale.
Request a before/after ingest volume breakdown and evidence for MTTR, alert noise, and other operational metrics.

Review platform summaries

Gartner Peer Insights: A substantial volume of reviews exists for the observability market. Reviewers note that dashboards and alerting can support monitoring workflows, while others raise setup complexity and variable support responsiveness across tiers.
TrustRadius: Aggregated sentiment is generally positive in platform summaries, with reviewers highlighting usability aspects of the UI and alerting; vendor/product summary cards indicate generally favorable ratings.
Capterra: Reviews include positive comments about integrations (for example, Heroku) and recurring complaints about pricing complexity and perceived cost for smaller organizations.

Community feedback (forums)

Community threads commonly emphasize concerns about pricing predictability and ingest costs, particularly when telemetry volumes grow unexpectedly.
Some community threads also indicate that functional capabilities meet many teams' needs but that cost governance is a frequent operational concern.

Why customers choose New Relic with OpenTelemetry (review themes)

Unified visibility across traces, metrics, and logs with integrated UI workflows.
Alerting and dashboarding features that reviewers say can support faster incident investigations.
Ability to instrument via OpenTelemetry while retaining access to New Relic’s platform features.

Why some customers leave or consider alternatives

Pricing increases or unpredictable bills, especially related to logs and ingest volume.
Friction around per-user licensing for broad organizational access.
Some users report dissatisfaction after UI or product redesigns or report learning curves during setup.

04Best fit

Company sizes

Mid-market to enterprise organizations (larger organizations with multiple engineering teams).
Startups and smaller teams can use free or entry-level tiers, but telemetry growth and cost predictability are key considerations.

Industries

Roles and personas

Decision makers: VP Engineering, Head of SRE/Platform, IT Ops leadership.
Daily users: SREs, DevOps engineers, backend engineers, and on-call responders.

Pain points addressed

Consolidated debugging and investigation across traces, logs, and metrics.
Operational dashboards and alerting to assist incident analysis and response.

Qualification criteria (good fit)

Organizations seeking vendor-neutral instrumentation (OpenTelemetry) combined with a managed SaaS backend.
Organizations able to invest in telemetry governance (sampling, attribute controls, log routing) during deployment.

05The pitch

What the product does (core value proposition)

Native OTLP ingest into New Relic so OTel SDKs/Collector can export directly.
New Relic Distribution of the OpenTelemetry Collector (NRDOT) for New Relic-supported Collector builds and preconfigured pipelines.
APM-style user interface and workflows that surface OTel-instrumented services (service maps, error views, etc.).

The vendor positions the offering as a way to reduce vendor lock-in for instrumentation while using New Relic as the analysis and user interface layer.

Target market and market positioning

Target users: SRE/DevOps teams, platform engineering, and application developers operating microservices, Kubernetes, and hybrid-cloud systems.
Positioning: combination of OpenTelemetry standards and a managed observability backend and UI. New Relic supports instrumentation via OTel, New Relic agents, or a hybrid approach while consolidating analysis and operational workflows in its backend.

Get a comprehensive analysis of New Relic OpenTelemetry including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →