New Relic: Application Performance Monitoring, Explained

New Relic provides a software-as-a-service observability platform that allows engineering teams to see inside their applications and infrastructure. It helps developers and operators understand the performance of their software, identify the root cause of problems, and analyze how customers interact with their digital products. The company started as a pioneer in Application Performance Monitoring (APM), a category of tools that instruments application code to trace requests and pinpoint bottlenecks. Over time, it has expanded its scope to become a comprehensive platform for collecting and analyzing what it calls "telemetry data": metrics, events, logs, and traces (MELT).

The core problem New Relic addresses is the complexity of modern software environments. As applications move from single monolithic structures to distributed microservices running in cloud environments, understanding system behavior becomes exponentially more difficult. New Relic agents collect data from every part of the technology stack, from the front-end browser to the back-end services and underlying infrastructure. This data is sent to a central platform where it can be queried, visualized in dashboards, and used to set up alerts, giving teams a unified view of their system's health.

A History of Monitoring Evolution

New Relic's journey reflects the broader evolution of software development and operations, from a focus on individual application health to a holistic view of system observability.

From APM Pioneer to Observability Platform

New Relic was founded in 2008 by Lew Cirne^[1]. Cirne had previously founded and sold Wily Technology, one of the first companies in the APM space, to CA Technologies. His vision for New Relic was to deliver APM as a more accessible, cloud-based service. The company's name is an anagram of "Lew Cirne". Initially, the product focused heavily on providing deep performance insights for applications built with Ruby on Rails, a popular framework at the time. Its ease of installation and clear dashboards helped it gain rapid traction among developers.

The company grew quickly, expanding its language agent support to include Java, .NET, Python, PHP, and Node.js. It established its headquarters in San Francisco, California^[2], and became a prominent tool in the burgeoning DevOps movement, which emphasized shared responsibility for software performance between development and operations teams.

Growth, IPO, and Strategic Shifts

Following several rounds of venture capital funding, New Relic held its initial public offering (IPO) on December 12, 2014^[3], trading on the New York Stock Exchange under the ticker symbol NEWR. The IPO solidified its position as a market leader in the APM space.

By the late 2010s, the market was shifting from siloed monitoring tools towards integrated "observability" platforms. In response, New Relic began a significant strategic pivot. In 2019, it introduced New Relic One, a redesigned platform intended to unify all its data sources into a single, programmable interface. This was followed in 2020 by a dramatic overhaul of its business model, moving away from product-specific subscriptions to a simplified consumption-based model. This change, which priced services based on data ingested and user seats, was a bold and sometimes controversial move designed to reduce friction and encourage customers to use the entire platform.

Acquisitions and Going Private

To bolster its platform capabilities, New Relic made several key acquisitions. In December 2020, it acquired Pixie Labs, a startup using eBPF technology for Kubernetes-native observability, which provides deep insights into application and network behavior without requiring manual code instrumentation. It later contributed the core Pixie technology to the Cloud Native Computing Foundation (CNCF). In October 2021, the company acquired CodeStream, a developer collaboration tool that brings observability data directly into the integrated development environment (IDE).

A major turning point occurred in 2023. On July 31, New Relic announced it had entered a definitive agreement to be acquired by private equity firms Francisco Partners and TPG in an all-cash transaction valued at approximately $6.5 billion. The acquisition was completed on November 8, 2023, taking the company private after nearly nine years on the public market. Most recently, in May 2024, New Relic formed a partnership with cloud security company Lacework to integrate Cloud Native Application Protection Platform (CNAPP) capabilities into its platform, signaling a deeper push into the security domain.

The New Relic Platform: How It Works

The modern New Relic platform is built around a unified database designed to handle massive volumes of diverse telemetry data.

The Telemetry Data Platform

