Published May 16, 2026
The vendor promotes features under public preview, such as AI-assisted log analysis and alerting. Preview status implies that feature availability, maturity, and pricing may change; buyers should validate preview features’ production readiness and contractual terms before relying on them for critical workflows.
The vendor provides guidance on cost optimization for log management; these materials are useful for planning but should be treated as prescriptive guidance rather than contractual guarantees because actual cost depends on log format, cardinality, and retention choices.
Get a comprehensive analysis of New Relic Log Management including market position, competitive landscape, adoption trends, and peer benchmarks.
Download full report →If the primary need is a dedicated logging/SIEM platform focused on security event analytics and detection-engineering workflows, specialized SIEM vendors may be a better fit.
If log volumes are very large and highly variable and the organization cannot implement or enforce governance to limit verbose production logging, alternative architectures with different cost controls or self-hosted/archival pipelines may be safer.
If the operational requirement is explicit opt-in-only telemetry collection at the vendor account level and the organization cannot accept any service defaults that enable automatic collection without prior configuration.
If the organization requires a fully open-source or self-managed stack to avoid vendor lock-in or to retain full control over telemetry egress and storage, ELK/Loki/OpenTelemetry-centric approaches may be preferable.
Community discussions often focus on pricing, defaults, and operational issues:
The vendor publishes white papers and best-practice guidance that emphasize reducing unnecessary log volume to control cost and improve search performance. Vendor materials also describe internal use of the platform at scale.
Critical evaluation:
New Relic Log Management is a log ingestion, search, analysis, and correlation capability within the New Relic Observability platform (New Relic One). Its primary function is to centralize logs and associate them with other telemetry types (metrics, traces, errors, infrastructure/Kubernetes data) so teams can investigate incidents with fewer context switches. New Relic documents a capability described internally as "logs in context," which refers to correlating logs with APM errors/traces and infrastructure data, and supports NRQL-based querying of Log data.
Key functional areas: