WIP

src/content/docs/apm/dwm/detailed-page-breakdown.mdx

@@ -7,9 +7,8 @@ metaDescription: Learn about the detailed page breakdown in New Relic's Dynamic
 freshnessValidatedDate: never
 ---
 
-# Detailed Page Breakdown
 
-## Overview
+
 
 ### Entities
 

src/content/docs/apm/dwm/introdution.mdx → src/content/docs/apm/transactions/workload-performance-monitoring/introdution.mdx

@@ -1,5 +1,5 @@
 ---
-title: Introduction to dynamic workload monitoring
+title: Introduction to workload performance monitoring
 tags:
   - transaction workloads
   - dynamic workload monitoring
@@ -19,15 +19,21 @@ New Relic's Dynamic Workload Monitoring (DWM) offers a revolutionary approach to
 
 <Callout variant="important">
 
-You need to enable distributed tracing to use transaction Workloads. Most of the experience is available to everyone; however, the Advanced Maps and Trace Flow map components in the Transaction Workload view require Advanced Compute.
+You need to enable distributed tracing to use workload performance monitoring. Most of the experience is available to everyone; however, the Advanced Maps and Trace Flow map components in the Transaction Workload view require Advanced Compute.
 </Callout>
 
+## Features and benefits
+
+* **Automatic workload construction**: WPM automatically builds workloads based on the focal transaction, eliminating the need for manual setup. It dynamically maps relevant front-end and service entities using distributed tracing and entity relationships.
+
+* ** Comprehensive data integration**: The system integrates critical data from across the platform, including session replays, transaction lists, alert conditions, and deployment changes, providing a holistic view of the workload.
+
+* **Enhanced troubleshooting**: By combining transaction models with distributed tracing, DWM offers an unsampled, accurate view of service performance, enabling users to quickly identify and resolve issues.
+
+## Getting started
+
+To get started with Dynamic Workload Monitoring, you need to enable distributed tracing in your New Relic account. Once enabled, you can access the Transaction Workloads feature from the New Relic One homepage.
 
-## What are transaction workloads? [#feature]
 
-Transaction Workloads are the first implementation of the Dynamic Workload Monitoring feature. The goal is to capture a collection of entities and data that could impact a focal transaction or be impacted by that transaction’s performance. It uses:
 
-- **Focal Transaction**: Sets the primary point of investigation and provides context for relationship mapping.
-- **Distributed Tracing**: Maps service dependencies, tracks transaction flows, and identifies bottlenecks.
-- **Entity Relationships**: Connects related services, maps infrastructure dependencies, and links browser and mobile components.
 

src/content/docs/apm/transactions/workload-performance-monitoring/transaction-workloads.mdx

@@ -0,0 +1,50 @@
+---
+title: Troubleshoot application performance with transaction workloads
+tags:
+  - transaction workloads
+  - dynamic workload monitoring
+metaDescription: Learn about the detailed page breakdown in New Relic's Dynamic Workload Monitoring (DWM) feature.
+freshnessValidatedDate: never
+---
+
+
+When application performance issues arise, it's crucial to have a systematic approach to identify and resolve the root cause. This guide walks you through troubleshooting application performance issues using Workload Performance Monitoring (WPM).
+
+Since WPM automatically captures and correlates all entities and data related to a specific problem or question, it provides a comprehensive view of the workload. This view includes the transaction flow, service relationships, and performance metrics, enabling you to quickly identify and resolve issues.
+
+## Navigate to the Transaction Workloads view
+
+To access the Transaction Workloads view, follow these steps:
+
+1. Go to **[one.newrelic.com](https://one.newrelic.com)> APM and Services**.
+2. From the APM summary page, click **Transactions > Transaction Details > View Transaction workload**.
+
+## Understand the Transaction Workloads view
+
+The Transaction Workloads view provides a detailed breakdown of the transaction workload, including the following components:
+
+* **Trace Flow map**: Visualizes the transaction flow, showing the services involved and the time taken by each service.
+
+* **Service-APM**: Lists the services involved in the transaction workload, along with their performance metrics.
+
+* **Entity Summary** At the top of the page, review the Entity summary. Note the number of entities involved, including Browser entities, APM services, and Infra host entities. Check for any entities missing alerts.
+
+* **Change Tracking:** Examine the Change Tracking section. If only a few change markers are present and located at the left side of the tile, changes are likely not the cause of the issue.
+
+Alerts Analysis: Expand the Alerts tile to analyze alerts by severity and domain. Look for alerts clumped at the right-hand side of the chart, indicating recent issues.
+
+### APM Section
+Response Time Analysis: In the APM section, review the Response time chart. Look for latency spikes across the services. Note any services that do not show spikes, as this may indicate they are not directly affected.
+
+### Transactions Table
+
+Scroll down to the Transactions table to identify transactions with the highest percentage change in response time. Pay attention to transactions from services that are downstream or directly impacted.
+
+### Infra Section
+Infrastructure Analysis: In the Infra section, examine the Related Entities component. Focus on the Hosts table, sorted by CPU Utilization in descending order.
+
+Identify Infrastructure Bottlenecks: Check if any hosts have 100% CPU utilization. If all top hosts are associated with a specific service (e.g., Service 4), this indicates a scaling issue affecting the service's performance.
+
+By following these steps, you can systematically identify and address performance issues within your application. In this example, the investigation revealed that the infrastructure supporting Service 4 was overutilized, causing latency issues that impacted upstream services. Addressing the scaling issue for Service 4 should resolve the performance degradation across the application.
+
+

src/nav/apm.yml

@@ -1292,6 +1292,14 @@ pages:
             path: /docs/apm/transactions/transaction-traces/security-transaction-traces
           - title: Non-web and background transactions
             path: /docs/apm/transactions/intro-transactions/monitor-background-processes-other-non-web-transactions
+
+      - title: Workload performance monitoring
+        pages:
+          - title: Introduction to workload performance monitoring
+            path: /docs/apm/transactions/workload-performance-monitoring/introdution
+          - title: Troubleshoot application perfromance issue with workload performance monitoring
+            path: /docs/apm/transactions/workload-performance-monitoring/transaction-workloads
+
       - title: Key transactions
         pages:
           - title: Guide to key transactions