PRTG Network Monitor Review: Sensor Costs and Scope

Short answer: PRTG Network Monitor fits teams that want one self-managed console for network-device, service, and traffic checks and can run its core on Windows. Its published subscriptions start at $200 per month, paid annually, for 500 sensors. Budget by actual checks, not device estimates. Paessler's pricing and system requirements establish those conditions. Physical topology and continuous support need separate scrutiny.

PRTG Network Monitor at a glance

Sources: product and trial, pricing, system requirements, SSO manual, and support matrix. "Not established" means the reviewed pages did not confirm the item, not that the feature or report cannot exist.

Who PRTG Network Monitor is for

PRTG Network Monitor can suit an IT team with a supported Windows server and a defined set of switches, routers, firewalls, and service endpoints to observe. Paessler lists SNMP, WMI, and flow collection requirements. A pilot should confirm that the exact devices expose the required data and that the collector can reach them. Vendor claims of broad coverage do not verify your firmware and firewall policy.

It also suits a multi-site team willing to run remote probes near targets. Paessler's probe manual describes local and remote collection. Put one critical branch in the trial and test both the probe-to-device and probe-to-core paths; the network location of each check changes what it can observe.

The strongest buying case is a known sensor inventory. List each interface, service, and environmental reading you need, then assign sensors during the trial. Paessler says a sensor monitors a measured aspect, while its device counts are approximations. This makes the cost decision more reliable than multiplying a device estimate by a generic ratio.

Who should not buy PRTG Network Monitor

Paessler lists a Windows core-server requirement, so a team with a strict Linux-only hosting policy should assess another core platform or change that policy before purchasing. Paessler's Linux option applies to a multi-platform remote probe, not to the core server. A remote probe does not remove the Windows core requirement.

Paessler says built-in auto-discovery does not show physical device connections by itself, so buyers whose main requirement is automatic Layer 2/3 topology should price and validate UVexplorer separately. The product page describes maps and dashboards, but a manually arranged monitoring map is not the same claim as discovered port-to-port topology. Ask for a live demonstration using a representative switch and compare it with your network records.

Paessler's support matrix assigns 8x5 coverage to Essential and Advanced, so teams that require 24x7 vendor support under their standard Network Monitor subscription should get a written support quote before committing. The same matrix lists 24x7 for Enterprise. This is a support-fit issue rather than a claim about product reliability.

Features that matter

Device and protocol coverage

PRTG Network Monitor documents SNMP, WMI, flow, and other sensor methods, with the actual target requirements set by the protocol. Paessler's requirements page says SNMP must be enabled and accessible, while flow exporters must send records to a probe. A sensor catalog is useful for screening, but a trial should verify the exact OID, flow format, or service endpoint required by your device.

Paessler's SNMP manual explains the manager-to-device model. For fast interfaces, verify high-capacity counters and how resets are handled in the resulting graph. Do not infer traffic visibility merely because a device responds to ping.

Discovery and visibility

PRTG auto-discovery searches the selected network and can add devices and recommended sensors. The manual says it is primarily intended for devices in the same network as a probe. Verify remote subnets and credentials rather than assuming a central scan covers every segment.

For topology, draw a clear line between inventory and physical connections. Paessler says PRTG discovery does not independently show the physical links and presents UVexplorer for Layer 2/3 relationships. Require the vendor to show link evidence and refresh behavior if topology is a buying criterion.

Alerts and incident workflow

PRTG supports state, speed, volume, threshold, and change notification triggers in its manual. Paessler also documents schedules that pause monitoring or notifications during planned periods. The trial should show a sensor failure, recipient routing, fallback delivery, and recovery, with an owner for each rule.

Paessler's notifications manual notes that delivery attempts can fail and recommends more than one method for important alerts. Test the actual path to your on-call tool. A configured trigger is not proof that a responder received the message.

Deployment, security, and distributed operation

The core server stores the configuration and monitoring history on the Windows host. Paessler's data-storage manual identifies the configuration file as sensitive because it contains credentials; its backups need the same protection. Plan host hardening, access rights, backups, and upgrade windows as part of deployment, not after the pilot.

