Datadog Network Monitoring Review: Costs and Fit

Short answer: Datadog Network Monitoring can fit teams that want cloud-host traffic, network-device health, and path tests beside existing Datadog telemetry. It is a set of separately priced products. Cloud Network Monitoring (CNM) lists at $5 per network host per month billed annually, and Network Device Monitoring (NDM) at $7 per device per month, with Infrastructure Monitoring also required. Datadog's pricing list and pricing FAQ establish the units and prerequisites.

Datadog Network Monitoring at a glance

Sources: Datadog list pricing, pricing FAQ, CNM setup, NDM setup, organization settings, and Trust Center.

Who Datadog Network Monitoring is for

Datadog is a candidate for a team that already operates Infrastructure Monitoring and wants to compare host-network behavior with other host observations. Datadog's CNM setup uses the Agent and system-probe on monitored hosts. A pilot should include a representative service pair and confirm the flows and tags that appear, rather than assume every network segment is visible from one Agent.

It can also fit network operators with routers, switches, and firewalls accessible from an Agent host. NDM setup explains the collector-to-device model, including SNMP metrics, traps, Syslog, and flow-related paths. Choose a collector location and credentials that are acceptable to the network-security team. Verify the exact device profiles in the supported-device list.

For an organization investigating end-to-end paths, Network Path setup documents Agent-based traceroute checks. The value depends on probe placement and the cost of the scheduled tests. Treat path monitoring as a specified use case, not an automatic consequence of buying CNM.

Who should not buy Datadog Network Monitoring

Datadog's pricing FAQ says every CNM host needs Infrastructure Pro or Enterprise, so a buyer comparing only the $5 CNM rate with another product's all-in rate would understate the list cost. NDM also requires one or more Infrastructure hosts for polling, so a device-only estimate misses its collector prerequisite. Build the quote from all billable components.

CNM setup requires an Agent and system-probe on each monitored host, so an environment that cannot deploy that component should evaluate NDM, exported flow records, or another product for the question it needs answered. Datadog says CNM on Windows monitors hosts rather than Windows containers; a Windows-container-heavy buyer should test coverage before promising that view.

Network Path and NetFlow have separate price units, so a team that needs frequent path tests and long flow retention should request a full usage estimate before buying. Datadog offers different NetFlow retention bands; the lowest published record price is tied to the shortest listed band, not every retention choice.

Features that matter

Host and device collection

CNM observes traffic involving hosts with the configured Datadog Agent and system-probe. The CNM setup guide describes Linux, Windows, and Kubernetes paths. It is useful for a host-centric dependency question, but it is not a passive tap of every device in a network. Check which source and destination tags appear for your own workloads.

NDM is a distinct device-focused path. Datadog's NDM setup puts an Agent on a host that can reach devices, then collects supported device data. That can avoid installing a program on each switch or router, but the polling host and SNMP access still need operations and security ownership. Verify model and firmware support against documented profiles.

Topology and performance evidence

Datadog's device topology map shows relationships derived from monitored device data. During a trial, compare a sample link with switch-neighbor evidence and note whether the source or target is unresolved. A map is strongest when its data source and freshness are visible; it should not replace a verified cabling inventory without comparison.

Network Path can trace selected routes from Agents. Place an Agent near the affected workload, then test a destination and protocol that represents the problem. A path drawn from a central host may differ from a branch or end-user path. Document source, target, protocol and test schedule in the alert.

Alerts and workflow

Datadog supports network monitors for TCP and HTTP checks available in the Agent, alongside monitors on collected metrics. A pilot should create an actionable rule with an owner and verify actual delivery. An alert based on one collector's state should identify that collector so the recipient can distinguish target failure from missing telemetry.

Review the evaluation window and no-data behavior with realistic traffic. A quiet site or delayed flow record can make a rule appear healthy or silent when it has too few samples. Datadog's no-data guide documents evaluation-window and delay settings; test equivalent rules on the actual data source.

Security, roles and data location

The buyer controls Agent installation, SNMP credentials, and collector network reachability. CNM and NDM require different privileges and data paths. Use an approved pilot to see which metadata and flow fields leave the environment and how long they remain available.

