By default, PRTG sets sensor scanning intervals to 60 seconds. For non-critical devices (like office printers or backup storage arrays), increase this interval to 5 or 15 minutes. This dramatically reduces the I/O load on the PRTG Core Server database. 3. Leverage Inheritance for Credentials
These sensors allowed PRTG to monitor hyper‑converged infrastructure (HPE 3PAR), cloud services (Azure, AWS), industrial equipment (OPC UA, Beckhoff), and the physical health of data‑center hardware. [25†L12-L22]
Set up SNMP, Windows, and Linux credentials at the highest possible folder group level. Do not configure credentials on individual devices unless they are unique exceptions.
: If your 21.0.x instance is internet-facing, place it behind a reverse proxy (nginx, IIS ARR) with modern WAF rules, or migrate to a supported version.
Performance tuning for SOAP and WMI-based sensors to track host resource allocations and virtual machine metrics without excessive CPU overhead. Protocol Support prtg network monitor 21.0.x
Removed the version number from the footer of the startup screen to prevent information disclosure to attackers. New & Improved Sensors
The Core Server is the central nervous system of PRTG. It houses the built-in proprietary database, the web server, and the central configuration files. In version 21.0.x, the data storage engine received significant performance optimizations, reducing disk I/O bottlenecks when processing high volumes of historical data. Probes (Local and Remote) Probes perform the actual monitoring work.
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.
| Issue | Workaround | |-------|-------------| | | Restart probe service weekly via scheduled task | | Remote probe disconnects over VPN | Increase HeartbeatInterval to 300 seconds in probe configuration | | SNMP v3 sensors fail with authPriv | Downgrade to authNoPriv or update to PRTG 22.3+ | | Web interface slow after 90 days uptime | Restart PRTG Web Server service | | Graphs stop rendering | Clear browser cache or reset \webcache folder | By default, PRTG sets sensor scanning intervals to
PRTG 21.0.x acts as a universal translator for network protocols, eliminating visibility gaps across multi-vendor environments.
Available for iOS and Android, leveraging push notifications to alert admins of critical outages on the go. Expanded Native Sensor Library
PRTG 21.0.x requires mobile app version 3.3+; older apps will fail due to API changes.
For the first time, PRTG introduced a probe capable of running on non-Windows systems, including Linux and Windows Docker containers Enhanced Security: Single Sign-On (SSO) via Azure Active Directory. Do not configure credentials on individual devices unless
This version deprecated and TLS 1.0 . It enforced TLS 1.2 by default for web interfaces and remote probes. Additionally, user passwords migrated to bcrypt hashing , mitigating pass-the-hash risks.
Quickly map your network and automatically populate devices with intelligent sensors.
Released in late 2021, this version was a landmark update that introduced the foundations of modern PRTG, bridging the gap between classic functionality and the next generation of network monitoring. For IT professionals managing on-premises, hybrid, or distributed networks, understanding PRTG 21.0.x is crucial, as its core innovations—particularly a redesigned interface and a modern API—continue to shape the platform today. This article provides a comprehensive guide to PRTG 21.0.x, covering its major innovations, installation, technical requirements, and how it fits into the larger monitoring landscape.
PRTG uses "Sensors" as its licensing metrics and functional building blocks. A sensor monitors one specific aspect of a device. For example: One ping check on a switch is . Monitoring CPU utilization on a server is one sensor .
A chaotic device tree makes managing alerts difficult. PRTG uses a hierarchical structure where configurations, credentials, and notification schedules pass down from parent groups to child devices.