New Relic APM 360

Name: New Relic APM 360
Brand: New Relic
Rating: 4.5 (2402 reviews)

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

1) Ultra cost-sensitive startups with high log volume - Workloads with heavy log output (Kubernetes stdout, verbose application logs) can lead to sustained ingest costs unless noise is reduced or alternative retention strategies are adopted. 2) Organizations needing broad full-access for all engineers - If hundreds of engineers require deep troubleshooting permissions, per-user full-access pricing may be less economical than alternative licensing models, depending on contract terms. 3) Teams that prioritize fully automated root cause and topology mapping out of the box - Teams seeking largely hands-off, push-button root cause analysis and automated topology for very large microservice graphs may find alternative vendors more aligned to that specific need, subject to their cost and commitment models. 4) Use cases where per-host modular pricing is advantageous - Organizations with very large infrastructure footprints but a small set of users and limited indexing/retention needs might find per-host or per-module pricing models from other vendors more cost-effective in some configurations.

Deal disqualifiers (poor fit)

Organisations that require strictly predictable, fixed bills and lack FinOps discipline for variable ingest costs.
Teams where many engineers must receive full platform permissions but budget for per-user licensing is constrained.
Environments where agent installation or distributed tracing is not feasible (for example, some shared hosting environments).

Limitations and prerequisites

Transaction-centric features require distributed tracing; some advanced visualizations may require additional compute configuration.
Agent-based instrumentation is required for many features; environments without agent installation capability (for example, certain shared hosting) may be unable to use some platform capabilities.

Practical limitations reported by users (frequency-weighted)

Most commonly reported themes in accessible review summaries and community discussion:

Cost escalation (ingest and per-user licensing)
Feature breadth leading to complexity and learning curve
Occasional billing or support frustrations reported in community threads (varies by account and contract)

Vendor-acknowledged constraints

The vendor documents limits on custom event reporting (event caps per harvest cycle; payload size limits). Teams with heavy custom instrumentation should review these limits.

02Why they buy

Capabilities documented in vendor materials and reflected in market feedback

- Integrated in-context troubleshooting workflows in APM 360: correlates deployments, SLOs, logs, infrastructure, errors, and security signals within the APM experience. - Transaction-centric troubleshooting (Transaction 360): provides a transaction-level view by correlating telemetry across services; this requires distributed tracing and may require compute add-ons for some advanced visualizations. - Documented compliance posture: vendor lists multiple security and compliance attestations on its security page.

Areas where competitors may have relative advantages

Some competitors are perceived as stronger on infrastructure and cloud-native integration breadth.
Other competitors are perceived as stronger for enterprise automation and topology discovery.

03Field reports

Review platform overview (high level)

- G2: The product has a substantial volume of reviews; summaries reference near-real-time telemetry and broad observability coverage while frequently noting potential cost increases as usage grows. - TrustRadius: Listings show many reviews and note a free starting tier with retention constraints. - Gartner Peer Insights: A significant volume of reviews exists; accessible summaries highlight setup complexity, learning curve, and pricing/usability concerns in some responses.

Representative excerpts (positive and negative, paraphrased)

Review excerpts highlight useful dashboards and alerting capabilities alongside commentary that setup and costs can present challenges.
Community posts frequently report concerns about pricing and per-user costs, and some posts describe frustration with billing or support experiences; these are anecdotal and vary by account and contract.

Why customers choose the vendor (common themes)

Established APM capabilities with code-level diagnostics.
A broad feature set covering APM, infrastructure, logs, synthetics, and dashboards within a single platform.
A flexible query language (NRQL) valued by advanced users.
A free tier useful for evaluation and small workloads.

Why some customers consider leaving (common churn triggers)

Cost predictability issues as ingest grows (logs are a common driver).
Learning curve and configuration complexity associated with a broad feature set.
Perceived billing or contract friction reported in community threads.

Vendor-published customer list vs independently validated ROI

Vendor public announcements list notable organizations using the platform. Such announcements indicate market traction but do not provide an independently verified ROI methodology. The presence of a customer logo does not, by itself, indicate enterprise-wide adoption or successful outcomes across all teams.

Analyst reprints and vendor-hosted materials (caution)

Vendor-hosted analyst reprints can provide useful framing of product positioning but may reflect sponsored content; procurement teams should treat these as vendor-provided perspective rather than independent validation.

Practical "time-to-value" considerations

Time-to-value is typically influenced by:

Agent rollout and distributed tracing enablement (transaction-centric views require distributed tracing).
Log forwarding and log configuration.
Governance (naming conventions, tags, service maps), alert strategy, and cost controls.

04Best fit

Best-fit company sizes (practical guidance)

Mid-market to enterprise engineering organizations with multiple services and a need for integrated workflows across APM, logs, and infrastructure.
Organizations with a designated observability governance function (platform team or SRE team) to manage tagging, alerting standards, and cost controls.

Industries / verticals

Common fits include SaaS, e-commerce, financial services, logistics, and other digital businesses with operational uptime and performance requirements; vendor materials reference customers across retail, travel, and consumer brands.

Roles and personas

Decision makers: VP Engineering, Head of SRE/Platform, CTO (mid-market and enterprise contexts).
Daily users: SREs, on-call engineers, backend developers, and DevOps teams.
Stakeholders: Product managers and executives (often limited to dashboard-level access).

Qualification criteria (great fit)

Organizations preferring a single platform experience rather than assembling separate open-source components (Prometheus/Loki/Tempo) and integrating multiple vendor tools.
Organizations able to manage or budget for telemetry ingest volumes.
Teams that value in-context troubleshooting (correlating deployments, errors, logs, infrastructure, and traces in one experience).

05The pitch

What the product does (core value proposition)

New Relic APM 360 is an application performance monitoring (APM) feature within the New Relic observability platform. It correlates APM signals (latency, throughput, errors) with adjacent telemetry (logs, infrastructure, deployments/changes, service levels/SLOs, security signals, traces) within a single workflow to reduce context switching and support earlier issue detection and troubleshooting. Closely related: New Relic introduced Transaction 360 (announced in 2025), a transaction-centric view that correlates entities and telemetry involved in a transaction across a distributed workload. Transaction 360 is commonly discussed alongside APM 360 as part of New Relic’s move toward unified troubleshooting views.

Target market and positioning

Primary users: SREs, DevOps, platform engineering, and application developers responsible for uptime and performance in microservices and cloud-native environments.
Positioning: Vendor messaging emphasizes a unified telemetry layer with integrated query and workflow capabilities, and references AI-assisted workflows to support some troubleshooting activities.

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

Download full report →