Skip to main content

New Relic Change Tracking Launched

New Relic launched a change tracking solution that gives engineering teams complete visibility into any change events from across the entire stack.

Engineers can now track any change – from deployments to configuration changes to business events – from any source in context of their performance data to troubleshoot fast and improve deployment efficiency. This latest addition to the platform's 30+ capabilities gives engineers the context to quickly understand the impact of changes, take action to fix problems fast and improve overall deployment efficiency. New Relic change tracking is available to all customers out of the box and included without additional cost for full platform users.

New Relic change tracking gives every engineer the context needed to resolve incidents quickly. It is a systematic way to quickly identify the deployments, configuration changes, and business events that cause instability or downtime in applications and infrastructure.

"Change events are at the root of most software performance degradations and outages, causing alert storms and forcing engineers to work feverishly to restore the system, while simultaneously fielding an influx of requests from stakeholders and customers," said New Relic CGO and GM, Observability Manav Khurana. "With New Relic change tracking, every engineer, regardless of the specialty, can now understand the impact of a change anywhere in the tech stack to take the fiction out of detection and resolution."

Features and benefits of New Relic change tracking include:

- Monitor any change event: Track any change – from deployments to configuration changes to business events – across the entire New Relic ecosystem.

- Connected across your CI/CD toolchain: Automatically mark charts with change details and metadata, and record deployments to NRDB from any source with a brand new GraphQL API, that can be used with any supported CI/CD tools like CircleCI and soon JFrog; New Relic CLI, and plugins with Jenkins and Github Actions.

- Universal access to change markers: See how changes impact software performance across the New Relic platform, including APM, browser, mobile, service levels, custom dashboards, and more.

- Brand new change analysis interface: Interactive, clickable markers hover over performance charts, guiding you to a change analysis interface, helping engineers correlate a change’s effect over time with errors, logs, anomalies, incidents, and more.

- Fast context for change-related incidents: Users can click on a change notification, determine why the change happened, triage the problem—all within New Relic—so your teams can start to roll it back and kickstart a remediation tactic as needed. Teams can easily view deployment changes in context with supported deep links, CI/CD metadata, commit SHAs, related entities, and changes to golden signals.

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

New Relic Change Tracking Launched

New Relic launched a change tracking solution that gives engineering teams complete visibility into any change events from across the entire stack.

Engineers can now track any change – from deployments to configuration changes to business events – from any source in context of their performance data to troubleshoot fast and improve deployment efficiency. This latest addition to the platform's 30+ capabilities gives engineers the context to quickly understand the impact of changes, take action to fix problems fast and improve overall deployment efficiency. New Relic change tracking is available to all customers out of the box and included without additional cost for full platform users.

New Relic change tracking gives every engineer the context needed to resolve incidents quickly. It is a systematic way to quickly identify the deployments, configuration changes, and business events that cause instability or downtime in applications and infrastructure.

"Change events are at the root of most software performance degradations and outages, causing alert storms and forcing engineers to work feverishly to restore the system, while simultaneously fielding an influx of requests from stakeholders and customers," said New Relic CGO and GM, Observability Manav Khurana. "With New Relic change tracking, every engineer, regardless of the specialty, can now understand the impact of a change anywhere in the tech stack to take the fiction out of detection and resolution."

Features and benefits of New Relic change tracking include:

- Monitor any change event: Track any change – from deployments to configuration changes to business events – across the entire New Relic ecosystem.

- Connected across your CI/CD toolchain: Automatically mark charts with change details and metadata, and record deployments to NRDB from any source with a brand new GraphQL API, that can be used with any supported CI/CD tools like CircleCI and soon JFrog; New Relic CLI, and plugins with Jenkins and Github Actions.

- Universal access to change markers: See how changes impact software performance across the New Relic platform, including APM, browser, mobile, service levels, custom dashboards, and more.

- Brand new change analysis interface: Interactive, clickable markers hover over performance charts, guiding you to a change analysis interface, helping engineers correlate a change’s effect over time with errors, logs, anomalies, incidents, and more.

- Fast context for change-related incidents: Users can click on a change notification, determine why the change happened, triage the problem—all within New Relic—so your teams can start to roll it back and kickstart a remediation tactic as needed. Teams can easily view deployment changes in context with supported deep links, CI/CD metadata, commit SHAs, related entities, and changes to golden signals.

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...