Prtg Network Monitor 21.0.x

For administrators still using PRTG 18.x or 19.x, upgrading to was a significant leap forward in both security and performance.

WMI checks require significantly more CPU power from both the Core Server and the target machine. Where possible, use WinRM or SNMP on Windows machines instead of traditional WMI sensors.

JThorpe had decided to run a virtual machine on the production database server. Probably trying to mine crypto, or maybe test a script, thinking no one would notice after hours. He was choking the network to death with virtualization overhead. prtg network monitor 21.0.x

Where possible, transition away from SNMPv1 and v2c, which transmit community strings in clear text. SNMPv3 adds encryption and cryptographic authentication.

In previous versions, cluster nodes sometimes suffered from synchronization lags, leading to false "down" alerts during failover testing. Version 21.0.x hardened the database replication protocol, ensuring that configuration changes (like adding a sensor or modifying a threshold) replicated within seconds across all nodes in a cluster. For administrators still using PRTG 18

Increase the interval to 5, 10, or 15 minutes.

| Sensor Count | CPU Usage (avg) | RAM Usage | Probe Response Time | |--------------|----------------|-----------|---------------------| | 1,000 | 8% | 6 GB | < 0.5 sec | | 5,000 | 22% | 16 GB | 1.2 sec | | 10,000 | 45% | 28 GB | 2.5 sec | | 20,000 | 85% | 52 GB | 5.0 sec (near limit)| JThorpe had decided to run a virtual machine

The pattern was unmistakable. Every 12 minutes, like clockwork, the Disk I/O spike hit the roof, stayed there for 45 seconds, and then plummeted. During that spike, the CPU was maxing out at 100%, causing the network stack to lag, which triggered the packet loss warnings.

For a new installation on the 21.0.x series, you would simply run the installer on a supported operating system and follow the steps: selecting the language, accepting the license agreement, and completing the installation before the server restarted. The process is streamlined with a convenient setup wizard.

It wasn't a hardware failure. It was a runaway process.

The discovery engine received speed improvements, and sensor requirements were added directly to the "Add Sensor" dialogs for easier troubleshooting. for these features or a guide on from an older version? Release Notes for PRTG 21 - Paessler