AWS veteran Nandini Ramani wants to lead New Relic into its agentic era, but must move quickly to remain competitive in a rapidly evolving observability market, experts said.
New Relic has had a tumultuous few years. Since 2020, the company has undergone several waves of consolidation, numerous pricing changes, a private equity buyout and three separate CEOs prior to Ramani taking the helm in October. There have also been several other C-suite switch-ups, with the chief financial, revenue and products officers all shuffling since 2024. Ramani succeeded former CEO Ashan Willy, who will serve as an advisor on the company's board of directors.
"This is not the continuity customers expect," said Torsten Volk, principal analyst at Omdia, a division of Informa TechTarget. "At the same time, the investment in new talent has lagged behind their major competitors. This is a frequent symptom of private equity taking over. On the plus side, Ramani brings exactly the experience needed to move the needle."
That experience includes leadership roles at Twitter, Oracle and Sun Microsystems. In her most recent stint – 5 ½ years at AWS – she oversaw a portfolio of cloud operations and observability services, including Amazon CloudWatch, OpenSearch and CloudTrail.
In reflecting on what's next for New Relic, Ramani highlighted its history as a disruptor – originally flipping the observability model by starting at the application layer and tracing down to logs, rather than the traditional logs-up approach. She sees New Relic's next opportunity as repeating this kind of disruption for the agentic era.
“[The observability market] is so competitive, but I feel like it's ripe for the next disruption," Ramani said. "[New Relic's previous era of disruption] was very developer-led. It really resonated and organically grew, unlike some of the others. When I talk to customers, they're looking to us to do the same type of disruption in a world where they are also trying to figure out what agents mean to them."
Ramani's experience overseeing CloudWatch at AWS gives her insight into the competitive pressures New Relic faces, but translating that knowledge into a distinct value proposition will be an immediate challenge, according to Volk.
"On one side there are strong competitors like Datadog and Dynatrace offering easy-to-use platforms with a wider set of capabilities. On the other side, hyperscalers [are increasingly creating] their own hybrid observability platforms, like AWS CloudWatch Omni. At the same time, the competition has been heavily investing in observability and evaluation capabilities for agents, a gap that New Relic needs to close fast," Volk said.
The competition has been heavily investing in observability and evaluation capabilities for agents, a gap that New Relic needs to close fast.

Torsten Volk
Principal analyst at Omdia
Ramani's background at AWS will give her two characteristics important to competing in today's frantic observability market, said Rob Strechay, an analyst at VB Intelligence.
"First, she will drive a lean innovation agenda, as she did at AWS," Strechay said. "Second, she is well connected to the cloud ecosystem and will know which gaps to focus on to rival folks like Datadog and Dynatrace, who have strong hyperscaler relationships."
First order of business at New Relic
New Relic's immediate priorities are to support agentic software development better internally and on its external platform, and to continue investing in core observability functions, Ramani said.
"We have a skills repository. Now, skills are not good enough. You need an agent swarm to do your job for you. Tomorrow it will be something else. I just want to create both a culture and the processes internally so we can run with velocity and adapt," Ramani said.
I just want to create both a culture and the processes internally so we can run with velocity and adapt.

Nandini Ramani
CEO at New Relic
To keep up with the relentless pace of change, New Relic will also pursue an extensible headless architecture for observability – one that does not require a UI or dashboards – to enable agents to consume insights at machine speed while also making them accessible to humans.
"Core observability as we know it, which is logs, metrics, traces, events – that's not going away. That was consumed mostly by humans to date. However, we now have agents that can operate 24/7 with no dashboards. [They don't] need any UI at all," Ramani said. "You can have MCPs talking; you can have [agent-to-agent protocol]. At the end of the day, you want to have good headless architecture that agents can connect to – it's extensible."
It's also important to ensure that observability data is accessible to the human in the loop using on-the-fly dashboards, Ramani said.
"The world of what we know as dashboards is changing," she said. "[Customers] really want to be design partners in figuring out what the next thing looks like."
Eventually, the plan is to pursue autonomous remediation in the platform – a pursuit undertaken by competitors like Datadog, Dynatrace and Groundcover – as well as "shifting-left" to prevent problems in the code.
"We are already in the infrastructure. We already have access to these things. The question is how do I remediate and give you confidence that I'm going to do it [proactively] without changing everything in your estate?" she said, noting that customers prefer a tiered approach where they gradually trust the agents with more important tasks.
New Relic launched its Autopilot Kubernetes Agent on Nov. 10, which is a fleet of SRE agents that automatically pinpoints root causes and generates a fix for humans to review and deploy.
Ramani also highlighted New Relic's unified data architecture as a competitive advantage.
"We did not grow through acquisitions and a bolted-on strategy, unlike others. We speak one language throughout, whether it's metrics, logs, traces, [or] events," she said.
New Relic customers focused on cost and complexity
Even as observability vendors push to add agentic features, the real differentiators are cost and lock-in, said Akash Thakur, an independent SRE & reliability architect and IEEE senior member.
"As systems scale, the data-volume-based pricing on these platforms can grow faster than teams expect, and that's often what drives a re-evaluation more than any missing capability," he said, noting that Datadog and Dynatrace have similar pricing models that grow with scale.
"Pricing is a challenge across the whole market," said Suresh Gangula, a DevOps engineer at Nike. "Pricing grows with users and data volume, so at scale teams have to actively manage what they send."
Gangula's team uses the open standard OpenTelemetry to collect metrics, logs and traces from apps and infrastructure, then feed them to New Relic for application monitoring and SignalFx for real-time infrastructure metrics.
"Vendors like New Relic have their own [collectors], but we use OpenTelemetry instead. That keeps our data collection vendor neutral, so we can change or add tools without re-instrumenting our apps," Gangula said. The organization used to use New Relic's collectors, but gradually switched to OpenTelemetry over time, in part because of cost.
"The harder part is working across several tools: different dashboards, different alert rules and keeping service names and tags consistent so data can be compared," Gangula said, noting that he'd like to see better integrations and smarter grouping of related alerts to reduce noise across tools.
New Relic's strategy reflects the reality that customers already use multiple observability tools, and that the company must offer differentiated capabilities without requiring them to abandon existing investments, Ramani said.
"If that's a durable differentiation for the customer and we meet them where they are to extend, then, when it makes sense, they will switch," Ramani said. "That is the approach that AWS takes, and I'm bringing that tenant with me because I'm a big believer that you meet the customer wherever they are."
Ben Lutkevich is an award-winning writer at TechTarget.com.