CNM - Add Traces tab to sidepanel section

[jeff-morgan-dd]

What does this PR do? What is the motivation?

Fixes DOCS-14106, adding a Traces tab to the Sidepanel section of the page.

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

AI assistance

First draft from Claude.

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/jeff.morgan/DOCS-14106-npm-apm/network_monitoring/cloud_network_monitoring/network_analytics

[kcaiddgit]

The Autonomous Systems (AS) View shows which Autonomous Systems carry your Network Path traffic, and how traffic flows between them. Use this view to identify which service providers handle your traffic and to examine the upstream and downstream relationships between Autonomous Systems.

Suboptimal Border Gateway Patrol (BGP) routes and issues with specific providers are often the root cause of performance degradation. The Autonomous Systems (AS) View maps BGP relationships for the Autonomous Systems in your paths, providing detailed insight into issue origination.

Select Autonomous Systems (AS) in the Network Path Explorer to get started.

Update version:
The Autonomous Systems (AS) View provides visibility into the network providers and Internet Service Providers that carry your traffic across the BGP(Border Gateway Protocol) routing layer. This view monitors latency and performance metrics for every AS in your network paths, helping you pinpoint exactly which upstream providers are experiencing issues when your network performance degrades.

The dashboard surfaces performance data through several lenses. The global blast radius map visualizes latency distribution by country, immediately showing you which geographic regions are experiencing higher latency. The traffic distribution panel breaks down what percentage of your paths traverse each region, while the traffic categories panel shows whether your traffic primarily flows through hosting providers or traditional ISPs. The "Need Attention" section automatically flags ASes with latency spikes or performance anomalies, ranking them by severity so you know where to focus your investigation.

The detailed AS table provides the operational data you need for troubleshooting: which prefixes each AS announces, how many of your monitored paths traverse that AS, and what specific issues have been detected (latency spikes, routing changes, or connectivity problems). You can filter by AS number, country, traffic category, or issue type to narrow your investigation. When a customer reports degraded performance, you can quickly determine whether the issue originates with your infrastructure, a specific transit provider, or a last-mile ISP—critical information for escalating to the right team or vendor.

BGP routing issues and provider-specific problems are difficult to diagnose because they sit outside your direct control. The AS View makes these invisible layers visible, giving you the data to answer questions like "Is this a peering issue?" or "Did our traffic shift to a different transit provider?" without manually tracing routes or parsing BGP tables.

Select Autonomous Systems (AS) in the Network Path to get started.

[jeff-morgan-dd]

The Autonomous Systems (AS) View shows which Autonomous Systems carry your Network Path traffic, and how traffic flows between them. Use this view to identify which service providers handle your traffic and to examine the upstream and downstream relationships between Autonomous Systems.

Suboptimal Border Gateway Patrol (BGP) routes and issues with specific providers are often the root cause of performance degradation. The Autonomous Systems (AS) View maps BGP relationships for the Autonomous Systems in your paths, providing detailed insight into issue origination.

Select Autonomous Systems (AS) in the Network Path Explorer to get started.

Update version: The Autonomous Systems (AS) View provides visibility into the network providers and Internet Service Providers that carry your traffic across the BGP(Border Gateway Protocol) routing layer. This view monitors latency and performance metrics for every AS in your network paths, helping you pinpoint exactly which upstream providers are experiencing issues when your network performance degrades.

The dashboard surfaces performance data through several lenses. The global blast radius map visualizes latency distribution by country, immediately showing you which geographic regions are experiencing higher latency. The traffic distribution panel breaks down what percentage of your paths traverse each region, while the traffic categories panel shows whether your traffic primarily flows through hosting providers or traditional ISPs. The "Need Attention" section automatically flags ASes with latency spikes or performance anomalies, ranking them by severity so you know where to focus your investigation.

The detailed AS table provides the operational data you need for troubleshooting: which prefixes each AS announces, how many of your monitored paths traverse that AS, and what specific issues have been detected (latency spikes, routing changes, or connectivity problems). You can filter by AS number, country, traffic category, or issue type to narrow your investigation. When a customer reports degraded performance, you can quickly determine whether the issue originates with your infrastructure, a specific transit provider, or a last-mile ISP—critical information for escalating to the right team or vendor.

BGP routing issues and provider-specific problems are difficult to diagnose because they sit outside your direct control. The AS View makes these invisible layers visible, giving you the data to answer questions like "Is this a peering issue?" or "Did our traffic shift to a different transit provider?" without manually tracing routes or parsing BGP tables.

Select Autonomous Systems (AS) in the Network Path to get started.

Thanks for this, Kai - i've pasted this into a comment on the BGP PR for visibility.

[domalessi]

Two minor suggestions but approved!