Versions in the 21.x range addressed critical vulnerabilities to harden the monitoring core:
In , Paessler announced the alpha release of a brand‑new user interface and a completely new RESTful API (API v2) . These features were not fully available in the 21.0.x series but began appearing in 21.1.x and later versions as experimental options.
Sensor Types and Coverage
Better management of certificates for secure communication between the core server and remote probes.
Standard SMTP messages containing sensor status details. prtg network monitor 21.0.x
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]
PRTG competes in a crowded market of network monitoring tools. How does it generally stack up against some common alternatives?
With cyber threats evolving, Paessler introduced stricter security defaults in 21.0.x. This version saw improvements in how the core server handles SSL/TLS connections and more granular user access controls. It ensures that your monitoring data—which is essentially a map of your vulnerabilities—stays out of the wrong hands. 2. The New Desktop App
Result: Error. Command timeout.
Yellow again. Then Red. Then Green.
The "21" in 21.0.x stands for 2021, the year this major versioning began. The primary goal of this cycle was to transition PRTG from a Windows-centric tool into a more flexible, hybrid-ready solution. It moved away from legacy components and introduced a more streamlined, responsive interface. 2. Key Features and Enhancements A. The New Desktop App
settings allowed users to test upcoming sensors, such as the AWS EBS v2 FortiGate System Statistics Modern Web Interface & API:
Several existing sensors and core capabilities were enhanced in the 2021 releases: Versions in the 21
对于跨地域或多站点的企业，PRTG 21.0.x提供了成熟的远程探针架构，使IT团队能够从单一核心服务器管理多个监控节点。远程探针在本地记录监控数据后发送到中央设备进行分析和可视化。此外，PRTG可配置为故障转移集群，一个或多个核心服务器协同工作共享同一配置，实现无间隙监控和不同视角的结果对比。
PRTG relies on inheritance for settings, credentials, and notifications. Structure your root system clearly: Location A (Branch Office) Servers (Inherits Windows Credentials) Network Switches (Inherits SNMP Credentials) Location B (Cloud Infrastructure) Azure Resources (Inherits API Keys)
(Description: Core server with two failover nodes, three remote probes – one on-prem, one in AWS, one in Azure, all communicating via TLS 1.2.)
