Skip to content

Commit 7b91ba2

Browse files
git-thuerk-donemaycmlee
git-thuerk-done
and
maycmlee
authored
[DOCS-12675] CNM Glossary (#33123)
* building out CNM Glossary * updates * updating path view * update further reading * move network path * updates * updates to NDM glossary * Apply suggestions from code review Co-authored-by: May Lee <[email protected]> * fix network map --------- Co-authored-by: May Lee <[email protected]>
1 parent 6cf1b43 commit 7b91ba2

File tree

4 files changed

+156
-29
lines changed

4 files changed

+156
-29
lines changed

‎config/_default/menus/main.en.yaml‎

Lines changed: 35 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -3631,41 +3631,46 @@ menu:
36313631
parent: nm_parent
36323632
identifier: cnm
36333633
weight: 1
3634+
- name: CNM Terms and Concepts
3635+
url: network_monitoring/cloud_network_monitoring/glossary
3636+
parent: cnm
3637+
identifier: cnm_glossary
3638+
weight: 101
36343639
- name: Setup
36353640
url: network_monitoring/cloud_network_monitoring/setup/
36363641
parent: cnm
36373642
identifier: cnm_setup
3638-
weight: 101
3643+
weight: 102
36393644
- name: Network Health
36403645
url: network_monitoring/cloud_network_monitoring/network_health/
36413646
parent: cnm
36423647
identifier: cnm_network_health
3643-
weight: 102
3648+
weight: 103
36443649
- name: Network Analytics
36453650
url: network_monitoring/cloud_network_monitoring/network_analytics/
36463651
parent: cnm
36473652
identifier: cnm_analytics
3648-
weight: 103
3653+
weight: 104
36493654
- name: Tags Reference
36503655
url: network_monitoring/cloud_network_monitoring/tags_reference/
36513656
parent: cnm_analytics
36523657
identifier: cnm_analytics_tags_reference
3653-
weight: 10000
3658+
weight: 10401
36543659
- name: Network Map
36553660
url: network_monitoring/cloud_network_monitoring/network_map/
36563661
parent: cnm
36573662
identifier: cnm_map
3658-
weight: 104
3663+
weight: 105
36593664
- name: Guides
36603665
url: network_monitoring/cloud_network_monitoring/guide/
36613666
identifier: cnm_guides
36623667
parent: cnm
3663-
weight: 105
3668+
weight: 106
36643669
- name: Supported Cloud Services
36653670
url: network_monitoring/cloud_network_monitoring/supported_cloud_services/
36663671
identifier: cnm_supported_cloud_services
36673672
parent: cnm
3668-
weight: 106
3673+
weight: 10601
36693674
- name: DNS Monitoring
36703675
url: network_monitoring/dns/
36713676
parent: nm_parent
@@ -3675,7 +3680,7 @@ menu:
36753680
url: network_monitoring/devices
36763681
parent: nm_parent
36773682
identifier: ndm
3678-
weight: 3
3683+
weight: 3
36793684
- name: NDM Terms and Concepts
36803685
url: network_monitoring/devices/glossary
36813686
parent: ndm
@@ -3690,67 +3695,67 @@ menu:
36903695
url: network_monitoring/devices/supported_devices
36913696
parent: ndm_setup
36923697
identifier: ndm_supported_devices
3693-
weight: 30001
3698+
weight: 30301
36943699
- name: SNMP Metrics
36953700
url: network_monitoring/devices/snmp_metrics
36963701
parent: ndm_setup
36973702
identifier: ndm_snmp_metrics
3698-
weight: 30002
3703+
weight: 30302
36993704
- name: SNMP Traps
37003705
url: network_monitoring/devices/snmp_traps
37013706
parent: ndm_setup
37023707
identifier: ndm_snmptraps
3703-
weight: 30003
3708+
weight: 30303
37043709
- name: Ping
37053710
url: network_monitoring/devices/ping
37063711
parent: ndm_setup
37073712
identifier: ndm_snmp_ping
3708-
weight: 30004
3713+
weight: 30304
37093714
- name: Syslog
37103715
url: network_monitoring/devices/syslog
37113716
parent: ndm_setup
37123717
identifier: ndm_syslog
3713-
weight: 30005
3718+
weight: 30305
37143719
- name: VPN Monitoring
37153720
url: network_monitoring/devices/vpn_monitoring
37163721
parent: ndm_setup
37173722
identifier: ndm_vpn_monitoring
3718-
weight: 30006
3723+
weight: 30306
37193724
- name: Integrations
37203725
url: network_monitoring/devices/integrations
37213726
parent: ndm
37223727
identifier: ndm_integrations
3723-
weight: 303
3728+
weight: 304
37243729
- name: Profiles
37253730
url: network_monitoring/devices/profiles
37263731
parent: ndm
37273732
identifier: ndm_profiles
3728-
weight: 304
3733+
weight: 305
37293734
- name: Configuration Management
37303735
url: network_monitoring/devices/config_management
37313736
parent: ndm
37323737
identifier: ndm_config_management
3733-
weight: 305
3738+
weight: 306
37343739
- name: Maps
37353740
url: network_monitoring/devices/topology
37363741
parent: ndm
37373742
identifier: ndm_network_maps
3738-
weight: 306
3743+
weight: 307
37393744
- name: SNMP Metrics Reference
37403745
url: network_monitoring/devices/data
37413746
parent: ndm
37423747
identifier: ndm_data
3743-
weight: 307
3748+
weight: 308
37443749
- name: Troubleshooting
37453750
url: network_monitoring/devices/troubleshooting
37463751
parent: ndm
37473752
identifier: ndm_trouble
3748-
weight: 308
3753+
weight: 309
37493754
- name: Guides
37503755
url: network_monitoring/devices/guide/
37513756
parent: ndm
37523757
identifier: ndm_guide
3753-
weight: 309
3758+
weight: 310
37543759
- name: NetFlow Monitoring
37553760
url: /network_monitoring/netflow/
37563761
parent: nm_parent
@@ -3766,26 +3771,31 @@ menu:
37663771
parent: nm_parent
37673772
identifier: network_path
37683773
weight: 5
3774+
- name: Terms and Concepts
3775+
url: network_monitoring/network_path/glossary
3776+
parent: network_path
3777+
identifier: network_path_glossary
3778+
weight: 501
37693779
- name: Setup
37703780
url: network_monitoring/network_path/setup/
37713781
parent: network_path
37723782
identifier: network_path_setup
3773-
weight: 501
3783+
weight: 502
37743784
- name: List View
37753785
url: network_monitoring/network_path/list_view/
37763786
parent: network_path
37773787
identifier: network_path_list_view
3778-
weight: 502
3788+
weight: 503
37793789
- name: Path View
37803790
url: network_monitoring/network_path/path_view/
37813791
parent: network_path
37823792
identifier: network_path_path_view
3783-
weight: 503
3793+
weight: 504
37843794
- name: Guides
37853795
url: network_monitoring/network_path/guide
37863796
parent: network_path
37873797
identifier: network_path_guides
3788-
weight: 504
3798+
weight: 505
37893799
- name: Storage Management
37903800
url: /infrastructure/storage_management/
37913801
pre: file-wui

‎content/en/network_monitoring/cloud_network_monitoring/glossary.md‎

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: CNM Terms and Concepts
3+
description: Glossary for Cloud Network Monitoring (CNM)
4+
further_reading:
5+
- link: '/network_monitoring/cloud_network_monitoring/setup/'
6+
tag: 'Documentation'
7+
text: 'Setting Up Cloud Network Monitoring'
8+
- link: '/network_monitoring/cloud_network_monitoring/tags_reference/'
9+
tag: 'Documentation'
10+
text: 'CNM Tags Reference'
11+
- link: '/monitors/types/cloud_network_monitoring/'
12+
tag: 'Documentation'
13+
text: 'CNM Monitors and Alerts'
14+
- link: '/network_monitoring/network_path/glossary'
15+
tag: 'Documentation'
16+
text: 'Network Path Glossary'
17+
---
18+
19+
## Overview
20+
21+
Cloud Network Monitoring (CNM) provides end-to-end visibility into network communication across services, containers, hosts, and cloud environments. It aggregates connection-level data into meaningful service-to-service dependencies, helping you analyze traffic patterns, troubleshoot latency and connectivity issues, and monitor the health of your applications.
22+
23+
For additional definitions and descriptions of important CNM terms such as _policy based routing_, see the [main Glossary][6].
24+
25+
## Terminology
26+
27+
| Concept | Description |
28+
| ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
29+
| **Cloud Network Monitoring (CNM)** | Cloud Network Monitoring (CNM) provides visibility into network traffic between services, containers, availability zones, and other tags in Datadog, aggregating raw connection-level data (IP, port, PID) into application-layer dependencies between client and server endpoints. |
30+
| **Flow data** | The low-level data collected by CNM (connections at IP, port, PID levels) that CNM uses to build higher-level representations of network dependencies and traffic flow. |
31+
| **Network Address Translation (NAT)** | A method for remapping one IP address to another. This allows multiple devices on a private network to share a single public IP address to connect to the internet. |
32+
| **[Network Health][1]** | Displays the overall health of network connections, surfacing connectivity problems and degraded network performance across hosts and services. |
33+
| **[Network Analytics][2]** | A CNM view that lets you graph and analyze network data between each client and server based on grouping tags, so you can investigate traffic patterns, dependencies, or anomalies. |
34+
| **[Network Map][3]** | A visualization view in CNM that maps network data between tags such as `service`, `kube_service`, `short_image`, and `container_name`. |
35+
| **[CNM Monitor][4]** | A Datadog monitor that alerts when a CNM (TCP network) metric crosses a user-defined threshold, for example network throughput between a specific client and server. |
36+
| **[CNM tags][5]** | Tags that CNM uses to group and display traffic, for example, service-to-service or zone-to-zone communication. |
37+
| **[Traffic volume][9] (Bytes Sent and Received)** | A primary network metric in CNM representing the amount of data transferred between endpoints. Often visualized in the network load section of dashboards or the network analytics page to spot spikes or traffic bottlenecks. |
38+
| **[TCP metrics][8] (Connections, Retransmits, Latency)** | Metrics CNM tracks for TCP flows, including open and closed connections, packet retransmissions, and round-trip time to detect connectivity issues, packet loss, or network congestion. |
39+
| **[Unresolved or NA traffic][10]** | Network flows that cannot be associated with defined tags (client or server). Often shown as "unresolved" or "NA," indicating that the origin or destination cannot be identified or grouped meaningfully. |
40+
41+
## Further Reading
42+
43+
{{< partial name="whats-next/whats-next.html" >}}
44+
45+
[1]: /network_monitoring/cloud_network_monitoring/network_health/
46+
[2]: /network_monitoring/cloud_network_monitoring/network_analytics/
47+
[3]: /network_monitoring/cloud_network_monitoring/network_map/
48+
[4]: /monitors/types/cloud_network_monitoring/
49+
[5]: /network_monitoring/cloud_network_monitoring/tags_reference/
50+
[6]: /glossary/?product=cloud-network-monitoring
51+
[8]: /network_monitoring/cloud_network_monitoring/network_analytics/#tcp
52+
[9]: /network_monitoring/cloud_network_monitoring/network_analytics/#network-load
53+
[10]: /network_monitoring/cloud_network_monitoring/network_analytics/#unresolved-traffic

‎content/en/network_monitoring/devices/glossary.md‎

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,14 +9,20 @@ further_reading:
99

1010
## Overview
1111

12-
Network Device Monitoring helps you gain insights into the health and performance of your on-prem routers, switches, and firewalls.
12+
Network Device Monitoring (NDM) helps you gain insights into the health and performance of your on-prem routers, switches, and firewalls.
1313
For additional definitions and descriptions of important NDM terms such as _layer 2_ and _layer 3_, see the main [Glossary][1].
1414

1515
## Terminology
1616

1717
Simple network management protocol (SNMP)
1818
: A network protocol that is used to collect information about bare metal networking gear.
1919

20+
Link Layer Discovery Protocol (LLDP)
21+
: A protocol used by devices to advertise identity and capabilities to neighboring devices. NDM uses LLDP to map topology.
22+
23+
Managed information base (MIB)
24+
: A database or list of all the possible OIDs and their definitions that are related to the MIB. For example, the `IF-MIB` (interface MIB) contains all the OIDs for descriptive information about a device's interface.
25+
2026
Object identifier (OID)
2127
: A unique ID or address on a device that when polled returns the response code of that value. For example, OIDs are CPU or device fan speed.
2228

@@ -35,14 +41,15 @@ Software-defined wide area network (SD-WAN)
3541
[Device namespaces][3]
3642
: Namespace of the device. Namespaces can be used as tags to differentiate between multiple network devices that may share the same private IP.
3743

38-
Ping
44+
[Ping][4]
3945
: A network tool that measures how long it takes for a signal to travel from one device to another over a network and back again.
4046

4147

4248
## Further Reading
4349

4450
{{< partial name="whats-next/whats-next.html" >}}
4551

46-
[1]: /glossary/
52+
[1]: /glossary/?product=network-device-monitoring
4753
[2]: /network_monitoring/devices/profiles
48-
[3]: /network_monitoring/devices/snmp_traps/?tab=yaml#device-namespaces
54+
[3]: /network_monitoring/devices/snmp_traps/?tab=yaml#device-namespaces
55+
[4]: /network_monitoring/devices/ping

‎content/en/network_monitoring/network_path/glossary.md‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
title: Network Path Terms and Concepts
3+
description: Glossary for Network Path
4+
further_reading:
5+
- link: '/network_monitoring/cloud_network_monitoring/setup/'
6+
tag: 'Documentation'
7+
text: 'Setting Up Cloud Network Monitoring'
8+
- link: '/network_monitoring/cloud_network_monitoring/tags_reference/'
9+
tag: 'Documentation'
10+
text: 'CNM Tags Reference'
11+
- link: '/monitors/types/cloud_network_monitoring/'
12+
tag: 'Documentation'
13+
text: 'CNM Monitors and Alerts'
14+
---
15+
16+
## Network Path
17+
18+
Network Path provides hop-by-hop visibility into the route between a source and destination, helping you identify where latency, packet loss, or routing changes occur.
19+
20+
## Terminology
21+
| Concept | Description |
22+
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
23+
| **[Network Path][6]** | Network Path provides hop-by-hop visibility into the route between a source and a destination, so you can identify where latency, packet loss, or routing changes occur. |
24+
| **Autonomous System (AS / ASN)** | A collection of IP routing prefixes managed by a single network operator. Network Path groups hop by Autonomous System (AS) or Autonomous System Number (ASN) to show routing domains along the path.
25+
| **[Path View][7]** | The Network Path visualization that displays each hop, grouped by Autonomous System Number (ASN), region, or network, along with probe status and hop metrics. |
26+
| **Hop** | A network node along a route between source and destination, identified by IP address and associated metadata (ASN, cloud region, provider). | |
27+
| **Source** | The starting point of a Network Path probe, typically an Agent-monitored host or container running the Datadog network monitoring tracer. |
28+
| **Destination** | The endpoint that the Network Path probe is targeting, such as a service, public endpoint, or domain. |
29+
| **Traceroute** | The mechanism that Network Path uses to determine intermediate hops and latency. CNM sends controlled probes, similar to traceroute, to discover each hop on the route. |
30+
| **Latency per hop** | The round-trip time between the probe source and each hop. This helps identify slow or congested nodes. |
31+
| **Packet loss per hop** | The percentage of probe packets dropped before reaching or returning from a hop, useful for diagnosing reliability issues. |
32+
33+
### Path View
34+
| Concept | Description |
35+
| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
36+
| **Aggregated hop** | A group of multiple identical hops (same IP, ASN, region), collapsed into a single representation to simplify visualization. |
37+
| **ICMP timeout or no response** | A hop where no ICMP response was received. Often appears as a gray or unknown hop in the Path View. |
38+
| **Missing hop** | A point in the path where the probe cannot identify a network node, often due to firewall filtering, ICMP rate limits, or private routing. Displayed as a dashed or empty hop. |
39+
| **Path change indicator** | A visual marker that shows when the observed route changes over time, for example an AS shift or a new hop. |
40+
| **AS grouping** | The cluster of hops belonging to the same Autonomous System, helping identify which network operator controls each segment of the path. |
41+
| **Region grouping** | The cluster of hops located within the same cloud region or geographic region. Helpful for identifying inter-regional routing.
42+
| **Start node** | The initial node (source) where the probe begins. Represented at the far left of the Path View. |
43+
| **End node** | The destination node where the probe terminates. Represented at the far right of the Path View. |
44+
| **Hop status indicator** | The icon or color indicating whether the hop is healthy, degraded, or unreachable, based on latency and loss. |
45+
| **Probe status** | Shows whether the probe reached a hop successfully, partially, or not at all. This helps you identify where traffic stops or degrades. | |
46+
| **Traversed count** | Represents the number of traceroute active probing packets received by reach hop. Higher counts suggest that the hop is consistently part of the route; lower counts may indicate path instability. |
47+
| **Traversal completion** | Represents whether or not the traceroute was able to successfully reach the destination. |
48+
| **Reachability** | The level of packet loss the destination is experiencing. |
49+
| **Latency** | How long the traceroute took to get from a source to its destination. |
50+
51+
52+
## Further Reading
53+
54+
{{< partial name="whats-next/whats-next.html" >}}
55+
56+
[6]: /network_monitoring/network_path/
57+
[7]: /network_monitoring/network_path/path_view

0 commit comments

Comments
 (0)