PRTG Manual: PRTG Status—System Status

Software Version and Server Information

PRTG Version

Shows the exact version of the build your PRTG installation is currently running on.

Auto-Update Status

Shows the latest auto-update message available from Software Auto-Update. For example, the message will indicate any PRTG updates ready to be installed.

Operating System

Shows the exact Windows version build and service packs, the number and kind of CPUs, and the computer name, of the system the PRTG core server is installed on. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Note: When running PRTG on virtual systems, not all of the mentioned values may be available.

Server Time

Shows the date and time of the system the PRTG core server is installed on. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Server CPU Load

Shows the current CPU load of the system the PRTG core server is installed on. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Username

Shows the username of the PRTG user you're currently logged in as.

Browser

Shows the name and user agent string of the browser you're currently viewing this page with.

Licensing

Licensee

Shows the Name of the license you're using for this installation of PRTG. Licensee (name) and license key together build your license information.

Key

Shows the beginning and the end of the license key you're using for this installation of PRTG. Licensee (name) and license key together build your license information.

Edition

Shows the PRTG edition you're using for this installation of PRTG. This determines how many sensors you can use in your monitoring (see below).

Activation Status

Shows the activation status of this installation of PRTG. Usually, activation is done automatically on first start-up. Only if PRTG cannot connect directly to the internet, a manual activation is necessary. For details, please see Activate the Product.

Software Maintenance

Shows the days remaining for your active maintenance contract. You can buy maintenance for each PRTG license. With an active maintenance contract you may download any available updates and use our premium email support, without additional costs.

Number of Sensors

