PRTG Manual: Architecture and User Interfaces
In this section, you can find an overview of the components of PRTG and how it works.
You can classify the components of PRTG into three main categories: system parts, user interfaces, and basic system administration tools.
PRTG core server
We assume that all systems on which the PRTG core server with the local probe or any remote probes run are secure. It is every system administrator's responsibility to make sure that only authorized persons can access these systems. For this reason, we highly recommend that you use dedicated machines for your PRTG system parts.
PRTG web interface
PRTG apps for mobile network monitoring
System Administration Tools
PRTG Administration Tool on PRTG Core Server Systems
PRTG Administration Tool on Remote Probe Systems
The PRTG core server is the heart of PRTG. It performs the following tasks:
- Configuration management for target devices (for example, servers, workstations, printers, switches, routers, or virtual machines (VM))
- Management and configuration of connected probes
- Cluster management
- Database for monitoring results
- Notification management including a mail server for email delivery
- Report generation and scheduling
- User account management
- Data purging (for example, deleting data that is older than 365 days)
- Web server and application programming interface (API) server
In a cluster, the master node is responsible for all of these tasks.
The built-in and secure web server, for which you require no additional Microsoft Internet Information Services (IIS) or Apache, supports HTTP as well as HTTPS (secured with Secure Sockets Layer (SSL)/Transport Layer Security (TLS)). It serves the PRTG web interface when you access it via a browser and also answers PRTG API calls.
The PRTG core server is configured as a Windows service that permanently runs. A logged-in user is not required.
On the probe, PRTG performs the actual monitoring via the sensors that you created on a device (for example, a computer, a router, a server, a firewall, and more). The probe receives its configuration from the PRTG core server, runs the monitoring processes, and delivers monitoring results back to the PRTG core server.
For PRTG Network Monitor, there is always a local probe that runs on the PRTG core server system.
For PRTG Hosted Monitor instances, there is always a hosted probe that runs on the PRTG core server system that Paessler hosts for you.
The actual monitoring is performed by probe processes that run on one or more systems.
The probes are configured as a Windows service that permanently runs. A logged-in user is not required.
During the installation, PRTG automatically creates the local probe. In a single-probe installation, which is the default setup, the local probe performs all monitoring.
For PRTG Network Monitor, the PRTG core server with the local probe inside the corporate LAN can monitor services and servers in the entire LAN.
When you create a PRTG Hosted Monitor instance, the system automatically creates the hosted probe. The hosted probe shows monitoring values of the hosted instance and can monitor devices, servers, and services that are publicly available in the internet like websites.
You can create additional remote probes to monitor multiple locations, to monitor a LAN with PRTG Hosted Monitor, or for several other scenarios. Remote probes use SSL/TLS-secured connections to the PRTG core server. With remote probes, you can securely monitor services and systems inside remote networks that are not publicly available or that are secured by firewalls.
For more information, see section Add Remote Probe.
For more information, see the video tutorial: Distributed monitoring with PRTG.
In a cluster, a cluster probe runs on all cluster nodes. All devices that you create on the cluster probe are monitored by all cluster nodes, so data from different perspectives is available and monitoring continues even if one of the cluster nodes fails.
Mini probes let you create small probes on any device, not only on Windows systems.
For more information, see section Mini Probe API.
PRTG automatically monitors the system health of the PRTG core server and of each probe to discover overload situations that can distort monitoring results. To monitor the status of the probe system, PRTG automatically creates the Core Health and Probe Health sensor, the System Health sensor, the Cluster Health sensor, some disk free and bandwidth sensors for all installed network cards, as well as a Common SaaS sensor that checks the availability of widely used software as a service (SaaS) providers.
We recommend that you keep these sensors. However, you can remove all of them except for the health sensors.
The health sensors measure various internal system parameters of the probe system hardware and the probe's internal processes and compute the results. Investigate frequent values below 100%.
Getting started with PRTG
How to connect PRTG through a firewall in 4 steps
Distributed monitoring with PRTG
What is a sensor?