At the heart of New Relic is the Telemetry Data Platform^[4], a hyper-scale time-series database. It is designed to ingest, store, and query metrics, events, logs, and traces from any source. This unified backend allows users to correlate different data types. For example, a developer can jump from a spike in application latency (metric) to the specific distributed traces that were slow, and then to the logs generated by those exact requests, all within a single interface. Data can be sent to the platform via New Relic's proprietary agents, open standards like OpenTelemetry, or third-party integrations. All data is queryable using the New Relic Query Language (NRQL)^[5], a SQL-like language for analytics and dashboarding.

Core Capabilities

The platform offers a suite of integrated tools that cover the entire software lifecycle.

• Application Performance Monitoring (APM): This is New Relic's foundational product. It uses language-specific agents installed within an application's runtime environment to automatically instrument code. It captures detailed performance data for every transaction, including execution time, database queries, and calls to external services. Its distributed tracing capability stitches together requests as they travel across multiple microservices, providing a complete picture of a user's journey through the system.

• Infrastructure Monitoring: This capability provides visibility into the health and performance of the underlying servers, virtual machines, containers, and cloud services that run applications. It monitors CPU, memory, storage, and network usage. It has deep integrations for Kubernetes, allowing teams to monitor the health of nodes, pods, and deployments, and for major cloud providers like AWS, Azure, and Google Cloud.

• Log Management: New Relic's log management^[6] solution aggregates logs from all components of a system. By bringing logs into the same platform as metrics and traces, it allows developers to see log messages in the context of performance problems, drastically reducing the time it takes to debug issues. Users can search and analyze logs without needing to switch to a separate tool.

• Digital Experience Monitoring: This category focuses on the end-user's experience. It includes Browser Monitoring (also known as Real User Monitoring or RUM), which measures the actual performance experienced by users on a website, tracking metrics like page load times and JavaScript errors. Mobile Monitoring does the same for native iOS and Android applications, tracking app startup times, crashes, and network performance. Synthetic Monitoring complements this by proactively running automated scripts from locations around the world to simulate user journeys and test critical workflows, alerting teams to problems before users are impacted.

• AIOps and Security: New Relic is increasingly incorporating machine learning for its AIOps capabilities, which automatically detect anomalies, reduce alert noise by grouping related incidents, and suggest probable root causes. The recent partnership with Lacework is intended to add security signal correlation to the platform, helping teams identify and respond to threats within the same observability context.

Business Model: From Hosts to Consumption

New Relic's business model has undergone a fundamental transformation. For most of its history, the company used a traditional SaaS subscription model, primarily priced per monitored host, with different tiers for different products. This model became cumbersome as customers adopted microservices and containers, where the concept of a "host" was less meaningful and costs could fluctuate unpredictably.

In July 2020, New Relic announced a radically simplified pricing model designed for the cloud era. The current model has two main components:

1. Data Ingest: The primary cost is based on the amount of data (in gigabytes) ingested into the Telemetry Data Platform each month. The company offers a substantial free tier to encourage broad data collection.
2. User Seats: The second component is a per-user fee. It offers three user types: a free Basic user for simple querying, a mid-tier Core user for developers who need more advanced analysis tools, and a Full Platform user for engineers who need access to all features, including administrative controls.

This model was designed to align the company's revenue with customer value, making pricing more predictable and encouraging users to send all their telemetry data to one place. While intended as a simplification, the transition was disruptive for some existing customers who had to re-evaluate their budgets based on data volume rather than hosts.

Market Position and Competitors

New Relic operates in the highly competitive observability market. For years, it has been recognized by industry analysts as a leader. For example, it was named a Leader in the 2023 Gartner® Magic Quadrant™ for Application Performance Monitoring and Observability. However, it faces intense competition from several key players:

• Datadog: Often considered New Relic's most direct competitor, Datadog has grown rapidly with a similarly broad platform approach covering infrastructure, APM, and logs. It is known for its ease of use and a wide array of integrations.

• Dynatrace: Another long-standing APM leader, Dynatrace has a strong focus on enterprise customers and heavily emphasizes its AI engine, Davis, for automated root cause analysis.