Remote probes extend collection to another network segment. Paessler's probe manual documents the model. In a segmented or customer network, validate permitted probe access, returned data, and what happens when its connection to the core breaks. Tenant isolation for MSP use was not established by the reviewed Network Monitor documents; demand a workflow demonstration before treating separate device groups as separate tenants.

Reports, integration, and scale

PRTG offers historical sensor export as CSV or XML through its historic-data API documentation. The manual limits raw-data requests to 40 days per API call and historical-data API calls to five per minute. These are export workflow limits, not necessarily how long data can be stored. Test an actual bulk export before relying on it for a future migration.

Paessler's system requirements recommend additional cores or a presales review above certain sensor and probe sizes. Size the deployment from expected sensor types, polling intervals, and site count. A listed license ceiling is not a measured throughput guarantee for your mix of checks.

Day-to-day admin and scale

The documented rollout starts with a Windows core, local probe, device tree, credentials, and auto-discovery. Paessler's smart-setup manual says its initial scan covers a local private subnet and that other subnets can be added later. Use a small group of representative devices first so discovered sensors do not consume the budget unnoticed.

After deployment, administrators maintain device credentials, sensor definitions, notification contacts, schedules, and probes. Paessler's notification setup guide separates delivery settings, contacts, templates, and triggers. Record which team owns each layer. A healthy sensor with a stale notification contact is still an incident-routing gap.

Paessler's system requirements include recommendations for remote-probe and sensor scale. They are planning guidance, not an independent benchmark. During a trial, watch the core and probe health while using the intended scan intervals and device types. Confirm that backup and software-update procedures preserve configuration and alert behavior.

The fine print

Support

Paessler lists Essential for PRTG 500 and 1000, Advanced for 2500 through 10000, and Enterprise for Enterprise Monitor in its support matrix. The public matrix gives 8x5 coverage and a two-hour first-response SLA for critical cases under Essential and Advanced. Enterprise lists 24x7 and a 45-minute critical first response. A first response is not a resolution guarantee.

The pricing FAQ says Network Monitor subscriptions include updates and ticket-based email support. For a business-critical deployment, ask how severity is classified, which time zone defines 8x5, and what a support upgrade would cost. We did not verify real-world case handling or response performance.

Exit and lock-in

PRTG can export historical sensor measurements as CSV or XML, with documented API limits. The data-storage manual identifies configuration files and the monitoring database on the self-managed core. Back up both before replacing the system, and test import into the destination tool. A CSV export of readings does not automatically recreate sensor definitions, dependencies, maps, or notification rules.

The reviewed public pages did not establish what access to the console remains after a paid subscription ends beyond the trial-to-freeware transition. Nor did they establish a vendor-managed deletion period for this self-managed deployment. Ask for contract and support terms in writing if exit timing matters.

PRTG Network Monitor pricing

Paessler's US pricing page, checked September 26, 2026, lists the following monthly equivalents paid annually. Sensor tiers are caps. Paessler's approximate device counts are illustrative, so size against actual checks.

Annual figures multiply the listed monthly equivalent by 12; they are not a separate vendor quote. Paessler's pricing FAQ says licenses cannot be combined on one server and can be upgraded. Freeware covers up to 100 sensors after the 30-day trial. No per-user seat math applies to this sensor-based license. Taxes, renewal offers, and extension pricing are not established by this table.

Security and reliability record

This is a documented record, not a claim that these are the only historical issues. The Paessler advisory itself is marked as no longer maintained, so use the current release notes and vendor support channel to confirm remediation for the version you intend to deploy.

PRTG Network Monitor versus alternatives

The comparison that matters first is deployment and data scope, not a synthetic score. Use the network monitoring software hub to compare current candidates against the same requirements. For PRTG specifically, verify Windows-core acceptability, actual sensor count, required topology evidence, and support coverage before adding it to a shortlist. Competitor prices and claims are omitted here because they were not independently verified for this review.

Bottom line

PRTG Network Monitor has a clear starting price and a flexible collection model for teams that accept a Windows core and can manage a sensor budget. The trial should count real sensors, demonstrate the needed topology separately, verify notification delivery, and produce a sample historical export. Put the documented support terms and the target core version in the purchase review before selecting it.