Fast-Track Incident Resolution with Transaction 360

Modern applications have become increasingly complex, featuring interconnected services and diverse components, including serverless functions, databases, AI models, and more. Traditional monitoring tools often struggle to deliver the unified visibility required to diagnose and resolve issues swiftly, resulting in increased downtime and business impact.

With New Relic’s Transaction 360—the industry's first transaction-centric observability solution designed to streamline and accelerate troubleshooting for business-critical transactions. Transaction 360 automatically correlates data across all relevant components and provides a comprehensive view of your entire application ecosystem, Transaction 360 significantly enhances the core capabilities of the New Relic One platform.

Automatic Dynamic Workload Creation: Reducing Data Overload

Developers and DevOps teams often face data overload when critical incidents arise, wasting valuable time navigating fragmented dashboards. Transaction 360 automatically aggregates entities, telemetry, alerts, and relevant changes associated with problematic transactions into one unified dynamic workload view. This approach reduces complexity and accelerates the identification of issues.

How we do it:
When an incident occurs, Transaction 360 immediately compiles all related telemetry and entities—from infrastructure to browser-level interactions—creating a consolidated view that eliminates the need to switch between multiple dashboards.

Aggregate Workload Change View: Analyze Deployments in Context

Isolating the impact of deployments and configuration changes across numerous interconnected services can be a time-consuming process. Transaction 360 provides an aggregated view of recent changes across all relevant entities, enabling teams to understand how these alterations impact overall transaction performance quickly.

Practical example:
If your checkout transaction suddenly slows down after a deployment, Transaction 360 pinpoints exactly which services were impacted by recent changes, enabling faster rollback or fixes.

Comprehensive Trace Flow Map: Full-Stack, Cross-Service Observability

Existing observability solutions often offer only partial snapshots or limited timeframes for troubleshooting transaction issues. Transaction 360 leverages combined distributed tracing (DT) and transaction tracing data to present a comprehensive and unsampled flow map. This full-stack visibility spans more extended historical periods—days or even weeks—rather than the typical limited windows (15-minute snapshots) offered by competitors.

Impact:
This comprehensive historical view enables teams to quickly identify when issues started, significantly accelerating root-cause analysis and reducing downtime.

AI-Powered Anomaly Detection and Proactive Alerts

Manual monitoring of complex transactions is impractical, leading to reactive rather than proactive responses. Transaction 360 incorporates advanced, AI-powered anomaly detection to identify potential issues before they escalate automatically. Automated alerts ensure rapid team engagement, dramatically reducing the mean time to detect and respond (MTTD/R).

Result:
Your team can proactively maintain performance stability, safeguarding user experience and revenue continuity.

Part 3: Getting Started

Getting started with Transaction 360 is straightforward:

Step 1: Enable Distributed Tracing

• Navigate to your New Relic account settings and enable distributed tracing, which is required to leverage Transaction 360's capabilities.

Step 2: Access Transaction 360 View

• Log into New Relic One.
• Go to APM and Services > Transactions > Transaction Details > View transaction 360 workload.

Step 3: Explore and Analyze

• Utilize the dynamic flow map for an intuitive visualization of transaction paths.
• Investigate participating entities, performance metrics, and infrastructure insights within the comprehensive Transaction 360 dashboard.

For more detailed guidance, explore the Transaction 360 Documentation.