Skip to content
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,15 @@ freshnessValidatedDate: never

Transaction 360 automatically captures and correlates all entities and data related to a specific transaction, providing a comprehensive view of your distributed workload. This holistic approach includes transaction flows, service relationships, and performance metrics across your entire stack, enabling you to quickly identify and resolve issues.

## What Transaction 360 shows you
## What Transaction 360 shows you [#what-transaction-360-shows-you]

Transaction 360 provides three main views to help you understand your workload:

- **Overview dashboard**: High-level summary with entity counts, issues, and change tracking
- **Dynamic flow map**: Visual representation of transaction paths and service dependencies
- **Entity breakdown**: Detailed performance metrics for all participating components

## Access Transaction 360
## Access Transaction 360 [#access-transaction-360]

1. Go to **[one.newrelic.com](https://one.newrelic.com) > APM and Services**
2. Select your service from the APM summary page
Expand All @@ -27,27 +27,40 @@ Transaction 360 provides three main views to help you understand your workload:
Database and Serverless monitoring sections are currently available in staging environments. Ensure you have appropriate account permissions and proper instrumentation to access these features.
</Callout>

## Dynamic flow map
## Dynamic flow map [#dynamic-flow-map]

<img
src="/images/dynamic-map.webp"
title="dynamic-map.webp"
alt="dynamic-map.webp"
src="/images/dynamic-flow-map.webp"
/>

The flow map visualizes your transaction's journey through your distributed system:
The Dynamic Flow map is a component within Transaction 360 that visualizes the transaction flow using aggregated trace data. It displays the services involved in the selected transaction and the time taken by each service, using color-coded anomaly indicators to highlight where latency or errors that are correlated with the focal transaction's performance are occurring.

- **Service connections**: See how services communicate and dependencies between them
- **Performance bottlenecks**: Identify slow components affecting overall transaction time
- **Trace relationships**: Click service pairs to view detailed tracing metrics between them

### Collaboration features
- **Team assignment**: Assign teams to transaction workloads for faster incident response
- **Tagging**: Group related entities to streamline investigation and organization
When you click on any service in the map, you can:
* View tracing metrics between the focal transaction and the selected service.
* Review time series charts showing performance trends for both services.
* Assign teams to entities to facilitate collaboration and issue resolution.
* Add tags to entities to streamline the investigation process.

## Entity performance breakdown
The dynamic flow map uses anomaly detection to help you identify which services are directly impacted by performance issues correlated with the focal transaction, enabling you to focus your investigation on the root cause.

**Host analysis:**
- **Resource ranking**: Identify hosts with highest resource consumption.
- **Related services**: See which applications run on each host.

**Collaboration features:**
- **Team assignment**: Assign teams to transaction workloads for faster incident response.
- **Tagging**: Group related entities to streamline investigation and organization.

For more details about Dynamic Flow Map features and capabilities, see [Dynamic Flow Map](/docs/service-architecture-intelligence/maps/dynamic-flow-map).

## Entity performance breakdown [#entity-performance-breakdown]

This section provides detailed metrics for each type of component in your transaction workload:

### APM services
### APM services [#apm-services]

<img
src="/images/partcipating-services.webp"
Expand All @@ -65,25 +78,9 @@ Monitor your application services with:
- **Performance changes**: Transactions with the highest response time changes
- **Trace details**: Click any transaction to view its complete trace flow

### Infrastructure entities

<img
src="/images/infrastructure-entities.webp"
/>

View infrastructure performance for hosts, containers, and Kubernetes clusters:

**Resource metrics:**
- **CPU usage**: Processor utilization across infrastructure
- **Memory consumption**: RAM usage and potential constraints
- **Disk I/O**: Storage performance and bottlenecks
- **Network activity**: Data transfer rates and network issues

**Host analysis:**
- **Resource ranking**: Identify hosts with highest resource consumption
- **Related services**: See which applications run on each host
* **Change tracking:** The number of change tracking markers detected in the transaction workload, indicating changes in the workload's performance. Click **View details** to view the change tracking markers and identify the entities that are directly impacted by the performance changes.

### Browser applications
### Browser applications [#browser-applications]

<img
src="/images/browser-entities.webp"
Expand All @@ -101,7 +98,7 @@ Monitor frontend performance and user experience:
- Click sessions to view detailed user interaction data
- For more details, see [Session Replay documentation](/docs/browser/browser-monitoring/browser-pro-features/session-replay/get-started/)

### Database monitoring
### Database monitoring [#database-monitoring]

Track database performance with comprehensive metrics:

Expand All @@ -124,7 +121,7 @@ Track database performance with comprehensive metrics:
- Click transaction names to filter queries by that transaction
- Access stack traces through individual query details

### Serverless functions
### Serverless functions [#serverless-functions]

Monitor AWS Lambda and other serverless components:

Expand All @@ -139,15 +136,15 @@ Monitor AWS Lambda and other serverless components:
- **Performance impact**: How function performance affects overall transaction speed
- **Resource efficiency**: Memory allocation vs. actual usage

### Mobile applications
### Mobile applications [#mobile-applications]

Track mobile app performance within your transaction flow:

- **App performance**: Response times and user experience metrics
- **Crash rates**: Mobile-specific error tracking
- **Device metrics**: Performance across different mobile devices

### AI/LLM monitoring
### AI/LLM monitoring [#ai-llm-monitoring]

Monitor Large Language Model performance and costs:

Expand All @@ -157,7 +154,7 @@ Monitor Large Language Model performance and costs:

For detailed AI monitoring setup, see [AI monitoring documentation](/docs/ai-monitoring/intro-to-ai-monitoring/).

## Next steps
## Next steps [#next-steps]

After identifying issues in Transaction 360:

Expand Down
Loading
Loading