• Splunk: While starting from a log management and security (SIEM) background, Splunk has expanded significantly into observability and APM. It is a formidable competitor, especially in large enterprises where its security products are already entrenched.

• Open Source and Cloud Native: New Relic also competes with open-source solutions like the combination of Prometheus (for metrics), Grafana (for visualization), and Jaeger (for tracing). While requiring more setup and maintenance, these tools are free and highly customizable. Cloud providers like AWS (CloudWatch), Google Cloud (Operations Suite), and Azure (Monitor) also offer native monitoring solutions that present a convenient, albeit sometimes less powerful, alternative.

Strengths and Criticisms

Like any mature technology platform, New Relic has distinct advantages and faces valid criticisms.

Genuine Strengths

• Mature and Deep APM: With over a decade of experience, New Relic's APM product is one of the most feature-rich on the market. Its automated instrumentation and detailed transaction traces are highly valued for deep, code-level diagnostics.

• Unified Data Platform: The single Telemetry Data Platform is a significant architectural strength. The ability to correlate metrics, traces, and logs using a single query language (NRQL) without data silos is a powerful advantage for complex troubleshooting.

• Strong Visualization: The platform's dashboarding and data exploration tools are flexible and powerful. NRQL allows for sophisticated, custom analytics that can be tailored to specific business or operational needs.

Limitations and Reported Criticisms

• Pricing Model Disruption: The 2020 shift to consumption-based pricing was a major point of friction. While a forward-looking move, some long-time customers reportedly faced significant cost increases or found the new model difficult to budget for. The unpredictability of data-based billing remains a concern for cost-sensitive organizations.

• Platform Complexity: While powerful, the breadth of the New Relic platform can be overwhelming. Mastering NRQL and advanced features requires a significant investment in training. Some users, as reported on peer review sites, find the user interface less intuitive than some competitors, particularly for initial setup and basic use cases.

• Post-Acquisition Uncertainty: Going private under new ownership introduces a period of transition. As noted by industry analysts, such changes can lead to shifts in product strategy, research and development priorities, and company culture. Customers and prospects may watch closely to see how the new ownership by Francisco Partners^[7] and TPG^[8] will influence the platform's future direction.

Decision Lens for Technical Leaders

Choosing an observability platform is a significant architectural decision. The right choice depends heavily on an organization's scale, maturity, budget, and philosophy.

Who is New Relic a good fit for?

New Relic is often a strong choice for mid-to-large enterprises that are seeking to consolidate their monitoring tools onto a single, integrated platform. It is particularly well-suited for organizations with complex, distributed microservices architectures where deep distributed tracing is critical. Teams with mature DevOps practices that are prepared to invest time in learning a powerful query language will extract the most value. The generous free tier also makes it an attractive starting point for smaller teams to explore full-stack observability.

Who might consider alternatives?

Early-stage startups or small businesses on a very tight budget might be wary of the consumption-based pricing model's potential for unpredictable costs. They may prefer open-source tools like Prometheus and Grafana or simpler, lower-cost SaaS products. Engineering teams that favor a best-of-breed approach and have the expertise to integrate specialized tools might find a combination of other products more effective. Organizations whose primary need is security monitoring might find a SIEM-first platform like Splunk to be a more natural fit.

Key Tradeoffs to Weigh

A technical leader considering New Relic should weigh several tradeoffs:

• All-in-One vs. Best-of-Breed: Is the operational efficiency of a single, unified platform more valuable than the potential for greater depth from multiple specialized tools? New Relic bets on the former.
• Consumption vs. Subscription: Does your organization prefer the budget predictability of a fixed subscription, or the flexibility of a consumption model that scales with use? The latter requires more diligent cost management.
• Ease of Use vs. Power: New Relic offers a powerful and highly programmable platform, but this comes with a steeper learning curve than some competitors. A team must be willing to invest in training to use its full capabilities.