diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml index 312764cf97458..e098d3d9917a5 100644 --- a/config/_default/menus/main.en.yaml +++ b/config/_default/menus/main.en.yaml @@ -1516,10 +1516,10 @@ menu: parent: monitor_types identifier: monitor_types_network weight: 317 - - name: Network Performance - url: monitors/types/network_performance/ + - name: Cloud Network Monitoring + url: monitors/types/cloud_network_monitoring/ parent: monitor_types - identifier: monitor_types_network_performance + identifier: monitor_types_cnm weight: 318 - name: NetFlow url: monitors/types/netflow/ @@ -2975,35 +2975,35 @@ menu: identifier: nm_parent parent: infrastructure_heading weight: 40000 - - name: Network Performance Monitoring - url: network_monitoring/performance/ + - name: Cloud Network Monitoring + url: network_monitoring/cloud_network_monitoring/ parent: nm_parent - identifier: npm + identifier: cnm weight: 1 - name: Setup - url: network_monitoring/performance/setup/ - parent: npm - identifier: npm_setup + url: network_monitoring/cloud_network_monitoring/setup/ + parent: cnm + identifier: cnm_setup weight: 101 - name: Overview Page - url: network_monitoring/performance/overview_page/ - parent: npm - identifier: npm_overview_page + url: network_monitoring/cloud_network_monitoring/overview_page/ + parent: cnm + identifier: cnm_overview_page weight: 102 - name: Network Analytics - url: network_monitoring/performance/network_analytics/ - parent: npm - identifier: npm_analytics + url: network_monitoring/cloud_network_monitoring/network_analytics/ + parent: cnm + identifier: cnm_analytics weight: 103 - name: Network Map - url: network_monitoring/performance/network_map/ - parent: npm - identifier: npm_map + url: network_monitoring/cloud_network_monitoring/network_map/ + parent: cnm + identifier: cnm_map weight: 104 - name: Guides - url: network_monitoring/performance/guide/ - identifier: npm_guides - parent: npm + url: network_monitoring/cloud_network_monitoring/guide/ + identifier: cnm_guides + parent: cnm weight: 105 - name: DNS Monitoring url: network_monitoring/dns/ diff --git a/content/en/account_management/billing/pricing.md b/content/en/account_management/billing/pricing.md index 25f55893213f9..3a342e136d344 100644 --- a/content/en/account_management/billing/pricing.md +++ b/content/en/account_management/billing/pricing.md @@ -50,11 +50,11 @@ You can put controls in place for both Indexed and Ingested span volumes. For mo * A **browser test** is a simulation of a scripted sequence of user actions on a web-based application using a virtualized web browser. Datadog charges per thousand browser tests executed to the Datadog Synthetic Monitoring service. -## Network Performance Monitoring +## Cloud Network Monitoring -* Datadog records the number of **Network Performance Monitoring** (NPM) hosts you are concurrently monitoring with the Datadog NPM service once per hour. +* Datadog records the number of **Cloud Network Monitoring** (CNM) hosts you are concurrently monitoring with the Datadog CNM service once per hour. * The billable count of hosts is calculated at the end of the month using the maximum count (high-water mark) of the lower 99 percent of usage for those hours. Datadog excludes the top 1 percent to reduce the impact of spikes in usage on your bill. -* Additionally, Datadog measures the total number of flows used by all NPM hosts per month. A **flow** is a record of traffic sent and received between a source (IP:Port) and destination (IP:Port), as measured over a five-minute time period. +* Additionally, Datadog measures the total number of flows used by all CNM hosts per month. A **flow** is a record of traffic sent and received between a source (IP:Port) and destination (IP:Port), as measured over a five-minute time period. ## Real User Monitoring diff --git a/content/en/account_management/billing/usage_metrics.md b/content/en/account_management/billing/usage_metrics.md index 7dcaf41d43b83..08b1297e3c551 100644 --- a/content/en/account_management/billing/usage_metrics.md +++ b/content/en/account_management/billing/usage_metrics.md @@ -44,7 +44,7 @@ Estimated usage metrics are generally available for the following usage types: | API test runs | `datadog.estimated_usage.synthetics.api_test_runs` | Estimated usage for API tests. | | Browser test runs | `datadog.estimated_usage.synthetics.browser_test_runs`| Estimated usage for browser tests. | | Parallel Testing Slots | `datadog.estimated_usage.synthetics.parallel_testing_slots` | Estimated usage for parallel testing slots. | -| Network Hosts | `datadog.estimated_usage.network.hosts`, `datadog.estimated_usage.network.hosts.by_tag` | Unique NPM hosts seen in the last hour. | +| Network Hosts | `datadog.estimated_usage.network.hosts`, `datadog.estimated_usage.network.hosts.by_tag` | Unique CNM hosts seen in the last hour. | | Network Devices | `datadog.estimated_usage.network.devices`, `datadog.estimated_usage.network.devices.by_tag` | Unique NDM devices seen in the last hour. | | Profiled Hosts | `datadog.estimated_usage.profiling.hosts`, `datadog.estimated_usage.profiling.hosts.by_tag` | Unique profiling hosts seen in the last hour. | | Profiled Containers | `datadog.estimated_usage.profiling.containers`, `datadog.estimated_usage.profiling.containers.by_tag` | Unique profiling containers seen in last 5 minutes. | diff --git a/content/en/administrators_guide/plan.md b/content/en/administrators_guide/plan.md index 9ab97fd1089b8..04df9d627f602 100644 --- a/content/en/administrators_guide/plan.md +++ b/content/en/administrators_guide/plan.md @@ -209,9 +209,9 @@ Use [Live processes][26] to view all of your running processes in one place. For Web server operations depend on the network availability of ports, the validity of SSL certificates, and low latencies. Install the [HTTP_Check][25] to monitor local or remote HTTP endpoints, detect bad response codes (such as 404), and use Synthetic API tests to identify soon-to-expire [SSL certificates][71]. -### Network Monitoring +### Cloud Network Monitoring -Web servers are almost always inter-connected with other services through a network fabric that is vulnerable to drops and can result in re-transmits. Use Datadog's [network integration][28] and enable [Network Performance Monitoring][29] to gain visibility into your network traffic between services, containers, availability zones, and other tags on your infrastructure. +Web servers are almost always inter-connected with other services through a network fabric that is vulnerable to drops and can result in re-transmits. Use Datadog's [network integration][28] and enable [Cloud Network Monitoring][29] to gain visibility into your network traffic between services, containers, availability zones, and other tags on your infrastructure. ## Platform services @@ -344,7 +344,7 @@ Create a detailed roll-out methodology in the [build][41] phase by focusing on t [26]: /infrastructure/process/?tab=linuxwindows [27]: /infrastructure/process/?tab=linuxwindows\#installation [28]: /integrations/network/ -[29]: /network_monitoring/performance/ +[29]: /network_monitoring/cloud_network_monitoring/ [30]: /service_catalog/ [31]: /service_management/events/ [32]: /error_tracking/ diff --git a/content/en/agent/basic_agent_usage/aix.md b/content/en/agent/basic_agent_usage/aix.md index ce3862677992b..001fdef582cd0 100644 --- a/content/en/agent/basic_agent_usage/aix.md +++ b/content/en/agent/basic_agent_usage/aix.md @@ -98,7 +98,7 @@ Additionally, the following integrations can be enabled to collect further metri Enable the above integrations by copying and editing the sample configuration files provided. These are found in `/etc/datadog-agent/conf.d`. The name of the YAML configuration file should match that of the integration: `/etc/datadog-agent/conf.d/.d/conf.yaml` enables the integration ``, and set its configuration. Example configuration files can be found at `/etc/datadog-agent/conf.d/.d/conf.yaml.example` -**Note**: Some of the available metrics differ between the integrations for the Unix Agent and the integrations for Linux, Windows and MacOS. Although it is possible to monitor processes and network metrics with the Unix Agent, the Live Process Monitoring and Network Performance Monitoring capabilities aren't available. Log Management is also not available with the Unix Agent. +**Note**: Some of the available metrics differ between the integrations for the Unix Agent and the integrations for Linux, Windows and MacOS. Although it is possible to monitor processes and network metrics with the Unix Agent, the Live Process Monitoring and Cloud Network Monitoring capabilities aren't available. Log Management is also not available with the Unix Agent.
The Unix Agent has no trace-agent component, so APM tracing and profiling is not supported.
diff --git a/content/en/agent/basic_agent_usage/windows.md b/content/en/agent/basic_agent_usage/windows.md index cb05db59964fe..a4cdd76f07c84 100644 --- a/content/en/agent/basic_agent_usage/windows.md +++ b/content/en/agent/basic_agent_usage/windows.md @@ -191,7 +191,7 @@ Each of the following configuration options can be added as a property to the co | `PROXY_USER` | String | (If using a proxy) sets your proxy user. [Learn more about using a proxy with the Datadog Agent][4]. | | `PROXY_PASSWORD` | String | (If using a proxy) sets your proxy password. For the process/container Agent, this variable is required for passing in an authentication password and cannot be renamed. [Learn more about using a proxy with the Datadog Agent][4]. | | `EC2_USE_WINDOWS_PREFIX_DETECTION` | Boolean | Use the EC2 instance id for Windows hosts on EC2. _(v7.28.0+)_ | -| [DEPRECATED] `ADDLOCAL` | String | Enable additional Agent component. Setting to `"MainApplication,NPM"` causes the driver component for [Network Performance Monitoring][5] to be installed. _(version 7.44.0 and previous)_ | +| [DEPRECATED] `ADDLOCAL` | String | Enable additional Agent component. Setting to `"MainApplication,NPM"` causes the driver component for [Cloud Network Monitoring][5] to be installed. _(version 7.44.0 and previous)_ | **Note:** Agent 7 only supports Python 3. Before upgrading, confirm that your custom checks are compatible with Python 3. See the [Python 3 Custom Check Migration][13] guide for more information. If you're not using custom checks or have already confirmed their compatibility, upgrade normally. @@ -392,7 +392,7 @@ After configuration is complete, [restart the Agent][11]. [2]: /agent/supported_platforms/?tab=windows [3]: /agent/faq/windows-agent-ddagent-user/ [4]: /agent/configuration/proxy/ -[5]: /network_monitoring/performance +[5]: /network_monitoring/cloud_network_monitoring [6]: /agent/guide/datadog-agent-manager-windows/ [7]: /integrations/wmi_check/ [8]: https://app.datadoghq.com/monitors/create/integration diff --git a/content/en/agent/iot/_index.md b/content/en/agent/iot/_index.md index d639476d1d8b5..e5967fc0b5673 100644 --- a/content/en/agent/iot/_index.md +++ b/content/en/agent/iot/_index.md @@ -25,7 +25,7 @@ The IoT Agent also supports: - Custom metric collection using an embedded [DogStatsD][6] server - Log collection using [tailing files][7], [TCP/UDP][8], and [journald][9] -The IoT Agent does not include the Python interpreter and other integrations pre-packaged with the standard Agent. It also doesn't support tracing for APM, live process monitoring, or network performance monitoring. +The IoT Agent does not include the Python interpreter and other integrations pre-packaged with the standard Agent. It also doesn't support tracing for APM, live process monitoring, or Cloud Network Monitoring. ## Setup diff --git a/content/en/all_guides.md b/content/en/all_guides.md index 99e363ad2309b..c6c7932a5405b 100644 --- a/content/en/all_guides.md +++ b/content/en/all_guides.md @@ -28,7 +28,7 @@ Guides in the Datadog documentation are pages that provide background knowledge, {{< whatsnext desc="Infrastructure:">}} {{< nextlink href="/containers/guide" >}}    Containers{{< /nextlink >}} {{< nextlink href="/serverless/guide" >}}    Serverless{{< /nextlink >}} -{{< nextlink href="/network_monitoring/performance/guide" >}}    Network Performance Monitoring{{< /nextlink >}} +{{< nextlink href="/network_monitoring/cloud_network_monitoring/guide" >}}    Cloud Network Monitoring{{< /nextlink >}} {{< nextlink href="/network_monitoring/devices/guide" >}}    Network Device Monitoring{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/en/cloud_cost_management/container_cost_allocation.md b/content/en/cloud_cost_management/container_cost_allocation.md index dcca185cf8f77..939978d628a46 100644 --- a/content/en/cloud_cost_management/container_cost_allocation.md +++ b/content/en/cloud_cost_management/container_cost_allocation.md @@ -45,7 +45,7 @@ The following table presents the list of collected features and the minimal Agen 1. For AWS ECS support, set up [**Datadog Container Monitoring**][104] in ECS tasks. 1. Optionally, enable [AWS Split Cost Allocation][105] for usage-based ECS allocation. 1. To enable GPU container cost allocation, install the [Datadog DCGM integration][106]. -1. To enable Data transfer cost allocation, set up [Network Performance Monitoring][107]. **Note**: additional charges apply +1. To enable Data transfer cost allocation, set up [Cloud Network Monitoring][107]. **Note**: additional charges apply [101]: https://app.datadoghq.com/cost/setup [102]: /containers/kubernetes/installation/?tab=operator @@ -53,7 +53,7 @@ The following table presents the list of collected features and the minimal Agen [104]: /containers/amazon_ecs/ [105]: https://docs.aws.amazon.com/cur/latest/userguide/enabling-split-cost-allocation-data.html [106]: /integrations/dcgm/?tab=kubernetes#installation -[107]: /network_monitoring/performance/setup +[107]: /network_monitoring/cloud_network_monitoring/setup {{% /tab %}} {{% tab "Azure" %}} @@ -145,7 +145,7 @@ Next, Datadog examines the daily [workload resources][104] running on that node. **Note**: Only _tags_ from pods and nodes are added to cost metrics. To include labels, enable labels as tags for [nodes][101] and [pods][102]. -[Network Performance Monitoring][105] must be enabled on all AWS hosts to allow accurate data transfer cost allocation. If some hosts do not have Network Performance Monitoring enabled, the data transfer costs for these hosts is not allocated and may appear as an `n/a` bucket depending on filter and group-by conditions. +[Cloud Network Monitoring][105] must be enabled on all AWS hosts to allow accurate data transfer cost allocation. If some hosts do not have Cloud Network Monitoring enabled, the data transfer costs for these hosts is not allocated and may appear as an `n/a` bucket depending on filter and group-by conditions. Datadog supports data transfer cost allocation using [standard 6 workload resources][104] only. For [custom workload resources][106], data transfer costs can be allocated down to the cluster level only, and not the node/namespace level. @@ -153,7 +153,7 @@ Datadog supports data transfer cost allocation using [standard 6 workload resour [102]: /containers/kubernetes/tag/?tab=containerizedagent#pod-labels-as-tags [103]: https://docs.aws.amazon.com/cur/latest/userguide/what-is-cur.html [104]: https://kubernetes.io/docs/concepts/workloads/ -[105]: /network_monitoring/performance/setup +[105]: /network_monitoring/cloud_network_monitoring/setup [106]: https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/ {{% /tab %}} @@ -246,8 +246,8 @@ Costs are allocated into the following spend types: | Spend type | Description | | -----------| ----------- | -| Usage | Cost of data transfer that is monitored by Network Performance Monitoring and allocated. | -| Not monitored | Cost of data transfer not monitored by Network Performance Monitoring. This cost is not allocated. | +| Usage | Cost of data transfer that is monitored by Cloud Network Monitoring and allocated. | +| Not monitored | Cost of data transfer not monitored by Cloud Network Monitoring. This cost is not allocated. | {{% /tab %}} {{% tab "Azure" %}} diff --git a/content/en/containers/amazon_ecs/_index.md b/content/en/containers/amazon_ecs/_index.md index a491f5ca06330..62079b60d0004 100644 --- a/content/en/containers/amazon_ecs/_index.md +++ b/content/en/containers/amazon_ecs/_index.md @@ -202,7 +202,7 @@ To collect Live Process information for all your containers and send it to Datad } {{< /highlight >}} -#### Network Performance Monitoring +#### Cloud Network Monitoring
This feature is only available for Linux. @@ -266,7 +266,7 @@ If you already have a task definition, update your file to include the following ``` #### Network Path -
Network Path for Datadog Network Performance Monitoring is in Preview. Reach out to your Datadog representative to sign up.
+
Network Path for Datadog Cloud Network Monitoring is in Preview. Reach out to your Datadog representative to sign up.
1. To enable [Network Path][31] on your ECS clusters, enable the `system-probe` traceroute module by adding the following environment variable in your `datadog-agent-sysprobe-ecs.json` file: diff --git a/content/en/containers/guide/kubernetes_daemonset.md b/content/en/containers/guide/kubernetes_daemonset.md index ec6d5945c08c0..da5730bd641d8 100644 --- a/content/en/containers/guide/kubernetes_daemonset.md +++ b/content/en/containers/guide/kubernetes_daemonset.md @@ -39,7 +39,7 @@ To install the Datadog Agent on your Kubernetes cluster: | | | | | | | [Manifest template][10] | no template | | | | | | | | [Manifest template][11] | [Manifest template][12] | - To enable trace collection completely, [extra steps are required on your application Pod configuration][13]. Refer also to the [logs][14], [APM][15], [processes][16], and [Network Performance Monitoring][17], and [Security][18] documentation pages to learn how to enable each feature individually. + To enable trace collection completely, [extra steps are required on your application Pod configuration][13]. Refer also to the [logs][14], [APM][15], [processes][16], and [Cloud Network Monitoring][17], and [Security][18] documentation pages to learn how to enable each feature individually. **Note**: Those manifests are set for the `default` namespace. If you are in a custom namespace, update the `metadata.namespace` parameter before applying them. @@ -367,7 +367,7 @@ Additional examples are available on the [Container Discover Management][27] pag [14]: /agent/kubernetes/log/ [15]: /agent/kubernetes/apm/ [16]: /infrastructure/process/?tab=kubernetes#installation -[17]: /network_monitoring/performance/setup/ +[17]: /network_monitoring/cloud_network_monitoring/setup/ [18]: /data_security/agent/ [19]: https://app.datadoghq.com/organization-settings/api-keys [20]: /getting_started/site/ diff --git a/content/en/containers/kubernetes/configuration.md b/content/en/containers/kubernetes/configuration.md index 7d1aad539573b..8a5f1175e7a11 100644 --- a/content/en/containers/kubernetes/configuration.md +++ b/content/en/containers/kubernetes/configuration.md @@ -13,7 +13,7 @@ After you have installed the Datadog Agent in your Kubernetes environment, you m ### Enable Datadog to collect: - [Traces (APM)](#enable-apm-and-tracing) - [Kubernetes events](#enable-kubernetes-event-collection) -- [NPM](#enable-npm-collection) +- [CNM](#enable-cnm-collection) - [Logs](#enable-log-collection) - [Processes](#enable-process-collection) @@ -134,7 +134,7 @@ agents: For DaemonSet configuration, see [DaemonSet Cluster Agent event collection][14]. -## Enable NPM collection +## Enable CNM collection {{< tabs >}} {{% tab "Datadog Operator" %}} @@ -183,7 +183,7 @@ helm upgrade -f datadog-values.yaml datadog/datadog {{% /tab %}} {{< /tabs >}} -For more information, see [Network Performance Monitoring][18]. +For more information, see [Cloud Network Monitoring][18]. ## Enable log collection @@ -852,7 +852,7 @@ Starting with Agent v6.4.0 (and v6.5.0 for the Trace Agent), you can override th [15]: /infrastructure/containers/ [16]: /containers/kubernetes/apm [17]: /containers/kubernetes/log -[18]: /network_monitoring/performance/ +[18]: /network_monitoring/cloud_network_monitoring/ [19]: /developers/dogstatsd [20]: https://app.datadoghq.com/orchestration/overview [21]: /infrastructure/containers/orchestrator_explorer diff --git a/content/en/containers/kubernetes/distributions.md b/content/en/containers/kubernetes/distributions.md index 47cd7e7559dc2..1323cce36a442 100644 --- a/content/en/containers/kubernetes/distributions.md +++ b/content/en/containers/kubernetes/distributions.md @@ -243,7 +243,7 @@ GKE Autopilot requires some configuration, shown below. Datadog recommends that you specify resource limits for the Agent container. Autopilot sets a relatively low default limit (50m CPU, 100Mi memory) that may lead the Agent container to quickly OOMKill depending on your environment. If applicable, also specify resource limits for the Trace Agent and Process Agent containers. Additionally, you may wish to create a priority class for the Agent to ensure it is scheduled. -**Note**: Network Performance Monitoring is not supported for GKE Autopilot. +**Note**: Cloud Network Monitoring is not supported for GKE Autopilot. {{< tabs >}} {{% tab "Helm" %}} @@ -330,6 +330,7 @@ agents: {{% /tab %}} {{< /tabs >}} + ## Red Hat OpenShift {#Openshift} OpenShift comes with hardened security by default with SELinux and SecurityContextConstraints (SCC). As a result, it requires some specific configurations: diff --git a/content/en/developers/guide/data-collection-resolution-retention.md b/content/en/developers/guide/data-collection-resolution-retention.md index de159deeca9f8..566f825320f45 100644 --- a/content/en/developers/guide/data-collection-resolution-retention.md +++ b/content/en/developers/guide/data-collection-resolution-retention.md @@ -45,7 +45,7 @@ Find below a summary of Datadog data [collection][6], [resolution][5], and reten | Infrastructure | Orchestrator Explorer (Kubernetes) | Datadog Agent | 15 seconds | 15 seconds | 15 minutes | | Infrastructure | Live containers | Datadog Agent + enabled Docker integration or Datadog container Agent | 2 seconds | 1 second | 36 hours | | Infrastructure | Live processes | Datadog Agent + Process Agent | 2 seconds | 1 second | 36 hours | -| Infrastructure | Network Performance Monitoring | System Probe | 30 seconds | 1 min | 14 days +| Infrastructure | Cloud Network Monitoring | System Probe | 30 seconds | 1 min | 14 days | Infrastructure | Network Device Monitoring | Datadog Agent | 15 seconds | 1 second | 15 months | Infrastructure | NetFlow Monitoring | Datadog Agent | Real time | Aggregated over 5 min interval | 30 days | | Infrastructure | System metrics | Datadog Agent | 15 seconds | 1 second | 15 months | diff --git a/content/en/getting_started/application/_index.md b/content/en/getting_started/application/_index.md index acad67cc67769..85781dff89c31 100644 --- a/content/en/getting_started/application/_index.md +++ b/content/en/getting_started/application/_index.md @@ -105,11 +105,11 @@ See [Host Map][9] for more details. [Datadog Application Performance Monitoring][6] (APM or tracing) provides you with deep insight into your application's performance—from automatically generated dashboards for monitoring key metrics, like request volume and latency, to detailed traces of individual requests—side by side with your logs and infrastructure monitoring. When a request is made to an application, Datadog can see the traces across a distributed system, and show you systematic data about precisely what is happening to this request. -## Network Performance Monitoring +## Cloud Network Monitoring {{< img src="getting_started/npm.png" alt="NPM" >}} -Datadog [Network Performance Monitoring][17] (NPM) gives you visibility into your network traffic across any tagged object in Datadog: from containers to hosts, services, and availability zones. Group by anything—from datacenters to teams to individual containers. Use tags to filter traffic by source and destination. The filters then aggregate into flows, each showing traffic between one source and one destination, through a customizable network page and network map. Each flow contains network metrics such as throughput, bandwidth, retransmit count, and source/destination information down to the IP, port, and PID levels. It then reports key metrics such as traffic volume and TCP retransmits. +Datadog [Cloud Network Monitoring][17] (NPM) gives you visibility into your network traffic across any tagged object in Datadog: from containers to hosts, services, and availability zones. Group by anything—from datacenters to teams to individual containers. Use tags to filter traffic by source and destination. The filters then aggregate into flows, each showing traffic between one source and one destination, through a customizable network page and network map. Each flow contains network metrics such as throughput, bandwidth, retransmit count, and source/destination information down to the IP, port, and PID levels. It then reports key metrics such as traffic volume and TCP retransmits. ## Synthetic Monitoring diff --git a/content/en/glossary/terms/flow.md b/content/en/glossary/terms/flow.md index 11c07e902d082..a3d0b4f8d798d 100644 --- a/content/en/glossary/terms/flow.md +++ b/content/en/glossary/terms/flow.md @@ -1,9 +1,9 @@ --- title: flow core_product: - - network performance monitoring + - cloud network monitoring --- In computer networks, a flow is the path taken when one endpoint communicates with another. Datadog's [network map][1] provides a visualization for network data flow. -For more information, see the documentation. +For more information, see the documentation. -[1]: /network_monitoring/performance/network_map/ +[1]: /network_monitoring/cloud_network_monitoring/network_map/ diff --git a/content/en/glossary/terms/layer_2.md b/content/en/glossary/terms/layer_2.md index 465c8eee66958..5a43de4064e7e 100644 --- a/content/en/glossary/terms/layer_2.md +++ b/content/en/glossary/terms/layer_2.md @@ -4,6 +4,6 @@ synonyms: - data link layer core_product: - network device monitoring - - network performance monitoring + - cloud network monitoring --- In the OSI model of computer networking, layer 2 defines the network data format. Layer 2 concerns frames and physical addressing. \ No newline at end of file diff --git a/content/en/glossary/terms/layer_3.md b/content/en/glossary/terms/layer_3.md index aee40d4c24e3e..d10ec6f5aa844 100644 --- a/content/en/glossary/terms/layer_3.md +++ b/content/en/glossary/terms/layer_3.md @@ -4,6 +4,6 @@ synonyms: - network layer core_product: - network device monitoring - - network performance monitoring + - cloud network monitoring --- In the OSI model of computer networking, layer 3 determines how data is physically routed from source to destination. Layer 3 concerns packets and logical addressing. \ No newline at end of file diff --git a/content/en/glossary/terms/netflow.md b/content/en/glossary/terms/netflow.md index e96ebc24470f2..c5c0e2cdc3227 100644 --- a/content/en/glossary/terms/netflow.md +++ b/content/en/glossary/terms/netflow.md @@ -1,7 +1,7 @@ --- title: NetFlow core_product: - - network performance monitoring + - cloud network monitoring --- [NetFlow][1] is a network protocol system that collects IP network traffic as it enters or exits an interface. It was introduced by Cisco in 1996. diff --git a/content/en/glossary/terms/network_profile.md b/content/en/glossary/terms/network_profile.md index 6ba4cfd74a80d..70be8cfc5bff7 100644 --- a/content/en/glossary/terms/network_profile.md +++ b/content/en/glossary/terms/network_profile.md @@ -1,7 +1,7 @@ --- title: network profile core_product: - - network performance monitoring + - cloud network monitoring - network device monitoring --- A network profile is set of attributes that describe how a network is configured. \ No newline at end of file diff --git a/content/en/glossary/terms/npm.md b/content/en/glossary/terms/npm.md index e07db6f53e7a8..48047bfb27690 100644 --- a/content/en/glossary/terms/npm.md +++ b/content/en/glossary/terms/npm.md @@ -1,7 +1,7 @@ --- -title: Network Performance Monitoring (NPM) +title: Cloud Network Monitoring (CNM) core_product: - - network performance monitoring + - cloud network monitoring --- -Datadog's Network Performance Monitoring (NPM) provides visibility into network traffic between services, containers, availability zones, etc. +Datadog's Cloud Network Monitoring (CNM) provides visibility into network traffic between services, containers, availability zones, etc. For more information, see the documentation. \ No newline at end of file diff --git a/content/en/glossary/terms/pbr.md b/content/en/glossary/terms/pbr.md index 3a92c12da3c49..74377988bc3c5 100644 --- a/content/en/glossary/terms/pbr.md +++ b/content/en/glossary/terms/pbr.md @@ -1,6 +1,6 @@ --- title: policy-based routing (PBR) core_product: - - network performance monitoring + - cloud network monitoring --- In computer networks, PBR is a technique for routing data according to policies and filters. \ No newline at end of file diff --git a/content/en/infrastructure/process/_index.md b/content/en/infrastructure/process/_index.md index 3cb4a9dc615cc..6a1a011591a48 100644 --- a/content/en/infrastructure/process/_index.md +++ b/content/en/infrastructure/process/_index.md @@ -490,7 +490,7 @@ Live Processes adds extra visibility to your container deployments by monitoring In [APM Traces][10], you can click on a service's span to see the processes running on its underlying infrastructure. A service's span processes are correlated with the hosts or pods on which the service runs at the time of the request. Analyze process metrics such as CPU and RSS memory alongside code-level errors to distinguish between application-specific and wider infrastructure issues. Clicking on a process brings you to the Live Processes page. Related processes are not supported for serverless and browser traces. -### Network Performance Monitoring +### Cloud Network Monitoring When you inspect a dependency in the [Network Analytics][11] page, you can view processes running on the underlying infrastructure of the endpoints such as services communicating with one another. Use process metadata to determine whether poor network connectivity (indicated by a high number of TCP retransmits) or high network call latency (indicated by high TCP round-trip time) could be due to heavy workloads consuming those endpoints' resources, and thus, affecting the health and efficiency of their communication. @@ -517,6 +517,6 @@ Processes are normally collected at 10s resolution. While actively working with [8]: /dashboards/widgets/timeseries/#pagetitle [9]: /infrastructure/livecontainers/ [10]: /tracing/ -[11]: /network_monitoring/performance/network_analytics +[11]: /network_monitoring/cloud_network_monitoring/network_analytics [12]: /agent/configuration/agent-commands/#restart-the-agent diff --git a/content/en/infrastructure/resource_catalog/_index.md b/content/en/infrastructure/resource_catalog/_index.md index 63aee54c0d372..d8e5651306bf3 100644 --- a/content/en/infrastructure/resource_catalog/_index.md +++ b/content/en/infrastructure/resource_catalog/_index.md @@ -54,7 +54,7 @@ Resource Catalog leverages Datadog cloud integrations and the Datadog Agent to g ## Setup -By default, when you navigate to the Resource Catalog, you are able to see Datadog Agent monitored hosts, as well as cloud resources crawled for other Datadog products such as NPM (Network Performance Monitoring), and DBM (Database Monitoring). To view additional cloud resources in the Resource Catalog, extend resource collection from the [Resource Catalog][5] setup page. To gain insights into your security risks, enable [Cloud Security Management][1] for each cloud account. +By default, when you navigate to the Resource Catalog, you are able to see Datadog Agent monitored hosts, as well as cloud resources crawled for other Datadog products such as CNM (Cloud Network Monitoring), and DBM (Database Monitoring). To view additional cloud resources in the Resource Catalog, extend resource collection from the [Resource Catalog][5] setup page. To gain insights into your security risks, enable [Cloud Security Management][1] for each cloud account. {{< img src="/infrastructure/resource_catalog/resource-catalog-doc-img-2.png" alt="The Resource Catalog configuration page for extending resource collection" width="100%">}} diff --git a/content/en/integrations/guide/azure-cloud-adoption-framework.md b/content/en/integrations/guide/azure-cloud-adoption-framework.md index ac3c3d2b1f412..52367bfd5c1fc 100644 --- a/content/en/integrations/guide/azure-cloud-adoption-framework.md +++ b/content/en/integrations/guide/azure-cloud-adoption-framework.md @@ -107,7 +107,7 @@ Once you have installed the Datadog Agent, add the following data collection met 1. [Add integrations to collect data][12] specific to the technologies your services employ. 2. [Enable Application Performance Monitoring (APM)][13] to measure the request counts, latency, and error rates of your services. 3. [Capture the logs generated by your environment][14] to gain deeper context into when your metrics and traces behave unexpectedly. If you have a lot of logs, [store only the most critical logs][15]. - 4. [Enable Network Performance Monitoring (NPM)][16] to ensure efficient communication between your services. NPM is crucial in the migration process because your original environment may need to communicate with your new cloud environment. + 4. [Enable Cloud Network Monitoring (CNM)][16] to ensure efficient communication between your services. CNM is crucial in the migration process because your original environment may need to communicate with your new cloud environment. Before you migrate your new workload, install the Agent, configure complete data collection on your legacy environment, and design your new workloads to include the Datadog Agent with the same complete data collection. @@ -171,7 +171,7 @@ For more information about how to configure SLOs and exposing them to stakeholde [13]: https://app.datadoghq.com/apm/getting-started [14]: https://app.datadoghq.com/logs/onboarding [15]: /logs/guide/getting-started-lwl/ -[16]: /network_monitoring/performance/ +[16]: /network_monitoring/cloud_network_monitoring/ [17]: https://app.datadoghq.com/infrastructure/map [18]: https://app.datadoghq.com/infrastructure/map?node_type=container [19]: https://app.datadoghq.com/apm/map diff --git a/content/en/logs/guide/reduce_data_transfer_fees.md b/content/en/logs/guide/reduce_data_transfer_fees.md index e7325e7171d25..42efff21d1bc2 100644 --- a/content/en/logs/guide/reduce_data_transfer_fees.md +++ b/content/en/logs/guide/reduce_data_transfer_fees.md @@ -30,14 +30,14 @@ Send data over a private network to avoid the public internet and reduce your da ## Additional tools After you switch to private links, you can use the following to monitor your usage and have more control over your data costs: -- Datadog's [Network Performance Monitoring][1] identifies your organization’s highest throughput applications. +- Datadog's [Cloud Network Monitoring][1] identifies your organization's highest throughput applications. - [Cloud Cost Management][2] tools can verify and monitor the reduction in your cloud costs. ## Further reading {{< partial name="whats-next/whats-next.html" >}} -[1]: /network_monitoring/performance/ +[1]: /network_monitoring/cloud_network_monitoring/ [2]: /cloud_cost_management/ [3]: /agent/guide/private-link/ [4]: /agent/guide/azure-private-link/ diff --git a/content/en/logs/log_collection/_index.md b/content/en/logs/log_collection/_index.md index d9585656cc6b0..448e194c39316 100644 --- a/content/en/logs/log_collection/_index.md +++ b/content/en/logs/log_collection/_index.md @@ -109,7 +109,7 @@ Datadog integrations and log collection are tied together. You can use an integr ## Reduce data transfer fees -Use Datadog's [Network Performance Monitoring][7] to identify your organization’s highest throughput applications. Connect to Datadog over supported private connections and send data over a private network to avoid the public internet and reduce your data transfer fees. After you switch to private links, use Datadog’s [Cloud Cost Management][8] tools to verify the impact and monitor the reduction in your cloud costs. +Use Datadog's [Cloud Network Monitoring][7] to identify your organization's highest throughput applications. Connect to Datadog over supported private connections and send data over a private network to avoid the public internet and reduce your data transfer fees. After you switch to private links, use Datadog’s [Cloud Cost Management][8] tools to verify the impact and monitor the reduction in your cloud costs. For more information, see [How to send logs to Datadog while reducing data transfer fees][9]. @@ -119,7 +119,7 @@ For more information, see [How to send logs to Datadog while reducing data trans [4]: /agent/kubernetes/log/#autodiscovery [5]: /agent/docker/log/#log-integrations [6]: /integrations/#cat-log-collection -[7]: /network_monitoring/performance/ +[7]: /network_monitoring/cloud_network_monitoring/ [8]: /cloud_cost_management/ [9]: /logs/guide/reduce_data_transfer_fees/ diff --git a/content/en/metrics/summary.md b/content/en/metrics/summary.md index 1a03562d81bb4..7b01915d1648f 100644 --- a/content/en/metrics/summary.md +++ b/content/en/metrics/summary.md @@ -202,7 +202,7 @@ This table shows the mapping between the metric origin as seen in the facet and | LLM Observability | Timeseries emitted by the LLM Observability product using the `lmobs_to_metrics` service. | Logs | Timeseries generated from the Datadog [Logs][28] platform. | Metrics API | Timeseries sent using Datadog's [OTLP Ingestion endpoint][21] and OTel receiver with a Datadog integration counterparts or points for estimated usage metrics or Datadog API Client. -| NPM | Timeseries sent by the Datadog [Network Performance Monitoring][19] product. +| CNM | Timeseries sent by the Datadog [Cloud Network Monitoring][19] product. | Observability Pipelines | Timeseries sent by the Datadog [Observability Pipielines][20] including error and performance metrics. | Other | Timeseries that don't have a DD integration counterpart. | Processes | Timeseries generated from the Datadog [Processes][22] product. @@ -236,7 +236,7 @@ This table shows the mapping between the metric origin as seen in the facet and [16]: /data_streams/ [17]: /opentelemetry/collector_exporter/otel_collector_datadog_exporter/?tab=onahost [18]: /opentelemetry/collector_exporter/ -[19]: /network_monitoring/performance/ +[19]: /network_monitoring/cloud_network_monitoring/ [20]: /observability_pipelines/ [21]: /opentelemetry/interoperability/otlp_ingest_in_the_agent/?tab=host [22]: /integrations/process/ diff --git a/content/en/monitors/types/_index.md b/content/en/monitors/types/_index.md index 096f9f7f6b06a..cee6b05f41ace 100644 --- a/content/en/monitors/types/_index.md +++ b/content/en/monitors/types/_index.md @@ -36,7 +36,7 @@ further_reading: {{< nextlink href="/monitors/types/process" >}}Live Process: Check if one or more processes are running on a host.{{< /nextlink >}} {{< nextlink href="/monitors/types/log" >}}Logs: Alert when a specified type of log exceeds a user-defined threshold over a given period of time.{{< /nextlink >}} {{< nextlink href="/monitors/types/network" >}}Network: Check the status of TCP/HTTP endpoints.{{< /nextlink >}} -{{< nextlink href="/monitors/types/network_performance" >}}Network Performance: Set alerts on your network traffic.{{< /nextlink >}} +{{< nextlink href="/monitors/types/cloud_network_monitoring" >}}Cloud Network Monitoring: Set alerts on your network traffic.{{< /nextlink >}} {{< nextlink href="/monitors/types/netflow" >}}NetFlow: Monitor flow records from your NetFlow-enabled devices.{{< /nextlink >}} {{< nextlink href="/monitors/types/outlier" >}}Outlier: Alert on members of a group behaving differently than the others.{{< /nextlink >}} {{< nextlink href="/monitors/types/process_check" >}}Process Check: Watch the status produced by the process.up service check.{{< /nextlink >}} diff --git a/content/en/monitors/types/network_performance.md b/content/en/monitors/types/cloud_network_monitoring.md similarity index 82% rename from content/en/monitors/types/network_performance.md rename to content/en/monitors/types/cloud_network_monitoring.md index 2b3d6041d1a3a..88983a574c228 100644 --- a/content/en/monitors/types/network_performance.md +++ b/content/en/monitors/types/cloud_network_monitoring.md @@ -1,9 +1,11 @@ --- -title: Network Performance Monitor +title: Cloud Networking Monitor +aliases: +- /monitors/types/network_performance/ further_reading: -- link: "/network_monitoring/performance/" +- link: "/network_monitoring/cloud_network_monitoring/" tag: "Documentation" - text: "Learn more about Network Performance Monitoring" + text: "Learn more about Cloud Network Monitoring" - link: "/monitors/notify/" tag: "Documentation" text: "Configure your monitor notifications" @@ -15,40 +17,40 @@ further_reading: text: "Check your monitor status" - link: "/monitors/recommended/" tag: "Documentation" - text: "Recommended NPM Monitors" + text: "Recommended CNM Monitors" --- ## Overview -Datadog [Network Performance Monitoring][1] (NPM) provides visibility into your network traffic between services, containers, availability zones, and any other tag in Datadog. After you enable NPM, you can create an NPM monitor and get alerted if a TCP network metric crosses a threshold that you have set. For example, you can monitor network throughput between a specific client/server and get alerted if that throughput crosses a threshold. +Datadog [Cloud Network Monitoring][1] (CNM) provides visibility into your network traffic between services, containers, availability zones, and any other tag in Datadog. After you enable CNM, you can create a CNM monitor and get alerted if a TCP network metric crosses a threshold that you have set. For example, you can monitor network throughput between a specific client/server and get alerted if that throughput crosses a threshold. ## Monitor creation -To create an NPM monitor in Datadog, use the main navigation: [**Monitors** --> **New Monitor** --> **Network Performance**][2]. +To create a CNM monitor in Datadog, use the main navigation: [**Monitors** --> **New Monitor** --> **Cloud Network**][2]. ### Define the search query {{< img src="monitors/monitor_types/network_performance/example_dns_failures.png" alt="Example configuration with auto-grouped client and server traffic, hidden N/A values, measured as the sum of DNS failures metric with a limit of 100" style="width:100%;" >}} -1. Construct a search query using the same logic as the [NPM analytics][3] search bar. +1. Construct a search query using the same logic as the [CNM analytics][3] search bar. 1. Select the tags you want to group your client and server by. 1. Choose if you want to show or hide N/A traffic. -1. Select a metric you want to measure from the dropdown list. By default, the monitor measures the sum of the metric selected. See which metrics are available for NPM monitors in the [metric definitions](#metric-definitions). +1. Select a metric you want to measure from the dropdown list. By default, the monitor measures the sum of the metric selected. See which metrics are available for CNM monitors in the [metric definitions](#metric-definitions). 1. Set the limit on how many results you want to be included in the query. ### Using formulas and functions -You can create NPM monitors using formulas and functions. This can be used, for example, to create monitors on throughput between a client and server. +You can create CNM monitors using formulas and functions. This can be used, for example, to create monitors on throughput between a client and server. The following example shows using a formula to calculate percent retransmits from a client to server. -{{< img src="monitors/monitor_types/network_performance/npm_formulas_functions.png" alt="Example NPM monitor configuration showing percent of retransmits from a client to server" style="width:100%;" >}} +{{< img src="monitors/monitor_types/network_performance/npm_formulas_functions.png" alt="Example CNM monitor configuration showing percent of retransmits from a client to server" style="width:100%;" >}} For more information, see the [Functions][4] documentation. ## Metric definitions -The following tables list the different NPM metrics you can create monitors on. +The following tables list the different CNM metrics you can create monitors on. ### Volume | Metric name | Definition | @@ -93,7 +95,7 @@ Configure monitors to trigger if the query value crosses a threshold and customi For detailed instructions on the **Configure notifications and automations** section, see the [Notifications][6] page. ## Common monitors -You can start creating monitors on NPM with the following common monitors. These provide a good starting point to track your network and get alerted if your network is experiencing unusual traffic and potentially experiencing unexpected network behavior. +You can start creating monitors on CNM with the following common monitors. These provide a good starting point to track your network and get alerted if your network is experiencing unusual traffic and potentially experiencing unexpected network behavior. ### Throughput monitor The throughput monitor alerts you if throughput between two endpoints specified in the query surpasses a threshold. Monitoring throughput can help you determine if your network is nearing capacity given your network bandwidth. Knowing this can give you enough time to make adjustments to your network to avoid bottlenecks and other effects downstream. @@ -114,9 +116,9 @@ DNS failure monitor tracks DNS server performance to help you identify server-si {{< partial name="whats-next/whats-next.html" >}} -[1]: /network_monitoring/performance/ +[1]: /network_monitoring/cloud_network_monitoring/ [2]: https://app.datadoghq.com/monitors/create/network-performance -[3]: /network_monitoring/performance/network_analytics/ +[3]: /network_monitoring/cloud_network_monitoring/network_analytics/ [4]: /dashboards/functions/ [5]: /monitors/configuration/ [6]: /monitors/notify/ diff --git a/content/en/network_monitoring/_index.md b/content/en/network_monitoring/_index.md index dd555d115e412..fb0bddd5e6eaf 100644 --- a/content/en/network_monitoring/_index.md +++ b/content/en/network_monitoring/_index.md @@ -11,7 +11,7 @@ further_reading: text: "Join an interactive session to better monitor your network performance" - link: "https://www.datadoghq.com/blog/network-performance-monitoring" tag: "Blog" - text: "Introducing Datadog Network Performance Monitoring" + text: "Introducing Datadog Cloud Network Monitoring" - link: 'https://www.datadoghq.com/blog/monitor-dns-with-datadog/' tag: 'Blog' text: 'Monitor DNS with Datadog' @@ -28,11 +28,11 @@ cascade: {{< learning-center-callout header="Join an enablement webinar session" hide_image="true" btn_title="Sign Up" btn_url="https://www.datadoghq.com/technical-enablement/sessions/?tags.topics-0=NPM">}} - Learn how Datadog Network Performance Monitoring provides full visibility into every network component that makes up your on-prem, cloud, and hybrid environments, with minimal overhead. + Learn how Datadog Cloud Network Monitoring provides full visibility into every network component that makes up your on-prem, cloud, and hybrid environments, with minimal overhead. {{< /learning-center-callout >}} {{< whatsnext desc="This section includes the following topics:">}} - {{< nextlink href="network_monitoring/performance" >}}Network Performance Monitoring: Explore metrics for point to point communication on your infrastructure.{{< /nextlink >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring" >}}Cloud Network Monitoring: Explore metrics for point to point communication on your infrastructure.{{< /nextlink >}} {{< nextlink href="network_monitoring/dns" >}}DNS Monitoring: Diagnose and debug DNS server issues.{{< /nextlink >}} {{< nextlink href="network_monitoring/devices" >}}Network Device Monitoring: Gain visibility into your network-connected devices, such as routers, switches, servers, and firewalls.{{< /nextlink >}} {{< /whatsnext >}} diff --git a/content/en/network_monitoring/performance/_index.md b/content/en/network_monitoring/cloud_network_monitoring/_index.md similarity index 60% rename from content/en/network_monitoring/performance/_index.md rename to content/en/network_monitoring/cloud_network_monitoring/_index.md index c15f184ee3c16..59fb109db3539 100644 --- a/content/en/network_monitoring/performance/_index.md +++ b/content/en/network_monitoring/cloud_network_monitoring/_index.md @@ -1,32 +1,33 @@ --- -title: Network Performance Monitoring +title: Cloud Network Monitoring description: Explore metrics for point to point communication on your infrastructure. aliases: - /monitors/network_flow_monitors/ - /graphing/infrastructure/network_performance_monitor/ - /network_performance_monitoring/ + - /network_monitoring/performance/ further_reading: - link: "https://www.datadoghq.com/blog/cloud-network-monitoring-datadog/" tag: "Blog" - text: "Monitor cloud architecture and app dependencies with Datadog NPM" + text: "Monitor cloud architecture and app dependencies with Datadog CNM" - link: "https://www.datadoghq.com/blog/network-performance-monitoring" tag: "Blog" - text: "Network Performance Monitoring" + text: "Cloud Network Monitoring" - link: "https://www.datadoghq.com/blog/npm-windows-support/" tag: "Blog" - text: "Monitor Windows hosts with Network Performance Monitoring" + text: "Monitor Windows hosts with Cloud Network Monitoring" - link: "https://www.datadoghq.com/blog/cloud-service-autodetection-datadog/" tag: "Blog" text: "Monitor cloud endpoint health with cloud service autodetection" - link: "https://www.datadoghq.com/blog/npm-best-practices/" tag: "Blog" - text: "Best practices for getting started with Datadog NPM" + text: "Best practices for getting started with Datadog CNM" - link: "https://www.datadoghq.com/blog/monitor-consul-with-datadog-npm/" tag: "Blog" - text: "Datadog NPM now supports Consul networking" + text: "Datadog CNM now supports Consul networking" - link: "https://www.datadoghq.com/blog/npm-story-centric-ux/" tag: "Blog" - text: "Quickstart network investigations with NPM's story-centric UX" + text: "Quickstart network investigations with CNM's story-centric UX" - link: "https://www.datadoghq.com/blog/monitor-dns-logs-for-network-and-security-datadog/" tag: "Blog" text: "Monitor DNS logs for network and security analysis" @@ -37,29 +38,29 @@ further_reading: tag: "Architecture Center" text: "Network Observability: SD-WAN Reference Architecture" algolia: - tags: ['npm', 'network performance monitoring'] + tags: ['Cloud Network Monitoring', 'Network Performance Monitoring', 'CNM', 'NPM'] --- ## Overview {{< vimeo url="https://player.vimeo.com/progressive_redirect/playback/670228207/rendition/1080p/file.mp4?loc=external&signature=42d4a7322017fffa6d5cc2e49ddbb7cfc4c6bbbbf207d13a5c9830630bda4ece" poster="/images/poster/npm.png" >}} -Datadog Network Performance Monitoring (NPM) gives you visibility into your network traffic between services, containers, availability zones, and any other tag in Datadog. Connection data at the IP, port, and PID levels is aggregated into application-layer dependencies between meaningful client and server endpoints, which can be analyzed and visualized through a customizable [network page][1] and [network map][2]. Use flow data along with key network traffic and DNS server metrics to: +Datadog Cloud Network Monitoring (CNM) gives you visibility into your network traffic between services, containers, availability zones, and any other tag in Datadog. Connection data at the IP, port, and PID levels is aggregated into application-layer dependencies between meaningful client and server endpoints, which can be analyzed and visualized through a customizable [network page][1] and [network map][2]. Use flow data along with key network traffic and DNS server metrics to: * Pinpoint unexpected or latent service dependencies * Optimize costly cross-regional or multi-cloud communication * Identify outages of cloud provider regions and third-party tools * Troubleshoot client-side and server-side DNS server issues -NPM makes it simple to monitor complex networks with built in support for Linux and [Windows OS][3] as well as containerized environments that are orchestrated and [instrumented with Istio service mesh][4]. +CNM makes it simple to monitor complex networks with built in support for Linux and [Windows OS][3] as well as containerized environments that are orchestrated and [instrumented with Istio service mesh][4]. -Additionally, [Network path][5], a feature of NPM, is available in Preview, which allows you to see hop-by-hop traffic in your network. +Additionally, [Network path][5], a feature of CNM, is available in Preview, which allows you to see hop-by-hop traffic in your network. {{< whatsnext desc="This section includes the following topics:">}} - {{< nextlink href="network_monitoring/performance/setup" >}}Setup: Configure the Agent to collect network data.{{< /nextlink >}} - {{< nextlink href="network_monitoring/performance/network_analytics" >}}Network Analytics: Graph your network data between each client and server available.{{< /nextlink >}} - {{< nextlink href="network_monitoring/performance/network_map" >}}Network Map: Map your network data between your tags.{{< /nextlink >}} - {{< nextlink href="monitors/types/network_performance/" >}}Recommended Monitors: Configure recommended NPM monitors.{{< /nextlink >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring/setup" >}}Setup: Configure the Agent to collect network data.{{< /nextlink >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring/network_analytics" >}}Network Analytics: Graph your network data between each client and server available.{{< /nextlink >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring/network_map" >}}Network Map: Map your network data between your tags.{{< /nextlink >}} + {{< nextlink href="monitors/types/cloud_network_monitoring/" >}}Recommended Monitors: Configure recommended CNM monitors.{{< /nextlink >}} {{< /whatsnext >}} ## Further Reading diff --git a/content/en/network_monitoring/cloud_network_monitoring/guide/_index.md b/content/en/network_monitoring/cloud_network_monitoring/guide/_index.md new file mode 100644 index 0000000000000..1ce98b8d056cf --- /dev/null +++ b/content/en/network_monitoring/cloud_network_monitoring/guide/_index.md @@ -0,0 +1,15 @@ +--- +title: Cloud Network Monitoring Guides +aliases: + - /network_performance_monitoring/guide/ +private: true +disable_toc: true +--- + +{{< whatsnext desc="General Guides:" >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring/guide/manage_traffic_costs_with_cnm" >}}Manage traffic costs with CNM{{< /nextlink >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring/guide/detecting_a_network_outage" >}}Detecting a Network Outage{{< /nextlink >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring/guide/aws_supported_services/" >}}CNM AWS Supported Services{{< /nextlink >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring/guide/gcp_supported_services/" >}}CNM Google Cloud Supported Services{{< /nextlink >}} + {{< nextlink href="network_monitoring/cloud_network_monitoring/guide/azure_supported_services/" >}}CNM Azure Supported Services{{< /nextlink >}} +{{< /whatsnext >}} diff --git a/content/en/network_monitoring/performance/guide/aws_supported_services.md b/content/en/network_monitoring/cloud_network_monitoring/guide/aws_supported_services.md similarity index 55% rename from content/en/network_monitoring/performance/guide/aws_supported_services.md rename to content/en/network_monitoring/cloud_network_monitoring/guide/aws_supported_services.md index 88c76b9ff40fa..9ecf91ad33279 100644 --- a/content/en/network_monitoring/performance/guide/aws_supported_services.md +++ b/content/en/network_monitoring/cloud_network_monitoring/guide/aws_supported_services.md @@ -1,16 +1,18 @@ --- -title: NPM AWS Supported Services +title: CNM AWS Supported Services +aliases: + - /network_monitoring/performance/guide/aws_supported_services npm_provider: aws further_reading: - link: 'https://www.datadoghq.com/blog/network-performance-monitoring' tag: 'Blog' - text: 'Network Performance Monitoring' + text: 'Cloud Network Monitoring' - link: '/network_monitoring/devices' tag: 'Documentation' text: 'Network Device Monitoring' --- -Datadog Network Performance Monitoring (NPM) automatically detects S3, RDS, Kinesis, ELB, Elasticache, and other AWS services listed below: +Datadog Cloud Network Monitoring (CNM) automatically detects S3, RDS, Kinesis, ELB, Elasticache, and other AWS services listed below: {{< get-npm-integrations "aws" >}} diff --git a/content/en/network_monitoring/performance/guide/azure_supported_services.md b/content/en/network_monitoring/cloud_network_monitoring/guide/azure_supported_services.md similarity index 53% rename from content/en/network_monitoring/performance/guide/azure_supported_services.md rename to content/en/network_monitoring/cloud_network_monitoring/guide/azure_supported_services.md index ec5460b0f0aec..ad43f8d5d2269 100644 --- a/content/en/network_monitoring/performance/guide/azure_supported_services.md +++ b/content/en/network_monitoring/cloud_network_monitoring/guide/azure_supported_services.md @@ -1,16 +1,18 @@ --- -title: NPM Azure Supported Services +title: CNM Azure Supported Services +aliases: + - /network_monitoring/performance/guide/azure_supported_services npm_provider: azure further_reading: - link: 'https://www.datadoghq.com/blog/network-performance-monitoring' tag: 'Blog' - text: 'Network Performance Monitoring' + text: 'Cloud Network Monitoring' - link: '/network_monitoring/devices' tag: 'Documentation' text: 'Network Device Monitoring' --- -Datadog Network Performance Monitoring (NPM) automatically detects API calls to Azure Blob Storage, Cosmos, Postgres and other Azure services listed below: +Datadog Cloud Network Monitoring (CNM) automatically detects API calls to Azure Blob Storage, Cosmos, Postgres and other Azure services listed below: {{< get-npm-integrations "azure" >}} diff --git a/content/en/network_monitoring/performance/guide/detecting_a_network_outage.md b/content/en/network_monitoring/cloud_network_monitoring/guide/detecting_a_network_outage.md similarity index 84% rename from content/en/network_monitoring/performance/guide/detecting_a_network_outage.md rename to content/en/network_monitoring/cloud_network_monitoring/guide/detecting_a_network_outage.md index cec1090f3443c..ff23890294fd5 100644 --- a/content/en/network_monitoring/performance/guide/detecting_a_network_outage.md +++ b/content/en/network_monitoring/cloud_network_monitoring/guide/detecting_a_network_outage.md @@ -2,14 +2,15 @@ title: Detecting a Network Outage aliases: - /network_performance_monitoring/guide/detecting_a_network_outage/ + - /network_monitoring/performance/guide/detecting_a_network_outage/ --- Network outages are often disguised as infrastructure, application, or container issues, which makes them hard to detect. Without visibility into your regional network performance or that of third-party endpoints you rely on, it may take hours to detect third-party or cloud regional outages, which could ultimately affect your customers. -With Network Performance Monitoring (NPM), you can detect network outages in minutes. By analyzing network flow data alongside process metrics, traces, logs, and infrastructure metrics, you can avoid making assumptions about the root of an issue, and instead use process of elimination (see the steps below) to determine whether you're experiencing a network outage. +With Cloud Network Monitoring (CNM), you can detect network outages in minutes. By analyzing network flow data alongside process metrics, traces, logs, and infrastructure metrics, you can avoid making assumptions about the root of an issue, and instead use process of elimination (see the steps below) to determine whether you're experiencing a network outage. ## Traffic overloading the underlying infrastructure -Use NPM metrics to see whether your source endpoint may be sending an enormous amount of traffic or making a large number of open connections to the destination endpoint. When selecting a faulty dependency (for example, one with high latency), you can use the side panel graphs to spot such spikes in traffic. These spikes may overwhelm your receiving application to the point that it cannot (in the case of TCP) respond to all connections, leading to increased packet loss and thus, increased TCP latency. +Use CNM metrics to see whether your source endpoint may be sending an enormous amount of traffic or making a large number of open connections to the destination endpoint. When selecting a faulty dependency (for example, one with high latency), you can use the side panel graphs to spot such spikes in traffic. These spikes may overwhelm your receiving application to the point that it cannot (in the case of TCP) respond to all connections, leading to increased packet loss and thus, increased TCP latency. {{< img src="network_performance_monitoring/guide/detecting_a_network_outage/npm-metrics.png" alt="Traffic overloading of the underlying infrastructure">}} @@ -21,7 +22,7 @@ On the other hand, resource overconsumption of either the client or server endpo ## Application errors in code -Network errors and latency can also be caused by client-side application errors. For instance, if your application is generating connections on loop unnecessarily, it could be overwhelming the endpoints that rely on it, leading to downstream application and network issues. To determine whether this is the case, look for application request errors in the **Traces** tab of a specific service in [NPM > DNS][1], or the **Network** tab of a specific trace in APM Traces. +Network errors and latency can also be caused by client-side application errors. For instance, if your application is generating connections on loop unnecessarily, it could be overwhelming the endpoints that rely on it, leading to downstream application and network issues. To determine whether this is the case, look for application request errors in the **Traces** tab of a specific service in [CNM > DNS][1], or the **Network** tab of a specific trace in APM Traces. {{< img src="network_performance_monitoring/guide/detecting_a_network_outage/traces_2.png" alt="Application errors in code">}} diff --git a/content/en/network_monitoring/performance/guide/gcp_supported_services.md b/content/en/network_monitoring/cloud_network_monitoring/guide/gcp_supported_services.md similarity index 53% rename from content/en/network_monitoring/performance/guide/gcp_supported_services.md rename to content/en/network_monitoring/cloud_network_monitoring/guide/gcp_supported_services.md index 87dff2132b4a2..3360ccd09f5a2 100644 --- a/content/en/network_monitoring/performance/guide/gcp_supported_services.md +++ b/content/en/network_monitoring/cloud_network_monitoring/guide/gcp_supported_services.md @@ -1,16 +1,18 @@ --- -title: NPM Google Cloud Supported Services +title: CNM Google Cloud Supported Services +aliases: + - /network_monitoring/performance/guide/gcp_supported_services npm_provider: gcp further_reading: - link: 'https://www.datadoghq.com/blog/network-performance-monitoring' tag: 'Blog' - text: 'Network Performance Monitoring' + text: 'Cloud Network Monitoring' - link: '/network_monitoring/devices' tag: 'Documentation' text: 'Network Device Monitoring' --- -Datadog Network Performance Monitoring (NPM) automatically detects API calls to AppEngine, Google DNS, Gmail, and other GCP services listed below: +Datadog Cloud Network Monitoring (CNM) automatically detects API calls to AppEngine, Google DNS, Gmail, and other GCP services listed below: {{< get-npm-integrations "gcp" >}} diff --git a/content/en/network_monitoring/performance/guide/manage_traffic_costs_with_npm.md b/content/en/network_monitoring/cloud_network_monitoring/guide/manage_traffic_costs_with_cnm.md similarity index 92% rename from content/en/network_monitoring/performance/guide/manage_traffic_costs_with_npm.md rename to content/en/network_monitoring/cloud_network_monitoring/guide/manage_traffic_costs_with_cnm.md index 96b7c184b74ee..de87cbaa98639 100644 --- a/content/en/network_monitoring/performance/guide/manage_traffic_costs_with_npm.md +++ b/content/en/network_monitoring/cloud_network_monitoring/guide/manage_traffic_costs_with_cnm.md @@ -1,11 +1,12 @@ --- -title: Manage Cloud Traffic Costs with NPM +title: Manage Cloud Traffic Costs with CNM aliases: - /network_performance_monitoring/guide/manage_traffic_costs_with_npm/ + - /network_monitoring/performance/guide/manage_traffic_costs_with_npm/ --- Traffic is expensive, especially in the cloud. Cloud providers charge different prices for traffic, depending on whether it is flowing within an availability zone (AZ), between AZs, between particular regions, or to the open internet. Cross-regional and egress traffic is not only the most expensive, but also the most vulnerable to errors, latency, and security threats. -Network Performance Monitoring (NPM) allows you to track all of the traffic patterns described above by mapping dependencies between any tags in Datadog, including service, container, availability zone, region, datacenter, etc. This insight into your dependencies and the traffic volume they produce (which is ultimately what cloud providers charge for) can be used to monitor and optimize your traffic-related costs. +Cloud Network Monitoring (CNM) allows you to track all of the traffic patterns described above by mapping dependencies between any tags in Datadog, including service, container, availability zone, region, datacenter, etc. This insight into your dependencies and the traffic volume they produce (which is ultimately what cloud providers charge for) can be used to monitor and optimize your traffic-related costs. ## Datadog's story diff --git a/content/en/network_monitoring/performance/network_analytics.md b/content/en/network_monitoring/cloud_network_monitoring/network_analytics.md similarity index 92% rename from content/en/network_monitoring/performance/network_analytics.md rename to content/en/network_monitoring/cloud_network_monitoring/network_analytics.md index 43a3cf6199508..e0c5526b7cf73 100644 --- a/content/en/network_monitoring/performance/network_analytics.md +++ b/content/en/network_monitoring/cloud_network_monitoring/network_analytics.md @@ -5,17 +5,18 @@ aliases: - /network_performance_monitoring/network_table - /network_performance_monitoring/network_page - /network_monitoring/performance/network_page + - /network_monitoring/performance/network_analytics further_reading: - link: 'https://www.datadoghq.com/blog/network-performance-monitoring' tag: 'Blog' - text: 'Network Performance Monitoring' + text: 'Cloud Network Monitoring' - link: 'https://www.datadoghq.com/blog/datadog-npm-search-map-updates/' tag: 'Blog' text: 'Streamline network investigations with an enhanced querying and map experience' - link: '/network_monitoring/devices' tag: 'Documentation' text: 'Network Device Monitoring' - - link: '/network_monitoring/performance/setup' + - link: '/network_monitoring/cloud_network_monitoring/setup' tag: 'Documentation' text: 'Collect your Network Data with the Datadog Agent.' --- @@ -24,7 +25,7 @@ further_reading: The Network Analytics page provides insights into your overall network health and shows [recommended queries](#recommended-queries) at the top of the page. These recommended queries enable you to run common queries and see snapshots of relevant metrics, so that you can see changes in throughput, latency, DNS errors, and more. Clicking on a recommended query automatically populates the search bar, group bys, and summary graphs to provide you with relevant insights into your network. -{{< img src="network_performance_monitoring/network_analytics/main_page_npm_4.png" alt="Network Analytics landing page under Network Performance" >}} +{{< img src="network_performance_monitoring/network_analytics/cnm_network_analytics_2.png" alt="Network Analytics landing page under Cloud Network Monitoring" >}} ## Queries @@ -44,21 +45,21 @@ Additionally, the following diagram illustrates inbound and outbound requests wh The following screenshot shows the default view, which aggregates the client and server by the `service` tag. Accordingly, each row in the table represents service-to-service aggregate connections when aggregated over a one hour time period. Select "Auto-grouped traffic" to see traffic bucketed into several commonly used tags such as `service`, `kube_service`, `short_image`, and `container_name`. -{{< img src="network_performance_monitoring/network_analytics/context_npm3.png" alt="Query interface, with the inputs 'Search for', 'View clients as', and 'View servers as'" style="width:90%;">}} +{{< img src="network_performance_monitoring/network_analytics/cnm_default_view_2.png" alt="CNM default view with drop downs showing view clients and servers as auto grouped traffic" style="width:90%;">}} The next example shows all aggregate connections from IP addresses representing services in region `us-east-1` to availability zones: -{{< img src="network_performance_monitoring/network_analytics/flow_table_region_az2.png" alt="Aggregate connection table filtered" style="width:80%;">}} +{{< img src="network_performance_monitoring/network_analytics/cnm_flow_table_region_2.png" alt="Aggregate connection table filtered" style="width:90%;">}} You can further aggregate to isolate to traffic where the client or server matches a CIDR using `CIDR(network.client.ip, 10.0.0.0/8)` or `CIDR(network.server.ip, 10.0.0.0/8)`. Additionally, set the timeframe over which traffic is aggregated using the time selector at the top right of the page: -{{< img src="network_performance_monitoring/network_analytics/npm_timeframe.png" alt="Time frame NPM" style="width:30%;">}} +{{< img src="network_performance_monitoring/network_analytics/npm_timeframe.png" alt="Time frame CNM" style="width:30%;">}} ### Recommended queries -{{< img src="network_performance_monitoring/network_analytics/recommended_query_options.png" alt="The Network Analytics page in Datadog displaying three recommended queries">}} +{{< img src="network_performance_monitoring/network_analytics/recommended_queries_2.png" alt="The Network Analytics page in Datadog displaying three recommended queries">}} Recommended queries allow you to begin investigating into your network—whether you're troubleshooting a specific issue or gaining a better overall understanding of your network. The recommended queries help you quickly find relevant network information without needing to search for or group the traffic. For example, the recommended query `Find dependencies of service: web-store` populates the search bar with the query `client_service: web-store` and displays the top services that the service web-store is sending traffic to within the network, and therefore its downstream dependencies. @@ -107,11 +108,11 @@ Groups allow you to group your data by a given tag's value. For example, if you If you want to investigate connections from all of your hosts in a single grouping, add the `host` tag in the **View clients as** dropdown, and add `Ungrouped traffic` in the **View servers as** dropdown. -{{< img src="network_performance_monitoring/network_analytics/npm_un-grouped.png" alt="NPM analytics page sorting by host and grouped by Ungrouped traffic" style="width:90%;">}} +{{< img src="network_performance_monitoring/network_analytics/cnm_un-grouped.png" alt="NPM analytics page sorting by host and grouped by Ungrouped traffic" style="width:90%;">}} If you have traffic that is not tagged by a specific group, you can select **Auto-grouped traffic** to group data by any available tags. For example, to see which tags are available for a specific `service`, use the `service` tag in the **View clients as** dropdown, and add `Auto-grouped traffic` in the **View servers as** dropdown: -{{< img src="network_performance_monitoring/network_analytics/npm_auto-grouped.png" alt="NPM analytics page sorting by service tags" style="width:90%;">}} +{{< img src="network_performance_monitoring/network_analytics/cnm_auto-grouped.png" alt="NPM analytics page sorting by service tags" style="width:90%;">}} The **Auto-grouped traffic** option can help you identify the source of your tags. For example, hover over the individual icons to display a tooltip that indicates the tag's origin: @@ -119,7 +120,7 @@ The **Auto-grouped traffic** option can help you identify the source of your tag Using the search bar and the group by feature together is helpful to further isolate your network traffic. For example, to find all traffic from your `auth-dotnet` service across all data centers, enter `service:auth-dotnet` in the search bar and select `datacenter` in the **View clients** as dropdown: -{{< img src="network_performance_monitoring/network_analytics/search_bar_with_groupby.png" alt="Using group by option with search field" style="width:90%;">}} +{{< img src="network_performance_monitoring/network_analytics/search_bar_with_groupby_2.png" alt="Using group by option with search field" style="width:90%;">}} ## Summary graphs @@ -187,7 +188,7 @@ For instance, you can: - Pivot to the [Network Page](#table) to isolate which pods are establishing the most connections to that service, and - Validate that their request is successful by analyzing S3 performance metrics, which are correlated with traffic performance directly in the side panel for a given dependency, under the *Integration Metrics* tab. -NPM automatically maps: +CNM automatically maps: - Network calls to S3 (which can broken down by `s3_bucket`), RDS (which can be broken down by `rds_instance_type`), Kinesis, ELB, Elasticache, and other [AWS services][3]. - API calls to AppEngine, Google DNS, Gmail, and other [Google Cloud services][4]. @@ -195,7 +196,7 @@ NPM automatically maps: To monitor other endpoints where an Agent cannot be installed (such as public APIs), group the destination in the Network Overview by the [`domain` tag](#domain-resolution). Or, see the section below for cloud service resolution. ### Cloud service enhanced resolution -If you have [setup][9] enhanced resolution for AWS or Azure, NPM can filter and group network traffic with several resources collected from these cloud providers. Depending on the cloud provider and resource, you have different sets of tags available to query with. Datadog applies the tags defined below in addition to the user-defined tags. +If you have [setup][9] enhanced resolution for AWS or Azure, CNM can filter and group network traffic with several resources collected from these cloud providers. Depending on the cloud provider and resource, you have different sets of tags available to query with. Datadog applies the tags defined below in addition to the user-defined tags. #### Amazon Web Services {{< tabs >}} @@ -258,7 +259,7 @@ If you have [setup][9] enhanced resolution for AWS or Azure, NPM can filter and Starting with Agent 7.17+, the Agent resolves IPs to human-readable domain names for external and internal traffic. Domain allows you to monitor cloud provider endpoints where a Datadog Agent cannot be installed, such as S3 buckets, application load balancers, and APIs. Unrecognizable domain names such as DGA domains from C&C servers may point to network security threats. `domain` **is encoded as a tag in Datadog**, so you can use it in search bar queries and the facet panel to aggregate and filter traffic. -{{< img src="network_performance_monitoring/network_analytics/domain_aggregation2.png" alt="Domain aggregation" >}} +{{< img src="network_performance_monitoring/network_analytics/domain_aggregation_3.png" alt="Domain aggregation" >}} **Note**: DNS resolution is supported for hosts where the system probe is running on the root network namespace, which is usually caused by running the system-probe in a container without using the host network. @@ -272,9 +273,9 @@ To view pre-NAT and post-NAT IPs, use the **Show pre-NAT IPs** toggle in the tab ### Network ID -NPM users may configure their networks to have overlapping IP spaces. For instance, you may want to deploy in multiple VPCs (virtual private clouds) which have overlapping address ranges and communicate only through load balancers or cloud gateways. +CNM users may configure their networks to have overlapping IP spaces. For instance, you may want to deploy in multiple VPCs (virtual private clouds) which have overlapping address ranges and communicate only through load balancers or cloud gateways. -To correctly classify traffic destinations, NPM uses the concept of a network ID, which is represented as a tag. A network ID is an alphanumeric identifier for a set of IP addresses that can communicate with one another. When an IP address mapping to several hosts with different network IDs is detected, this identifier is used to determine the particular host network traffic is going to or coming from. +To correctly classify traffic destinations, CNM uses the concept of a network ID, which is represented as a tag. A network ID is an alphanumeric identifier for a set of IP addresses that can communicate with one another. When an IP address mapping to several hosts with different network IDs is detected, this identifier is used to determine the particular host network traffic is going to or coming from. In AWS and Google Cloud, the network ID is automatically set to the VPC ID. For other environments, the network ID may be set manually, either in `datadog.yaml` as shown below, or by adding the `DD_NETWORK_ID` to the process and core Agent containers. @@ -287,7 +288,7 @@ In AWS and Google Cloud, the network ID is automatically set to the VPC ID. For Organize and share views of traffic data. Saved Views make debugging faster and empower collaboration. For instance, you can create a view, save it for the future for common queries, and copy its link to share network data with your teammates. -{{< img src="network_performance_monitoring/network_analytics/npm_saved_views2.png" alt="Saved Views" >}} +{{< img src="network_performance_monitoring/network_analytics/cnm_saved_views.png" alt="Cloud Network Monitoring Saved Views" >}} - To save a view: click the *+ Save* button and name the view to record your current query, table configuration, and graph metric selections. - To load a view: click *Views* at the top left to see your Saved Views and select a view from the list. @@ -327,9 +328,9 @@ Select any row from the data table to see associated logs, traces, and processes ### Pivot to network path -Hover over a row in the analytics table to pivot to [network path][11] and see the paths between the source and destination specified in NPM. +Hover over a row in the analytics table to pivot to [network path][11] and see the paths between the source and destination specified in CNM. -{{< img src="network_performance_monitoring/network_analytics/view_network_path.png" alt="Example of hovering over a row in the Analytics table to show the Network Path toggle" style="width:90%;">}} +{{< img src="network_performance_monitoring/network_analytics/view_network_path_2.png" alt="Example of hovering over a row in the Analytics table to show the Network Path toggle" style="width:90%;">}} ## Sidepanel @@ -355,14 +356,14 @@ The **Security** tab highlights potential network threats and findings detected {{< partial name="whats-next/whats-next.html" >}} [1]: /logs/search_syntax/ -[2]: /network_monitoring/performance/network_map/ -[3]: /network_monitoring/performance/guide/aws_supported_services/ -[4]: /network_monitoring/performance/guide/gcp_supported_services/ +[2]: /network_monitoring/cloud_network_monitoring/network_map/ +[3]: /network_monitoring/cloud_network_monitoring/guide/aws_supported_services/ +[4]: /network_monitoring/cloud_network_monitoring/guide/gcp_supported_services/ [5]: /logs/explorer/saved_views/ [6]: /security/threats/ [7]: /security/cloud_security_management/misconfigurations/ [8]: /security/detection_rules/ -[9]: /network_monitoring/performance/setup/#enhanced-resolution +[9]: /network_monitoring/cloud_network_monitoring/setup/#enhanced-resolution [10]: /network_monitoring/dns/#recommended-queries [11]: /network_monitoring/network_path [12]: /getting_started/tagging/unified_service_tagging/ diff --git a/content/en/network_monitoring/performance/network_map.md b/content/en/network_monitoring/cloud_network_monitoring/network_map.md similarity index 96% rename from content/en/network_monitoring/performance/network_map.md rename to content/en/network_monitoring/cloud_network_monitoring/network_map.md index 174b84751b466..7c8c6c53de7dc 100644 --- a/content/en/network_monitoring/performance/network_map.md +++ b/content/en/network_monitoring/cloud_network_monitoring/network_map.md @@ -3,17 +3,18 @@ title: Network Map description: Map your Network data across all your tags. aliases: - /network_performance_monitoring/network_map/ + - /network_monitoring/performance/network_map further_reading: - link: 'https://www.datadoghq.com/blog/network-performance-monitoring' tag: 'Blog' - text: 'Network Performance Monitoring' + text: 'Cloud Network Monitoring' - link: 'https://www.datadoghq.com/blog/datadog-npm-search-map-updates/' tag: 'Blog' text: 'Streamline network investigations with an enhanced querying and map experience' - link: '/network_monitoring/devices' tag: 'Documentation' text: 'Network Device Monitoring' - - link: '/network_monitoring/performance/setup' + - link: '/network_monitoring/cloud_network_monitoring/setup' tag: 'Documentation' text: 'Collect your Network Data with the Datadog Agent.' --- diff --git a/content/en/network_monitoring/performance/overview_page.md b/content/en/network_monitoring/cloud_network_monitoring/overview_page.md similarity index 88% rename from content/en/network_monitoring/performance/overview_page.md rename to content/en/network_monitoring/cloud_network_monitoring/overview_page.md index 35fd31fa838e1..7ffcd86653603 100644 --- a/content/en/network_monitoring/performance/overview_page.md +++ b/content/en/network_monitoring/cloud_network_monitoring/overview_page.md @@ -1,17 +1,19 @@ --- title: Overview Page -description: The Network Performance Monitoring Overview Page in the Datadog UI. +description: The Cloud Network Monitoring Overview Page in the Datadog UI. +aliases: + - /network_monitoring/performance/overview_page further_reading: - link: 'https://www.datadoghq.com/blog/network-performance-monitoring' tag: 'Blog' - text: 'Network Performance Monitoring' + text: 'Cloud Network Monitoring' --- ## Overview -The [NPM overview page][3] provides a high-level overview of your network, from costly network traffic to DNS health to service top talkers. Use the Overview page to filter network traffic by environment or team with tags, and adjust the time frame for your network data. +The [CNM overview page][3] provides a high-level overview of your network, from costly network traffic to DNS health to service top talkers. Use the Overview page to filter network traffic by environment or team with tags, adjust the time frame for your network data and investigate your most expensive traffic. -{{< img src="/network_performance_monitoring/overview_page/overview_page_2.png" alt="The network overview page in Datadog" style="width:100%;">}} +{{< img src="/network_performance_monitoring/overview_page/cnm_overview_page_2.png" alt="The network overview page in Datadog" style="width:110%;">}} ## External network traffic diff --git a/content/en/network_monitoring/performance/setup.md b/content/en/network_monitoring/cloud_network_monitoring/setup.md similarity index 86% rename from content/en/network_monitoring/performance/setup.md rename to content/en/network_monitoring/cloud_network_monitoring/setup.md index 0921d7660f196..1e5f1cc2e0fe3 100644 --- a/content/en/network_monitoring/performance/setup.md +++ b/content/en/network_monitoring/cloud_network_monitoring/setup.md @@ -1,31 +1,32 @@ --- -title: Network Performance Monitoring Setup +title: Cloud Network Monitoring Setup description: Collect your Network Data with the Agent. aliases: - /network_performance_monitoring/installation/ + - /network_monitoring/performance/setup further_reading: - link: 'https://www.datadoghq.com/blog/network-performance-monitoring' tag: 'Blog' - text: 'Network Performance Monitoring' + text: 'Cloud Network Monitoring' - link: 'https://www.datadoghq.com/blog/monitor-containers-with-npm/' tag: 'Blog' - text: 'Datadog NPM with containers and service-meshed networks' + text: 'Datadog CNM with containers and service-meshed networks' - link: '/network_monitoring/devices' tag: 'Documentation' text: 'Network Device Monitoring' - link: "https://www.datadoghq.com/blog/monitor-consul-with-datadog-npm/" tag: "Blog" - text: "Datadog NPM now supports Consul networking" + text: "Datadog CNM now supports Consul networking" --- -Datadog Network Performance Monitoring (NPM) gives you visibility into your network traffic between services, containers, availability zones, and any other tag in Datadog so you can: +Datadog Cloud Network Monitoring (CNM) gives you visibility into your network traffic between services, containers, availability zones, and any other tag in Datadog so you can: - Pinpoint unexpected or latent service dependencies. - Optimize costly cross-regional or multi-cloud communication. - Identify outages of cloud provider regions and third-party tools. - Troubleshoot faulty service discovery with DNS server metrics. -Network Performance Monitoring requires [Datadog Agent v6.14+][1]. Because metrics are automatically collected in higher versions of the Agent, see the [metrics setup section][2] to configure DNS Monitoring. +Cloud Network Monitoring requires [Datadog Agent v6.14+][1]. Because metrics are automatically collected in higher versions of the Agent, see the [metrics setup section][2] to configure DNS Monitoring. ## Supported platforms @@ -33,7 +34,7 @@ Network Performance Monitoring requires [Datadog Agent v6.14+][1]. Because metri #### Linux OS -Data collection is done using eBPF, so Datadog minimally requires platforms that have underlying Linux kernel versions of 4.4.0+ or have eBPF features backported. NPM supports the following Linux distributions: +Data collection is done using eBPF, so Datadog minimally requires platforms that have underlying Linux kernel versions of 4.4.0+ or have eBPF features backported. CNM supports the following Linux distributions: - Ubuntu 16.04+ - Debian 9+ @@ -51,19 +52,19 @@ Data collection is done using a network kernel device driver. Support is availab #### macOS -Datadog Network Performance Monitoring does not support macOS platforms. +Datadog Cloud Network Monitoring does not support macOS platforms. ### Containers -NPM helps you visualize the architecture and performance of your containerized and orchestrated environments, with support for [Docker][5], [Kubernetes][6], [ECS][7], and other container technologies. Datadog's container integrations enable you to aggregate traffic by meaningful entities--such as containers, tasks, pods, clusters, and deployments--with out-of-the-box tags such as `container_name`, `task_name`, and `kube_service`. +CNM helps you visualize the architecture and performance of your containerized and orchestrated environments, with support for [Docker][5], [Kubernetes][6], [ECS][7], and other container technologies. Datadog's container integrations enable you to aggregate traffic by meaningful entities--such as containers, tasks, pods, clusters, and deployments--with out-of-the-box tags such as `container_name`, `task_name`, and `kube_service`. -NPM is not supported for Google Kubernetes Engine (GKE) Autopilot. +CNM is not supported for Google Kubernetes Engine (GKE) Autopilot. ### Network routing tools #### Istio -With NPM, you can map network communication between containers, pods, and services over the Istio service mesh. +With CNM, you can map network communication between containers, pods, and services over the Istio service mesh. Datadog monitors every aspect of your Istio environment, so you can also: @@ -71,19 +72,19 @@ Datadog monitors every aspect of your Istio environment, so you can also: - Break down the performance of your service mesh with request, bandwidth, and resource consumption [metrics][8]. - Examine distributed traces for applications transacting over the mesh with [APM][9]. -NPM supports Istio v1.6.4+ with [Datadog Agent v7.24.1+][1]. +CNM supports Istio v1.6.4+ with [Datadog Agent v7.24.1+][1]. To learn more about monitoring your Istio environment with Datadog, [see the Istio blog][10]. #### Cilium -Network Performance Monitoring is compatible with **Cilium** installations, provided the following requirements are met: +Cloud Network Monitoring is compatible with **Cilium** installations, provided the following requirements are met: 1) Cilium version 1.6 and above, and 2) Kernel version 5.1.16 and above, or 4.19.57 and above for 4.19.x kernels ### Provisioning systems -Network Performance Monitoring supports use of the following provisioning systems: +Cloud Network Monitoring supports use of the following provisioning systems: - Daemonset / Helm 1.38.11+: See the [Datadog Helm chart][11] - Chef 12.7+: See the [Datadog Chef recipe][12] @@ -96,7 +97,7 @@ Given this tool's focus and strength is in analyzing traffic _between_ network e {{< tabs >}} {{% tab "Agent (Linux)" %}} -To enable network performance monitoring with the Datadog Agent, use the following configurations: +To enable Cloud Network Monitoring with the Datadog Agent, use the following configurations: 1. **If you are using an agent older than v6.14+**, enable [live process collection][1] first, otherwise skip this step. @@ -111,7 +112,7 @@ To enable network performance monitoring with the Datadog Agent, use the followi ```yaml network_config: # use system_probe_config for Agent's older than 7.24.1 ## @param enabled - boolean - optional - default: false - ## Set to true to enable Network Performance Monitoring. + ## Set to true to enable Cloud Network Monitoring. # enabled: true ``` @@ -139,7 +140,7 @@ On systems with SELinux enabled, the system-probe binary needs special permissio The Datadog Agent RPM package for CentOS-based systems bundles an [SELinux policy][3] to grant these permissions to the system-probe binary. -If you need to use Network Performance Monitoring on other systems with SELinux enabled, do the following: +If you need to use Cloud Network Monitoring on other systems with SELinux enabled, do the following: 1. Modify the base [SELinux policy][3] to match your SELinux configuration. Depending on your system, some types or attributes may not exist (or have different names). @@ -179,11 +180,11 @@ If these utilities do not exist in your distribution, follow the same procedure Data collection for Windows relies on a filter driver for collecting network data. -To enable Network Performance Monitoring for Windows hosts: +To enable Cloud Network Monitoring for Windows hosts: 1. Install the [Datadog Agent][1] (version 7.27.1 or above) with the network driver component enabled. - [DEPRECATED] _(version 7.44 or below)_ During installation pass `ADDLOCAL="MainApplication,NPM"` to the `msiexec` command, or select "Network Performance Monitoring" when running the Agent installation through the GUI. + [DEPRECATED] _(version 7.44 or below)_ During installation pass `ADDLOCAL="MainApplication,NPM"` to the `msiexec` command, or select "Cloud Network Monitoring" when running the Agent installation through the GUI. 1. Edit `C:\ProgramData\Datadog\system-probe.yaml` to set the enabled flag to `true`: @@ -201,7 +202,7 @@ To enable Network Performance Monitoring for Windows hosts: ```shell net /y stop datadogagent && net start datadogagent ``` -**Note**: Network Performance Monitoring monitors Windows hosts only, and not Windows containers. +**Note**: Cloud Network Monitoring monitors Windows hosts only, and not Windows containers. [1]: /agent/basic_agent_usage/windows/?tab=commandline @@ -209,7 +210,7 @@ To enable Network Performance Monitoring for Windows hosts: {{% /tab %}} {{% tab "Kubernetes" %}} -To enable Network Performance Monitoring with Kubernetes using Helm, add the following to your `values.yaml` file.
+To enable Cloud Network Monitoring with Kubernetes using Helm, add the following to your `values.yaml` file.
**Helm chart v2.4.39+ is required**. For more information, see the [Datadog Helm Chart documentation][1]. ```yaml @@ -218,7 +219,7 @@ To enable Network Performance Monitoring with Kubernetes using Helm, add the fol enabled: true ``` -**Note**: If you receive a permissions error when configuring NPM on your Kubernetes environment: `Error: error enabling protocol classifier: permission denied`, add the following to your `values.yaml` (Reference this [section][5] in the Helm chart): +**Note**: If you receive a permissions error when configuring CNM on your Kubernetes environment: `Error: error enabling protocol classifier: permission denied`, add the following to your `values.yaml` (Reference this [section][5] in the Helm chart): ```yaml agents: @@ -227,7 +228,7 @@ To enable Network Performance Monitoring with Kubernetes using Helm, add the fol enabled: true ``` -If you are not using Helm, you can enable Network Performance Monitoring with Kubernetes from scratch: +If you are not using Helm, you can enable Cloud Network Monitoring with Kubernetes from scratch: 1. Download the [datadog-agent.yaml manifest][2] template. 2. Replace `` with your [Datadog API key][3]. @@ -400,7 +401,7 @@ If you already have the [Agent running with a manifest][4]: [The Datadog Operator][1] is a way to deploy the Datadog Agent on Kubernetes and OpenShift. It reports deployment status, health, and errors in its Custom Resource status, and it limits the risk of misconfiguration thanks to higher-level configuration options. -To enable Network Performance Monitoring in Operator, use the following configuration: +To enable Cloud Network Monitoring in Operator, use the following configuration: ```yaml apiVersion: datadoghq.com/v2alpha1 @@ -417,7 +418,7 @@ spec: {{% /tab %}} {{% tab "Docker" %}} -To enable Network Performance Monitoring in Docker, use the following configuration when starting the container Agent: +To enable Cloud Network Monitoring in Docker, use the following configuration when starting the container Agent: ```shell docker run --cgroupns host \ @@ -485,7 +486,7 @@ To set up on Amazon ECS, see the [Amazon ECS][1] documentation page. {{< site-region region="us,us3,us5,eu" >}} ### Enhanced resolution -Optionally, enable resource collection for cloud integrations to allow Network Performance Monitoring to discover cloud-managed entities. +Optionally, enable resource collection for cloud integrations to allow Cloud Network Monitoring to discover cloud-managed entities. - Install the [Azure integration][101] for visibility into Azure load balancers and application gateways. - Install the [AWS Integration][102] for visibility into AWS Load Balancer. **you must enable ENI and EC2 metric collection** @@ -493,10 +494,23 @@ For additional information around these capabilities, see [Cloud service enhance [101]: /integrations/azure [102]: /integrations/amazon_web_services/#resource-collection -[103]: /network_monitoring/performance/network_analytics/#cloud-service-enhanced-resolution +[103]: /network_monitoring/cloud_network_monitoring/network_analytics/#cloud-service-enhanced-resolution {{< /site-region >}} +### Failed connections + +To enable the Agent to start collecting data about failed connections, add the following setting to your `/etc/datadog-agent/system-probe.yaml` file (or `C:\ProgramData\Datadog\system-probe.yaml` for Windows). + +```yaml +network_config: # use system_probe_config for Agent versions older than 7.24.1 + ## @param enabled - boolean - optional - default: false + ## Set to true to enable Cloud Network Monitoring. + # + enabled: true + enable_tcp_failed_connections: true ##enabled by default +``` + ## Further Reading {{< partial name="whats-next/whats-next.html" >}} diff --git a/content/en/network_monitoring/dns/_index.md b/content/en/network_monitoring/dns/_index.md index 648e02549eafa..efe28f3322b18 100644 --- a/content/en/network_monitoring/dns/_index.md +++ b/content/en/network_monitoring/dns/_index.md @@ -35,7 +35,7 @@ DNS Monitoring provides an overview of DNS server performance to help you identi ## Setup -Before you can begin to use DNS Monitoring, [set up Network Performance Monitoring][1]. Also ensure you are using the latest version of the Agent, or at least Agent v7.23+ for Linux OS, and v7.28+ for Windows Server. Once installed, a **DNS** tab is accessible in the Network Performance Monitoring product. +Before you can begin to use DNS Monitoring, [set up Cloud Network Monitoring][1]. Also ensure you are using the latest version of the Agent, or at least Agent v7.23+ for Linux OS, and v7.28+ for Windows Server. Once installed, a **DNS** tab is accessible in the Cloud Network Monitoring product. Are you looking for Network Device Monitoring instead? See the [NDM setup instructions][2]. @@ -110,7 +110,7 @@ The sidepanel provides contextual telemetry to help you quickly debug DNS server {{< partial name="whats-next/whats-next.html" >}} -[1]: /network_monitoring/performance/ +[1]: /network_monitoring/cloud_network_monitoring/ [2]: /network_monitoring/devices/snmp_metrics/?tab=snmpv2 -[3]: /network_monitoring/performance/network_analytics#table -[4]: /network_monitoring/performance/network_analytics/#recommended-queries +[3]: /network_monitoring/cloud_network_monitoring/network_analytics#table +[4]: /network_monitoring/cloud_network_monitoring/network_analytics/#recommended-queries diff --git a/content/en/network_monitoring/network_path/_index.md b/content/en/network_monitoring/network_path/_index.md index f23ee86cc1fda..99956948a594c 100644 --- a/content/en/network_monitoring/network_path/_index.md +++ b/content/en/network_monitoring/network_path/_index.md @@ -17,16 +17,16 @@ further_reading: text: "Get end-to-end network visibility with Datadog Network Path" --- {{< site-region region="gov" >}} -
Network Path for Datadog Network Performance Monitoring is not supported for your selected Datadog site ({{< region-param key="dd_site_name" >}}).
+
Network Path for Datadog Cloud Network Monitoring is not supported for your selected Datadog site ({{< region-param key="dd_site_name" >}}).
{{< /site-region >}} -
Network Path for Datadog Network Performance Monitoring is in Preview. Reach out to your Datadog representative to sign up.
+
Network Path for Datadog Cloud Network Monitoring is in Preview. Reach out to your Datadog representative to sign up.
## Overview Network Path illustrates the route that network traffic follows from its origin to its destination. This provides network administrators with the capability to precisely identify the source of network problems, whether they're internal or from an Internet Service Provider (ISP), or due to other issues such as misrouting. Each row signifies a path from a source to its destination, as depicted in the `source` and `destination` facet panel. -**Note**: [Network Performance Monitoring][2] must be enabled to use Network Path functionality. +**Note**: [Cloud Network Monitoring][2] must be enabled to use Network Path functionality. {{< img src="network_performance_monitoring/network_path/network_path_default_view_3.png" alt="The Network Path default view, showing the path from source to destination" >}} @@ -46,4 +46,4 @@ The following diagram depicts the typical flow of a network path from a source ( {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/network/path -[2]: /network_monitoring/performance/ +[2]: /network_monitoring/cloud_network_monitoring/ diff --git a/content/en/network_monitoring/network_path/list_view.md b/content/en/network_monitoring/network_path/list_view.md index 969fe740f9a60..ab7bd9cd4cc50 100644 --- a/content/en/network_monitoring/network_path/list_view.md +++ b/content/en/network_monitoring/network_path/list_view.md @@ -12,10 +12,10 @@ further_reading: --- {{< site-region region="gov" >}} -
Network Path for Datadog Network Performance Monitoring is not supported for your selected Datadog site ({{< region-param key="dd_site_name" >}}).
+
Network Path for Datadog Cloud Network Monitoring is not supported for your selected Datadog site ({{< region-param key="dd_site_name" >}}).
{{< /site-region >}} -
Network Path for Datadog Network Performance Monitoring is in Preview. Reach out to your Datadog representative to sign up.
+
Network Path for Datadog Cloud Network Monitoring is in Preview. Reach out to your Datadog representative to sign up.
## Overview diff --git a/content/en/network_monitoring/network_path/path_view.md b/content/en/network_monitoring/network_path/path_view.md index cc9abedd9e349..a2bdf335d596a 100644 --- a/content/en/network_monitoring/network_path/path_view.md +++ b/content/en/network_monitoring/network_path/path_view.md @@ -10,10 +10,10 @@ further_reading: text: "Monitor cloud architecture and app dependencies with Datadog NPM" --- {{< site-region region="gov" >}} -
Network Path for Datadog Network Performance Monitoring is not supported for your selected Datadog site ({{< region-param key="dd_site_name" >}}).
+
Network Path for Datadog Cloud Network Monitoring is not supported for your selected Datadog site ({{< region-param key="dd_site_name" >}}).
{{< /site-region >}} -
Network Path for Datadog Network Performance Monitoring is in Preview. Reach out to your Datadog representative to sign up.
+
Network Path for Datadog Cloud Network Monitoring is in Preview. Reach out to your Datadog representative to sign up.
## Overview diff --git a/content/en/network_monitoring/network_path/setup.md b/content/en/network_monitoring/network_path/setup.md index aad84eff3f930..1eb415c2d29f7 100644 --- a/content/en/network_monitoring/network_path/setup.md +++ b/content/en/network_monitoring/network_path/setup.md @@ -12,10 +12,10 @@ further_reading: --- {{< site-region region="gov" >}} -
Network Path for Datadog Network Performance Monitoring is not supported for your selected Datadog site ({{< region-param key="dd_site_name" >}}).
+
Network Path for Datadog Cloud Network Monitoring is not supported for your selected Datadog site ({{< region-param key="dd_site_name" >}}).
{{< /site-region >}} -
Network Path for Datadog Network Performance Monitoring is in Preview. Reach out to your Datadog representative to sign up, and then use the following instructions to configure the Datadog Agent to gather network path data.
+
Network Path for Datadog Cloud Network Monitoring is in Preview. Reach out to your Datadog representative to sign up, and then use the following instructions to configure the Datadog Agent to gather network path data.
## Overview @@ -24,7 +24,7 @@ Setting up Network Path involves configuring your Linux environment to monitor a ## Prerequisites - Agent version `7.59` or higher is required. -- [NPM][1] must be enabled. +- [CNM][1] must be enabled. **Note**: If your network configuration restricts outbound traffic, follow the setup instructions on the [Agent proxy configuration][2] documentation. @@ -176,7 +176,7 @@ Configure network traffic paths to allow the Agent to automatically discover and {{< partial name="whats-next/whats-next.html" >}} -[1]: /network_monitoring/performance/setup/ +[1]: /network_monitoring/cloud_network_monitoring/setup/ [2]: https://docs.datadoghq.com/agent/configuration/proxy/?tab=linux [3]: https://github.com/DataDog/datadog-agent/blob/main/pkg/config/config_template.yaml#L1645 [4]: https://github.com/DataDog/datadog-agent/blob/main/cmd/agent/dist/conf.d/network_path.d/conf.yaml.example diff --git a/content/en/network_monitoring/performance/guide/_index.md b/content/en/network_monitoring/performance/guide/_index.md deleted file mode 100644 index d9dba6c037216..0000000000000 --- a/content/en/network_monitoring/performance/guide/_index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: Network Performance Monitoring Guides -aliases: - - /network_performance_monitoring/guide/ -private: true -disable_toc: true ---- - -{{< whatsnext desc="General Guides:" >}} - {{< nextlink href="network_monitoring/performance/guide/manage_traffic_costs_with_npm" >}}Manage traffic costs with NPM{{< /nextlink >}} - {{< nextlink href="network_monitoring/performance/guide/detecting_a_network_outage" >}}Detecting a Network Outage{{< /nextlink >}} - {{< nextlink href="network_monitoring/performance/guide/aws_supported_services/" >}}NPM AWS Supported Services{{< /nextlink >}} - {{< nextlink href="network_monitoring/performance/guide/gcp_supported_services/" >}}NPM Google Cloud Supported Services{{< /nextlink >}} - {{< nextlink href="network_monitoring/performance/guide/azure_supported_services/" >}}NPM Azure Supported Services{{< /nextlink >}} -{{< /whatsnext >}} diff --git a/content/en/observability_pipelines/legacy/production_deployment_overview.md b/content/en/observability_pipelines/legacy/production_deployment_overview.md index e79f727b322aa..684c2505f3e22 100644 --- a/content/en/observability_pipelines/legacy/production_deployment_overview.md +++ b/content/en/observability_pipelines/legacy/production_deployment_overview.md @@ -60,7 +60,7 @@ Your pipeline begins with data collection. Your services and systems generate da You should choose the agent that optimizes your engineering team's ability to monitor their systems. Therefore, integrate Observability Pipelines Worker with the best agent for the job and deploy the Observability Pipelines Worker on separate nodes as an aggregator. -For example, Datadog [Network Performance Monitoring][4] integrates the Datadog Agent with vendor-specific systems and produces vendor-specific data. Therefore, the Datadog Agent should collect the data and send it directly to Datadog, since the data is not a supported data type in the Observability Pipelines Worker. +For example, Datadog [Cloud Network Monitoring][4] integrates the Datadog Agent with vendor-specific systems and produces vendor-specific data. Therefore, the Datadog Agent should collect the data and send it directly to Datadog, since the data is not a supported data type in the Observability Pipelines Worker. As another example, the Datadog Agent collects service metrics and enriches them with vendor-specific Datadog tags. In this case, the Datadog Agent should send the metrics directly to Datadog or route them through the Observability Pipelines Worker. The Observability Pipelines Worker should not replace the Datadog Agent because the data being produced is enriched in a vendor-specific way. @@ -143,7 +143,7 @@ Optimize your system of analysis for analysis while reducing costs by doing the [1]: https://wiki.archlinux.org/title/Domain_name_resolution [2]: /observability_pipelines/legacy/reference/sources/ -[4]: /network_monitoring/performance/ +[4]: /network_monitoring/cloud_network_monitoring/ [5]: /observability_pipelines/legacy/architecture/ --- diff --git a/content/en/opentelemetry/agent/_index.md b/content/en/opentelemetry/agent/_index.md index 3c96aa7b55cf5..3c94cb7602dc0 100644 --- a/content/en/opentelemetry/agent/_index.md +++ b/content/en/opentelemetry/agent/_index.md @@ -27,7 +27,7 @@ The Datadog Agent with embedded OpenTelemetry Collector offers: ### Comprehensive observability -- Access {{< translate key="integration_count" >}} Datadog integrations, [Live Container Monitoring][3], [Network Performance Monitoring][7], and [Universal Service Monitoring][5] (with eBPF) and more +- Access {{< translate key="integration_count" >}} Datadog integrations, [Live Container Monitoring][3], [Cloud Network Monitoring][7], and [Universal Service Monitoring][5] (with eBPF) and more - Leverage OpenTelemetry community-contributed integrations to collect telemetry in OpenTelemetry Protocol (OTLP) native format - Control your OTLP data with the Collector's processing and routing capabilities @@ -159,7 +159,7 @@ This guide helps you migrate from an existing OpenTelemetry Collector setup to t [3]: /containers/ [4]: /sensitive_data_scanner/ [5]: /universal_service_monitoring/ -[7]: /network_monitoring/performance/ +[7]: /network_monitoring/cloud_network_monitoring/ [9]: /agent/fleet_automation/ [11]: https://github.com/DataDog/datadog-agent/blob/386130a34dde43035c814f9a9b08bc72eb20e476/comp/otelcol/collector-contrib/impl/manifest.yaml [16]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/filelogreceiver/README.md diff --git a/content/en/opentelemetry/compatibility.md b/content/en/opentelemetry/compatibility.md index 46e97a4f779f2..d04b1ddcc9d44 100644 --- a/content/en/opentelemetry/compatibility.md +++ b/content/en/opentelemetry/compatibility.md @@ -40,7 +40,7 @@ The following table shows Datadog feature compatibility across different setups: | [Real User Monitoring][22] (RUM) | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | [Live Processes][16] | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | [Live Container Monitoring/Kubernetes Explorer][20] | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | -| [Network Performance Monitoring][21] (NPM) | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | +| [Cloud Network Monitoring][21] (CNM) | | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | [Universal Service Monitoring][17] (USM) | | | {{< X >}} | {{< X >}} | {{< X >}} | | [Source code integration][24] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}}
(Datadog SDK only) | {{< X >}} | | [Database Monitoring][14] (DBM) | {{< tooltip text="N/A" tooltip="OTel does not offer DBM functionality" >}}| | {{< X >}} | {{< X >}}
(Datadog SDK only) | {{< X >}} | @@ -58,7 +58,6 @@ The following table shows OpenTelemetry feature compatibility across different s |-----------------------------------------------------|------------------------------------|------------------------------------|-------------------------------------|------------------------------------------------------|--------------| | [Span Links][25] | {{< X >}} | {{< X >}} | {{< X >}} | {{< X >}} | | - ## More details ### Runtime metrics @@ -69,11 +68,11 @@ Setups using the OpenTelemetry SDK follow the [OpenTelemetry Runtime Metrics][1] To enable full RUM functionality, you need to [inject supported headers][2] to correlate RUM and traces. -### Network Performance Monitoring (NPM) +### Cloud Network Monitoring (CNM) Span-level or endpoint-level monitoring is **not** supported. -For more information, see [Network Performance Monitoring Setup][3]. +For more information, see [Cloud Network Monitoring Setup][3]. ### Live Processes @@ -96,7 +95,7 @@ When using Datadog and OpenTelemetry together, Datadog recommends the following [1]: /opentelemetry/integrations/runtime_metrics/ [2]: /real_user_monitoring/platform/connect_rum_and_traces/ -[3]: /network_monitoring/performance/setup/ +[3]: /network_monitoring/cloud_network_monitoring/setup/ [4]: /infrastructure/process/ [5]: /integrations/guide/source-code-integration/?tab=go#configure-telemetry-tagging [6]: /opentelemetry/interoperability/otlp_ingest_in_the_agent/ diff --git a/content/en/security/threats/_index.md b/content/en/security/threats/_index.md index c60fb3a8a07bb..bd81d4d3d1710 100644 --- a/content/en/security/threats/_index.md +++ b/content/en/security/threats/_index.md @@ -13,7 +13,7 @@ Cloud Security Management Threats (CSM Threats) monitors file, network, and proc ## Detect threats to your production workloads in real-time -Monitor file and process activity at the kernel level to detect threats to your infrastructure, such as Amazon EC2 instances, Docker containers, and Kubernetes clusters. Combine CSM Threats with [Network Performance Monitoring][9] and detect suspicious activity at the network level before a workload is compromised. +Monitor file and process activity at the kernel level to detect threats to your infrastructure, such as Amazon EC2 instances, Docker containers, and Kubernetes clusters. Combine CSM Threats with [Cloud Network Monitoring][9] and detect suspicious activity at the network level before a workload is compromised. CSM Threats uses the Datadog Agent to monitor your environment. If you don't already have the Datadog Agent set up, [start with setting up the Agent][2] on a [supported operating system][1]. There are four types of monitoring that the Datadog Agent uses for CSM Threats: diff --git a/content/en/service_catalog/guides/troubleshooting.md b/content/en/service_catalog/guides/troubleshooting.md index 10b33edaa5ee9..b955ff5809fb1 100644 --- a/content/en/service_catalog/guides/troubleshooting.md +++ b/content/en/service_catalog/guides/troubleshooting.md @@ -21,7 +21,7 @@ The count in the Service Catalog Setup Guidance section reflects the number of S ## Additional telemetry is available to a service but it's not listed -Service Catalog relies on the `DD_SERVICE` tag in all telemetry types (infrastructure metrics, logs, network performance monitoring) to gather information about a given service. If you don't see a telemetry type that you expect in the Service Catalog, ensure that you have configured the `DD_SERVICE` tag according to the instructions in [Unified Service Tagging][2]. +Service Catalog relies on the `DD_SERVICE` tag in all telemetry types (infrastructure metrics, logs, Cloud Network Monitoring) to gather information about a given service. If you don't see a telemetry type that you expect in the Service Catalog, ensure that you have configured the `DD_SERVICE` tag according to the instructions in [Unified Service Tagging][2]. ## Can't add metadata for RUM services diff --git a/content/en/synthetics/guide/api_test_timing_variations.md b/content/en/synthetics/guide/api_test_timing_variations.md index a64b5fe72476e..a1e98539b6725 100644 --- a/content/en/synthetics/guide/api_test_timing_variations.md +++ b/content/en/synthetics/guide/api_test_timing_variations.md @@ -114,7 +114,7 @@ Variations of the Time to first byte can occur because of the network and server ### Download time Variations in download time can occur because of changes in the response size. The downloaded body size is available on test results and the `synthetics.http.response.size` metric. -Wherever variations can occur because of network load, you can use [Network Performance Monitoring][6] and [Synthetics ICMP Tests][7] to identify potential bottlenecks. +Wherever variations can occur because of network load, you can use [Cloud Network Monitoring][6] and [Synthetics ICMP Tests][7] to identify potential bottlenecks. In cases where variations can occur because of server load, use the [Datadog Agent][8] and its [integrations][9] to identify potential delays. @@ -128,7 +128,7 @@ In cases where variations can occur because of server load, use the [Datadog Age [3]: /synthetics/private_locations/configuration#dns-configuration [4]: /synthetics/api_tests/dns_tests#define-request [5]: /synthetics/private_locations/?tab=docker#overview -[6]: /network_monitoring/performance/#overview +[6]: /network_monitoring/cloud_network_monitoring/#overview [7]: /synthetics/api_tests/icmp_tests/#overview [8]: /getting_started/agent/#overview [9]: /integrations/ diff --git a/content/en/tracing/trace_collection/proxy_setup/_index.md b/content/en/tracing/trace_collection/proxy_setup/_index.md index 000ea800d3074..4f804fe8f5b33 100644 --- a/content/en/tracing/trace_collection/proxy_setup/_index.md +++ b/content/en/tracing/trace_collection/proxy_setup/_index.md @@ -469,7 +469,7 @@ Datadog monitors every aspect of your Istio environment, so you can: - View individual distributed traces for applications transacting over the mesh with APM (see below). - Assess the health of Envoy and the Istio control plane with [logs][1]. - Break down the performance of your service mesh with request, bandwidth, and resource consumption [metrics][1]. -- Map network communication between containers, pods, and services over the mesh with [Network Performance Monitoring][2]. +- Map network communication between containers, pods, and services over the mesh with [Cloud Network Monitoring][2]. To learn more about monitoring your Istio environment with Datadog, [see the Istio blog][3]. diff --git a/content/en/tracing/trace_explorer/trace_view.md b/content/en/tracing/trace_explorer/trace_view.md index 34d8254bc63de..e4c3cb2d8ba4b 100644 --- a/content/en/tracing/trace_explorer/trace_view.md +++ b/content/en/tracing/trace_explorer/trace_view.md @@ -214,7 +214,7 @@ Click on a service's span to see the processes running on its underlying infrast {{% tab "Network" %}} -Click on a service's span to see network dependencies of the service making the request. Use key network performance metrics such as volume, errors (TCP retransmits), and network latency (TCP round-trip time) to differentiate between application-specific and network-wide issues, especially when no code errors have been generated. For instance, you can use network telemetry to determine if high request latency is due to traffic overloading of the relevant application, or faulty dependencies with a downstream pod, security group, or any other tagged endpoint. Clicking on a process brings you to the [Network Analytics][1] page. To view span-specific processes, enable [Network Performance Monitoring][2]. +Click on a service's span to see network dependencies of the service making the request. Use key network performance metrics such as volume, errors (TCP retransmits), and network latency (TCP round-trip time) to differentiate between application-specific and network-wide issues, especially when no code errors have been generated. For instance, you can use network telemetry to determine if high request latency is due to traffic overloading of the relevant application, or faulty dependencies with a downstream pod, security group, or any other tagged endpoint. Clicking on a process brings you to the [Network Analytics][1] page. To view span-specific processes, enable [Cloud Network Monitoring][2]. **Note**: Related network telemetry is not currently supported for serverless traces. diff --git a/content/en/universal_service_monitoring/setup.md b/content/en/universal_service_monitoring/setup.md index eeb60fcd6ab81..8ac3595abf8b3 100644 --- a/content/en/universal_service_monitoring/setup.md +++ b/content/en/universal_service_monitoring/setup.md @@ -733,7 +733,7 @@ If you use load balancers with your services, enable additional cloud integratio **For services running on IIS:** 1. Install the [Datadog Agent][1] (version 6.41 or 7.41 and later) with the network kernel device driver component enabled. - For Agent version 7.44 or earlier, you must pass `ADDLOCAL="MainApplication,NPM"` to the `msiexec` command during installation, or select **Network Performance Monitoring** when running the Agent installation through the GUI. + For Agent version 7.44 or earlier, you must pass `ADDLOCAL="MainApplication,NPM"` to the `msiexec` command during installation, or select **Cloud Network Monitoring** when running the Agent installation through the GUI. 2. Edit `C:\ProgramData\Datadog\system-probe.yaml` to set the enabled flag to `true`: diff --git a/static/images/network_performance_monitoring/network_analytics/cnm_auto-grouped.png b/static/images/network_performance_monitoring/network_analytics/cnm_auto-grouped.png new file mode 100644 index 0000000000000..2258602db93de Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/cnm_auto-grouped.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/cnm_default_view_2.png b/static/images/network_performance_monitoring/network_analytics/cnm_default_view_2.png new file mode 100644 index 0000000000000..53907f8df1806 Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/cnm_default_view_2.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/cnm_flow_table_region_2.png b/static/images/network_performance_monitoring/network_analytics/cnm_flow_table_region_2.png new file mode 100644 index 0000000000000..53159fb006e7f Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/cnm_flow_table_region_2.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/cnm_network_analytics_2.png b/static/images/network_performance_monitoring/network_analytics/cnm_network_analytics_2.png new file mode 100644 index 0000000000000..adbf5e14090a6 Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/cnm_network_analytics_2.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/cnm_saved_views.png b/static/images/network_performance_monitoring/network_analytics/cnm_saved_views.png new file mode 100644 index 0000000000000..f6eb50e14253f Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/cnm_saved_views.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/cnm_un-grouped.png b/static/images/network_performance_monitoring/network_analytics/cnm_un-grouped.png new file mode 100644 index 0000000000000..3ce00aeed3b8c Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/cnm_un-grouped.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/domain_aggregation_3.png b/static/images/network_performance_monitoring/network_analytics/domain_aggregation_3.png new file mode 100644 index 0000000000000..6fa33b45cd40f Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/domain_aggregation_3.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/network_analytics_with_client_and_server_tag.png b/static/images/network_performance_monitoring/network_analytics/network_analytics_with_client_and_server_tag.png index bda1b1845ea1d..e33600114e19b 100644 Binary files a/static/images/network_performance_monitoring/network_analytics/network_analytics_with_client_and_server_tag.png and b/static/images/network_performance_monitoring/network_analytics/network_analytics_with_client_and_server_tag.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/recommended_queries_2.png b/static/images/network_performance_monitoring/network_analytics/recommended_queries_2.png new file mode 100644 index 0000000000000..cf5dee30719aa Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/recommended_queries_2.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/search_bar_with_groupby_2.png b/static/images/network_performance_monitoring/network_analytics/search_bar_with_groupby_2.png new file mode 100644 index 0000000000000..e3d0f4eb5c4f4 Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/search_bar_with_groupby_2.png differ diff --git a/static/images/network_performance_monitoring/network_analytics/view_network_path_2.png b/static/images/network_performance_monitoring/network_analytics/view_network_path_2.png new file mode 100644 index 0000000000000..a282d50b740ab Binary files /dev/null and b/static/images/network_performance_monitoring/network_analytics/view_network_path_2.png differ diff --git a/static/images/network_performance_monitoring/overview_page/cnm_overview_page_2.png b/static/images/network_performance_monitoring/overview_page/cnm_overview_page_2.png new file mode 100644 index 0000000000000..bb11df602cbdb Binary files /dev/null and b/static/images/network_performance_monitoring/overview_page/cnm_overview_page_2.png differ