Datadog organization settings document SAML settings, and SCIM documentation covers user provisioning. Verify the required plan and role behavior with your identity provider. The Trust Center lists assurance reports, but request the current report that covers the purchased service and region rather than assuming every badge has identical scope.

Scale, retention and integration

The price list makes network scale a multi-unit problem: network hosts, devices, path tests, and aggregated flow records. Datadog's NetFlow docs describe equipment-exported records; the pricing FAQ distinguishes them from CNM host flows. Choose data retention and test volume based on investigations you actually need.

Datadog has integration and API options, but the reviewed material does not establish a complete one-click export of host flows, device history, topology, alert definitions, and dashboards. Test a sample export before treating platform exit as a minor task. Record the raw source, query, tags and retention setting for every business-critical signal.

Day-to-day admin and scale

CNM operations include deploying and updating the Agent and system-probe, maintaining host tags, and checking for missing collection. Datadog's CNM guide is explicit about the component. Assign ownership for the Agent configuration and confirm that it survives normal host and container-platform updates.

NDM operators maintain reachable polling hosts, SNMP access, device profiles, and any Syslog, trap or NetFlow receivers. The NDM setup guide describes those inputs. A collector outage can affect many devices at once, so its own health should be monitored. In a segmented network, record which devices each collector can actually reach.

Review usage as the monitored estate changes. Enabling a new host group, expanding SNMP discovery, adding frequent Network Path tests, or lengthening NetFlow retention can change different bill lines. The public price list names these units, but a contract may have commitments or allotments. Compare the invoice to the pilot inventory and the contract's definitions.

The fine print

Support

Datadog's pricing page advertises chat and email support and additional support plans. The reviewed public material does not establish a particular response-time guarantee for the buyer's proposed subscription. Obtain the service schedule, severity levels, escalation route, and premium-support price in writing.

The internal team remains responsible for host Agents, polling hosts, SNMP credentials and test configuration. A vendor support case cannot repair a collector that your firewall blocks until the owner of that path is involved. Test the alert and support handoff during the pilot.

Exit and lock-in

Datadog's SaaS console can hold metrics, flows, tags, topology, dashboards, and alerts across separate network products. The reviewed public sources do not establish a complete migration export for all of them. Before relying on the platform, test export of a representative device history, CNM view, path test and alert definition through the tools and APIs available in your contract.

Record source-to-destination queries, Agent placement, device credentials ownership, and billing units outside the vendor console. Ask for post-cancellation data access and deletion terms in the contract. A dashboard screenshot is not a replacement for historical observations or a working alert rule.

Datadog Network Monitoring pricing

Datadog's US price list, checked September 26, 2026, shows these list rates for annual billing. The items are separate product units, not a single bundled license.

Datadog's pricing FAQ says CNM requires Infrastructure Pro or Enterprise for each monitored host. At these list rates, one CNM host with Infrastructure Pro represents $20 per month billed annually before other products, taxes, and contract terms. That is simple arithmetic, not a vendor quote. NDM needs at least one Infrastructure polling host; the number of devices that host can support depends on the deployment. There is no per-user seat calculation for these network products.

Price a realistic scenario before purchase: number of CNM hosts, network devices, polling hosts, path tests per month, aggregated flow records, selected retention, and any other Datadog products. Month-to-month and on-demand rates are higher on the current price list. Contract commitments or discounts may alter the invoice.

Security and reliability record

This record avoids inferring that the absence of an identified incident means none occurred. It also does not claim that every listed certification covers every product feature; the report scope needs human review.

Datadog Network Monitoring versus alternatives

Compare Datadog using the same required host, device, path and flow coverage as other candidates. A tool with one lower per-device price may not include host-flow detail; a host-focused product may not poll switches. Use the network monitoring software hub and shortlist to record the specific requirement and full monthly estimate. Competitor prices are omitted because they were not verified here.

Bottom line

Datadog is a strong candidate for teams that already use its Infrastructure platform and can deploy the right collectors for host, device and path questions. Run a pilot that verifies device coverage and alert delivery, then compare observed billing units with a complete written quote. Budget the required Infrastructure hosts alongside the network products.