diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 87218bf55e6..726e26d20ec 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -3611,41 +3611,46 @@ menu: parent: nm_parent identifier: cnm weight: 1 + - name: CNM Terms and Concepts + url: network_monitoring/cloud_network_monitoring/glossary + parent: cnm + identifier: cnm_glossary + weight: 101 - name: Setup url: network_monitoring/cloud_network_monitoring/setup/ parent: cnm identifier: cnm_setup - weight: 101 + weight: 102 - name: Network Health url: network_monitoring/cloud_network_monitoring/network_health/ parent: cnm identifier: cnm_network_health - weight: 102 + weight: 103 - name: Network Analytics url: network_monitoring/cloud_network_monitoring/network_analytics/ parent: cnm identifier: cnm_analytics - weight: 103 + weight: 104 - name: Tags Reference url: network_monitoring/cloud_network_monitoring/tags_reference/ parent: cnm_analytics identifier: cnm_analytics_tags_reference - weight: 10000 + weight: 10401 - name: Network Map url: network_monitoring/cloud_network_monitoring/network_map/ parent: cnm identifier: cnm_map - weight: 104 + weight: 105 - name: Guides url: network_monitoring/cloud_network_monitoring/guide/ identifier: cnm_guides parent: cnm - weight: 105 + weight: 106 - name: Supported Cloud Services url: network_monitoring/cloud_network_monitoring/supported_cloud_services/ identifier: cnm_supported_cloud_services parent: cnm - weight: 106 + weight: 10601 - name: DNS Monitoring url: network_monitoring/dns/ parent: nm_parent @@ -3655,7 +3660,7 @@ menu: url: network_monitoring/devices parent: nm_parent identifier: ndm - weight: 3 + weight: 3 - name: NDM Terms and Concepts url: network_monitoring/devices/glossary parent: ndm @@ -3670,67 +3675,67 @@ menu: url: network_monitoring/devices/supported_devices parent: ndm_setup identifier: ndm_supported_devices - weight: 30001 + weight: 30301 - name: SNMP Metrics url: network_monitoring/devices/snmp_metrics parent: ndm_setup identifier: ndm_snmp_metrics - weight: 30002 + weight: 30302 - name: SNMP Traps url: network_monitoring/devices/snmp_traps parent: ndm_setup identifier: ndm_snmptraps - weight: 30003 + weight: 30303 - name: Ping url: network_monitoring/devices/ping parent: ndm_setup identifier: ndm_snmp_ping - weight: 30004 + weight: 30304 - name: Syslog url: network_monitoring/devices/syslog parent: ndm_setup identifier: ndm_syslog - weight: 30005 + weight: 30305 - name: VPN Monitoring url: network_monitoring/devices/vpn_monitoring parent: ndm_setup identifier: ndm_vpn_monitoring - weight: 30006 + weight: 30306 - name: Integrations url: network_monitoring/devices/integrations parent: ndm identifier: ndm_integrations - weight: 303 + weight: 304 - name: Profiles url: network_monitoring/devices/profiles parent: ndm identifier: ndm_profiles - weight: 304 + weight: 305 - name: Configuration Management url: network_monitoring/devices/config_management parent: ndm identifier: ndm_config_management - weight: 305 + weight: 306 - name: Maps url: network_monitoring/devices/topology parent: ndm identifier: ndm_network_maps - weight: 306 + weight: 307 - name: SNMP Metrics Reference url: network_monitoring/devices/data parent: ndm identifier: ndm_data - weight: 307 + weight: 308 - name: Troubleshooting url: network_monitoring/devices/troubleshooting parent: ndm identifier: ndm_trouble - weight: 308 + weight: 309 - name: Guides url: network_monitoring/devices/guide/ parent: ndm identifier: ndm_guide - weight: 309 + weight: 310 - name: NetFlow Monitoring url: /network_monitoring/netflow/ parent: nm_parent @@ -3746,26 +3751,31 @@ menu: parent: nm_parent identifier: network_path weight: 5 + - name: Terms and Concepts + url: network_monitoring/network_path/glossary + parent: network_path + identifier: network_path_glossary + weight: 501 - name: Setup url: network_monitoring/network_path/setup/ parent: network_path identifier: network_path_setup - weight: 501 + weight: 502 - name: List View url: network_monitoring/network_path/list_view/ parent: network_path identifier: network_path_list_view - weight: 502 + weight: 503 - name: Path View url: network_monitoring/network_path/path_view/ parent: network_path identifier: network_path_path_view - weight: 503 + weight: 504 - name: Guides url: network_monitoring/network_path/guide parent: network_path identifier: network_path_guides - weight: 504 + weight: 505 - name: Storage Management url: /infrastructure/storage_management/ pre: file-wui diff --git a/content/en/network_monitoring/cloud_network_monitoring/glossary.md b/content/en/network_monitoring/cloud_network_monitoring/glossary.md new file mode 100644 index 00000000000..96467c75064 --- /dev/null +++ b/content/en/network_monitoring/cloud_network_monitoring/glossary.md @@ -0,0 +1,53 @@ +--- +title: CNM Terms and Concepts +description: Glossary for Cloud Network Monitoring (CNM) +further_reading: + - link: '/network_monitoring/cloud_network_monitoring/setup/' + tag: 'Documentation' + text: 'Setting Up Cloud Network Monitoring' + - link: '/network_monitoring/cloud_network_monitoring/tags_reference/' + tag: 'Documentation' + text: 'CNM Tags Reference' + - link: '/monitors/types/cloud_network_monitoring/' + tag: 'Documentation' + text: 'CNM Monitors and Alerts' + - link: '/network_monitoring/network_path/glossary' + tag: 'Documentation' + text: 'Network Path Glossary' +--- + +## Overview + +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. + +For additional definitions and descriptions of important CNM terms such as _policy based routing_, see the [main Glossary][6]. + +## Terminology + +| Concept | Description | +| ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **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. | +| **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. | +| **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. | +| **[Network Health][1]** | Displays the overall health of network connections, surfacing connectivity problems and degraded network performance across hosts and services. | +| **[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. | +| **[Network Map][3]** | A visualization view in CNM that maps network data between tags such as `service`, `kube_service`, `short_image`, and `container_name`. | +| **[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. | +| **[CNM tags][5]** | Tags that CNM uses to group and display traffic, for example, service-to-service or zone-to-zone communication. | +| **[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. | +| **[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. | +| **[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. | + +## Further Reading + +{{< partial name="whats-next/whats-next.html" >}} + +[1]: /network_monitoring/cloud_network_monitoring/network_health/ +[2]: /network_monitoring/cloud_network_monitoring/network_analytics/ +[3]: /network_monitoring/cloud_network_monitoring/network_map/ +[4]: /monitors/types/cloud_network_monitoring/ +[5]: /network_monitoring/cloud_network_monitoring/tags_reference/ +[6]: /glossary/?product=cloud-network-monitoring +[8]: /network_monitoring/cloud_network_monitoring/network_analytics/#tcp +[9]: /network_monitoring/cloud_network_monitoring/network_analytics/#network-load +[10]: /network_monitoring/cloud_network_monitoring/network_analytics/#unresolved-traffic \ No newline at end of file diff --git a/content/en/network_monitoring/devices/glossary.md b/content/en/network_monitoring/devices/glossary.md index e4b9ba09210..7be0f313fda 100644 --- a/content/en/network_monitoring/devices/glossary.md +++ b/content/en/network_monitoring/devices/glossary.md @@ -9,7 +9,7 @@ further_reading: ## Overview -Network Device Monitoring helps you gain insights into the health and performance of your on-prem routers, switches, and firewalls. +Network Device Monitoring (NDM) helps you gain insights into the health and performance of your on-prem routers, switches, and firewalls. For additional definitions and descriptions of important NDM terms such as _layer 2_ and _layer 3_, see the main [Glossary][1]. ## Terminology @@ -17,6 +17,12 @@ For additional definitions and descriptions of important NDM terms such as _laye Simple network management protocol (SNMP) : A network protocol that is used to collect information about bare metal networking gear. +Link Layer Discovery Protocol (LLDP) +: A protocol used by devices to advertise identity and capabilities to neighboring devices. NDM uses LLDP to map topology. + +Managed information base (MIB) +: 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. + Object identifier (OID) : 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. @@ -35,7 +41,7 @@ Software-defined wide area network (SD-WAN) [Device namespaces][3] : Namespace of the device. Namespaces can be used as tags to differentiate between multiple network devices that may share the same private IP. -Ping +[Ping][4] : 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. @@ -43,6 +49,7 @@ Ping {{< partial name="whats-next/whats-next.html" >}} -[1]: /glossary/ +[1]: /glossary/?product=network-device-monitoring [2]: /network_monitoring/devices/profiles -[3]: /network_monitoring/devices/snmp_traps/?tab=yaml#device-namespaces \ No newline at end of file +[3]: /network_monitoring/devices/snmp_traps/?tab=yaml#device-namespaces +[4]: /network_monitoring/devices/ping \ No newline at end of file diff --git a/content/en/network_monitoring/network_path/glossary.md b/content/en/network_monitoring/network_path/glossary.md new file mode 100644 index 00000000000..babfd101bfd --- /dev/null +++ b/content/en/network_monitoring/network_path/glossary.md @@ -0,0 +1,57 @@ +--- +title: Network Path Terms and Concepts +description: Glossary for Network Path +further_reading: + - link: '/network_monitoring/cloud_network_monitoring/setup/' + tag: 'Documentation' + text: 'Setting Up Cloud Network Monitoring' + - link: '/network_monitoring/cloud_network_monitoring/tags_reference/' + tag: 'Documentation' + text: 'CNM Tags Reference' + - link: '/monitors/types/cloud_network_monitoring/' + tag: 'Documentation' + text: 'CNM Monitors and Alerts' +--- + +## Network Path + +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. + +## Terminology +| Concept | Description | +| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **[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. | +| **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. +| **[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. | +| **Hop** | A network node along a route between source and destination, identified by IP address and associated metadata (ASN, cloud region, provider). | | +| **Source** | The starting point of a Network Path probe, typically an Agent-monitored host or container running the Datadog network monitoring tracer. | +| **Destination** | The endpoint that the Network Path probe is targeting, such as a service, public endpoint, or domain. | +| **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. | +| **Latency per hop** | The round-trip time between the probe source and each hop. This helps identify slow or congested nodes. | +| **Packet loss per hop** | The percentage of probe packets dropped before reaching or returning from a hop, useful for diagnosing reliability issues. | + +### Path View +| Concept | Description | +| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| **Aggregated hop** | A group of multiple identical hops (same IP, ASN, region), collapsed into a single representation to simplify visualization. | +| **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. | +| **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. | +| **Path change indicator** | A visual marker that shows when the observed route changes over time, for example an AS shift or a new hop. | +| **AS grouping** | The cluster of hops belonging to the same Autonomous System, helping identify which network operator controls each segment of the path. | +| **Region grouping** | The cluster of hops located within the same cloud region or geographic region. Helpful for identifying inter-regional routing. +| **Start node** | The initial node (source) where the probe begins. Represented at the far left of the Path View. | +| **End node** | The destination node where the probe terminates. Represented at the far right of the Path View. | +| **Hop status indicator** | The icon or color indicating whether the hop is healthy, degraded, or unreachable, based on latency and loss. | +| **Probe status** | Shows whether the probe reached a hop successfully, partially, or not at all. This helps you identify where traffic stops or degrades. | | +| **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. | +| **Traversal completion** | Represents whether or not the traceroute was able to successfully reach the destination. | +| **Reachability** | The level of packet loss the destination is experiencing. | +| **Latency** | How long the traceroute took to get from a source to its destination. | + + +## Further Reading + +{{< partial name="whats-next/whats-next.html" >}} + +[6]: /network_monitoring/network_path/ +[7]: /network_monitoring/network_path/path_view \ No newline at end of file