Shows the number of sensors you can use in your monitoring, with your current edition of PRTG (see above). If you reach the limit, each new sensor that you create will be set to a Pause status automatically. In order to upgrade your license right now, click on the Need more sensors? Click here to upgrade! button to visit our web shop. Editions that allow an unlimited number of sensors do  not restrict the number of possible sensors by license, so you can create sensors until the performance limit is reached. This means you can use about 20,000 sensors per core server (depending on your system's performance, sensor types, and scanning intervals); for details, see system requirements linked in the More section below.

System Startup Log

Shows the log information created during the last startup of the PRTG core server. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Cluster Status

This box is only visible if you're running a PRTG cluster. This section lists all cluster nodes configured in your monitoring.

Node [Number]

Shows the name of the cluster node as well as the node type (primary/secondary node) and status (current master/failover node). Additionally, all connections from this node to the other cluster nodes are shown, as illustrated on the PRTG Status—Cluster Status page.

Local Status

This box is only visible if you're running a PRTG cluster. This section lists information about the cluster node you're currently logged in to.

Server State Cluster Messages

Shows internal summary information about the current node and the communication between the nodes. You might be asked about this by Paessler's technical support staff.

Cluster Connections

This box is only visible if you're running a PRTG cluster. This section lists information about the connections between the different cluster nodes.

State of Local Node

Shows Treeversion and size of the Server Volume, both internal system information.

State of Cluster Members

For each cluster node, the name and IP address is shown, as well as a state CRC code, the time stamp of the last "keep alive" signal sent, the current size of the buffer, and the remote IP.

Message State of Cluster Members

For each cluster node, the name, IP address, and unique identifier is shown, as well as the connection state, and statistic information about the cluster message system which is used for the communication between the different nodes.

Administration Tools

Different action buttons are shown for debugging purposes. Use them if Paessler's technical support staff advises you to do so.

Create Database Snapshot

Click this button to create a snap shot of your PRTG configuration. This action can take up to 100 seconds. Once finished, you will find a ZIP file containing a *.dat file in the Configuration Auto-Backups sub folder of your PRTG data directory. If you're running a PRTG cluster, this action is executed on the cluster node you're currently logged in to. The ZIP file follows the name pattern PRTG Configuration (Snapshot YYYY-MM-DD HH-MM-SS).zip.

Write Core Status File

Click this button to create status files of your PRTG core server. You will find the two text files in the Logs (System) sub folder of your PRTG data directory. If you're running a PRTG cluster, this action is executed on the cluster node you're currently logged in to. The files are named Core Status.txt and Core Memory.txt. They are overwritten each time you click this button.

Write Probe Status Files

Click this button to create status files of your PRTG probes. Status files will be written for the local probe running on the PRTG core server (if you're running a PRTG cluster, on the cluster node you're currently logged in to) as well as for all remote probes configured (if any). On the respective systems, you will find four text files in the Logs (System) sub folder of the PRTG data directories. The files follow the name pattern Probe Memory XX.txt, ProbeState XX.txt, ProbeState AXX.txt, and ProbeState BXX.txt. They are overwritten each time you click this button.

Restart All Probes

Click this button to restart all PRTG probes. This will restart the local probe Windows service. If there are any remote probes configured, the probe Windows services on the respective remote systems will be restarted as well. In order to start single probes only, please see Probes section below. Note: If you're running a PRTG cluster, this action is executed on the cluster node you're currently logged in to. In this case, remote probes are only restarted if you're logged in to the primary master node. The cluster probe Windows service of failover nodes is not restarted if this action is executed on the master node. If you want to restart the cluster probe Windows service of a failover node, please log in to this failover node's web interface and click on the same button there.

Auto-Discovery Tasks

Currently Running

Shows the number of auto-discovery tasks that are currently running. A high number of auto-discovery tasks can negatively influence system performance.

Background Tasks

Historic Data

Shows if PRTG is re-calculating the historic data cache in the background. If so, you will see the tasks to do until done. Usually, this calculation is done after every core server restart.

Toplist Buffer

When using xFlow or Packet Sniffer sensors, PRTG stores Toplist data. The data stream received is buffered and written to the data directory of the core system. Depending on the number and size of the data stream as well as the hard disk and system performance of the core system, the buffer size can rise. When reaching a buffer size of 500, Toplist data is dropped which can lead to incorrect Toplist values for the sensors.

Toplist Upgrade

If you recently updated from an older PRTG version (7 or 8), Toplist data needs to run through a one-time conversion process. While conversion is running you may experience a considerably slow monitoring system. Usually, you will see n/a here.

Database Objects

Shows statistic information about your monitoring configuration. This information might be necessary when contacting Paessler's technical support staff.

Probes

Shows the total number of probes configured.

Groups

Shows the total number of groups in your configuration.

Devices

Shows the total number of devices in your configuration.

Sensors

Shows the total number of sensors in your configuration.

User Groups

Shows the total number of user groups in your configuration.

Users

Shows the total number of users configured.

Notifications

Shows the total number of notifications configured.

Schedules

Shows the total number of schedules configured.

Requests/Second

Shows a value calculated from the total number of sensors and the average scanning interval configured. This number indicates how many monitoring requests per second are sent from the probe(s) to the devices in your network. There are no general guidelines what is a "good" value here. This depends on the sensor types used as well as on your system's performance.

Sensors

Shows a list with numbers and types of sensors used in your configuration. Note: In the list, internal short names are used for sensor types instead of the official designations.

Probes

This section lists all probes configured in your monitoring. If there are no remote probes configured, only the "Local probe" appears in the list, which runs mandatorily on the PRTG core server. Note: If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Remote probes (if any) will only be shown when you're logged in to the primary master node. When logged in to a failover node, the cluster probe running on this node will appear as "Local probe".

Probe [#Number] "[Name]"

Information about the connection status is shown. If the probe is currently connected, the field shows the source IP address and port number used by the probe. For the "Local probe", the IP will always be IP 127.0.0.1. You will also see information about the date when the last data packet was received from the probe. If you want to restart a single probe, please click on the Restart Probe button.

System Settings

Web Server URL

Shows the URL to access the PRTG web interface. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Web Server IPs

Shows all IP addresses the PRTG web server is running at. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Web Server Ports

Shows the port the PRTG web server is running at. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Web Server Port Usage

Shows the number of ports used by the PRTG web server.

Incoming Probe Connection Binding

Shows a combination of the two values below.

Incoming Probe Connection IPs

Shows a list of all IP addresses on which your current PRTG installation listens to incoming remote probe connections. This is the same information as shown in the System Administration—Probes settings. 0.0.0.0 means that the core server listens on all local network adapter IPs. In order to change this setting, please open the PRTG Server Administrator on the system of the PRTG core server.

Incoming Probe Connection Port

Shows the port number on which your current PRTG installation listens to incoming remote probe connections. This is the same information as shown in the System Administration—Probes settings. Default port is 23560. In order to change this setting, please open the PRTG Server Administrator on the system of the PRTG core server.

Probe Allow IPs

Shows all source IP addresses that will be accepted by the core server for incoming remote probe connections. This is the same information as shown in the System Administration—Probes settings and can be changed there. any means that all remote probe connections are accepted, regardless of the IP address of the remote probe system.

Probe Deny IPs

Shows all source IP addresses that will be denied by the core server for incoming remote probe connections. This is the same information as shown in the System Administration—Probes settings and can be changed there. Denied IPs are superior to allowed IPs. If this field is empty, there are no denied IPs. Note: PRTG automatically adds the IP address of a remote probe system to this list when you delete a remote probe from your device tree.

DataPath

Shows the path where PRTG stores its configuration, monitoring database, etc. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. In order to change this setting, please open the PRTG Server Administrator on the system of the PRTG core server (or of the respective cluster node, if applicable).

Web Server Activity

Shows statistic information about the web server since last startup. All values are reset when the core server is restarted. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Time Since Startup

Shows the time that has passed since the PRTG web server was started.

Page Views

Shows the total number of page views on this core server.

Geo Maps

Shows the total number of geo maps shown on this core server.

HTTP Requests

Shows the total number of HTTP requests to this core server.

HTTP Requests > 500/1000/5000 ms

Shows for how many (percent) of the HTTP requests above the page delivery took longer than 500, 1,000, or 5,000 milliseconds.

Slow Request Ratio

Shows a calculated number of the HTTP request values above. The lower this number, the faster is your installation's web interface.

Synchronization

The core server holds the configuration of the entire monitoring and deploys it to the probes. This section shows statistic information about the synchronization of the core server with the local probe and all connected remote probes (if any), since last startup of the core server. All values shown here are reset when the core server is restarted. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to. Note: Only when logged in to the primary master node you will see synchronization data for remote probe connections.

Last Synchronization with a Probe

Shows the time stamp of the last probe synchronization, and if there is still something to do.

Probe/Core Message Count

Shows the total number of messages sent between core and probe(s), as well as a calculated message speed value.

Sync Cycle Speed

Shows the time necessary for a full synchronization, as well as an evaluation comment of this time (usually, this will be "OK").

Configuration Requests Sent

Shows the total number of configuration requests and the requests that still have to be sent.

Configuration Requests Deleted

Internal debug information. Usually, this value will be 0.

Configuration Requests With Response

Internal debug information. Usually, this value will be 0.

System Warnings

If there are any warnings they will be shown here. Usually "None" will be shown here.

Core System Memory

Shows machine-oriented information regarding the memory usage of the core server system. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Thread Information

Shows machine-oriented information regarding the threads running on the core server system. If you're running a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

Setup—Topics

• Account Settings—My Account
• Account Settings—Notifications
• Account Settings—Schedules
• System Administration—System and Website
• System Administration—Notification Delivery
• System Administration—Probes
• System Administration—Cluster
• System Administration—User Accounts
• System Administration—User Groups
• PRTG Status—System Status
• PRTG Status—Cluster Status
• PRTG Status—Activation Status
• Software Auto Update
• Downloads
   

Others

There are some settings that have to be made in the System Administration Tools, available as native Windows applications. For more details, please see sections:

• PRTG Server Administrator
• PRTG Probe Administrator