<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: PRTG Status—System Status

PRTG Version

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

Auto-Update Status

Shows the latest auto-update message available from the auto-update. For example, the message indicates any updates ready to be installed.

This information is not displayed in PRTG hosted by Paessler.

Operating System

Shows the exact Windows version build and service packs, the number and kind of CPUs, and the computer name of the PRTG core server system.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

When running PRTG on virtual systems, some of the mentioned values might not be available.

This information is not displayed in PRTG hosted by Paessler.

Server Time

Shows the date and time of the PRTG core server system.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

Server CPU Load

Shows the CPU load of the PRTG core server system.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

Username

Shows the username of the user account that you are logged in with.

Active User Sessions

Shows the usernames of all user accounts that are logged in.

When a user account logs out, it takes up to 1 minute until the username disappears.

Browser

Shows the name and user agent string of the browser you are viewing this page with.

License Status

Shows the activation status of this installation of PRTG. Usually, PRTG completes the activation automatically during installation or when you change your license information. Only if PRTG cannot connect directly to the internet, is a manual activation necessary.

For more information, see section Activate the Product.

License Name

Shows the owner of the license that you use for this installation of PRTG, for example ExampleOrganization. License Name, license key, and system ID together build your license information.

You can find the label License Owner in some documents from the Paessler shop. License Owner is the same as License Name, for which you might be asked while installing PRTG or when you change your license key.

License Key

Shows the license key that you use for this installation of PRTG. License Name, license key, and system ID together build your license information.

System ID

The system ID is a fixed value that is automatically assigned to your PRTG installation.

Licensed Edition

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

Last Update

Shows the date of the last update for this PRTG installation. We recommend that you use the auto-update.

Maintenance until

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

Number of Sensors

Shows the number of sensors you can use in your monitoring with your edition of PRTG. If you reach the limit, PRTG automatically sets each new sensor that you add to a Paused status. To upgrade your license right now, click 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 that you can use about 10,000 sensors per PRTG core server (depending on your system's performance, sensors, and scanning intervals).

For more information, see section Detailed System Requirements.

Shows the log information created during the last startup of the PRTG core server.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

If there are any warnings, PRTG shows them here. Usually, you see None.

This box is only visible if you run PRTG in a cluster. This section lists all of your cluster nodes.

Node [Number]

Shows the name and type of the cluster node (primary node or secondary node) and its status (current master node or failover node). Additionally, all connections from this cluster node to the other cluster nodes are shown.

For more information, see section PRTG Status—Cluster Status.

This box is only visible if you run PRTG in a cluster. This section lists information about the cluster node that you are logged in to.

Server State

Shows the name of the cluster node and its status (current master node or failover node).

Cluster Messages

Shows internal summary information about the cluster node and the communication between the cluster nodes. You might be asked about this by the Paessler support team.

This box is only visible if you run PRTG in a cluster. This section lists information about the connections between the cluster nodes.

State of Local Node

Shows the treeversion and size of the server volume, both types of internal system information.

State of Cluster Members

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

Message State of Cluster Members

For each cluster node, the name and unique identifier is shown, as well as the connection state, and statistics about the cluster message system that is used for the communication between the cluster nodes.

Shows machine-oriented information regarding the memory usage of the PRTG core server system.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

For more information, see the Knowledge Base: What do the PRTG core memory parameters mean?

Shows machine-oriented information regarding the threads running on the PRTG core server system.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

The "Activity History" shows how busy PRTG was for you in the past. The graphs indicate the number of activities in the last 365 days. Below the graphs, you see statistics about the past day.

Sensor Scans

Shows how often all sensors refreshed their data in the past.

Sensor Status Changes

Shows how often the sensor states changed in the past.

Notifications Sent

Shows how many notifications PRTG sent out in the past.

Reports Generated

Shows how many reports PRTG created in the past.

Page Views

Shows how often pages in the PRTG web interface were opened in the past.

Sensors

Shows how many sensors existed in the past.

Devices

Shows how many devices existed in the past.

Reports

Shows how many reports existed in the past.

Maps

Shows how many maps existed in the past.

Currently Running

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

Historic Data

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

Toplist Buffer

When using xFlow (NetFlow, jFlow, sFlow, IPFIX) or Packet Sniffer sensors, PRTG stores Toplist data. The data stream received is buffered and written to the data directory of the PRTG core server system. Depending on the number and size of the data stream as well as the hard disk and system performance of the PRTG core server 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.

Similar Sensors Detection

Shows the status and the selected setting for the analysis depth of the similar sensors analysis.

Recommended Sensors Detection

Shows the status of the detection engine and the tasks of the recommended sensors detection.

Shows statistic information about your monitoring configuration. This information might be necessary when contacting the Paessler support team.

Probes

Shows the total number of probes in your installation.

Groups

Shows the total number of groups in your installation.

Devices

Shows the total number of devices in your installation.

Sensors

Shows the total number of sensors in your installation.

Channels

Shows the total number of channels in your installation.

User Groups

Shows the total number of user groups in your installation.

Users

Shows the total number of users in your installation.

Notifications

Shows the total number of notifications in your installation.

Schedules

Shows the total number of schedules in your installation.

Maps

Shows the total number of created maps in your installation.

Libraries

Shows the total number of created libraries in your installation.

Reports

Shows the total number of reports in your installation.

Bitfield/Boolean/Integer/Range Lookups

Shows the total number of used lookups by lookup type.

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 probes to the devices in your network.

There are no general guidelines on what a "good" value is here. This depends on the sensors used as well as on your system's performance.

Shows all sensors used in your configuration in order of performance impact (from very low to very high). If the CPU load of the probe system is very high, you can see which sensors might be causing this issue. Consider the recommended number of sensors in the respective sections for sensors with high and very high performance impact.

In the list, internal short names are used for sensors instead of the official designations.

You can also see the performance impact of a sensor on the sensor's Overview tab or in the Add Sensor dialog.

Shows all sensors used in your configuration in order of scanning interval. Choose reasonable scanning intervals for sensors that can affect the system performance. See the respective sections for sensors for more information.

In the list, internal short names are used for sensors instead of the official designations.

This section lists all probes configured in your monitoring setup. If there are no remote probes configured, only the local probe or the hosted probe appears in the list, which always runs on the PRTG core server.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

Remote probes (if any) are only shown when you are logged in to the primary master node. When logged in to a failover node, the cluster probe on this cluster node appears as local probe.

Probe [#Number] "[Name]"

Information about the connection status is shown. If the probe is connected, the field shows the source IP address and port number used by the probe. For the local probe, the IP is always 127.0.0.1. You also see information about the date when the last data packet was received from the probe.

If you want to restart a single probe, open the Administrative Tools Settings.

Web Server URL

Shows the URL to access the PRTG web interface.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

Web Server IPs

Shows all IP addresses that the PRTG web server runs on.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

Web Server Ports

Shows the port that the PRTG web server runs on.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

Web Server Port Usage

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

SSL/TLS Versions for Web Server

Shows the Secure Sockets Layer (SSL)/Transport Layer Security (TLS) versions used for connections from and to the PRTG web server. This is only shown if you are using a TLS-secured connection.

Web Server Ciphers

Shows the ciphers used by the PRTG web server. This is only shown if you are using a TLS-secured connection.

SSL/TLS Versions for Probe Port

Shows the SSL/TLS versions used for the probe port.

Probe Ciphers

Shows the ciphers used for the remote probe connection.

DH Parameters Size

Shows the length of the Diffie-Hellman (DH) parameters. This is only shown if you are using a TLS-secured connection.

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 PRTG listens for incoming remote probe connections. This is the same information as shown in the System Administration—Core & Probes settings. 0.0.0.0 means that the PRTG core server listens on all local network adapter IPs.

Incoming Probe Connection Port

Shows the port number on which the PRTG listens for incoming remote probe connections. The default port is 23560.

Probe Allow IPs

Shows all source IP addresses that PRTG accepts for incoming remote probe connections. This is the same information as shown in the System Administration—Core & Probes settings and you can change it 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 PRTG denies for incoming remote probe connections. This is the same information as shown in the System Administration—Core & Probes settings and you can changed it there. Denied IPs are superior to allowed IPs. If this field is empty, there are no denied IPs.

PRTG automatically adds the IP address of a remote probe system to this list when you delete a remote probe from your device tree.

Data Path

Shows the path where PRTG stores its configuration, monitoring database, etc. To change this setting, open the PRTG Administration Tool on the PRTG core server system (or of the respective cluster node, if applicable).

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

Shows statistics about the web server since the last startup. All values are reset when the PRTG core server is restarted.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are 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 PRTG core server.

Geo Maps

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

HTTP Requests

Shows the total number of HTTP requests to this PRTG 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 is, the faster the PRTG web interface is.

The PRTG core server holds the configuration of the entire monitoring setup and deploys it to the probes. This section shows statistics about the synchronization of the PRTG core server with the local probe and all connected remote probes (if any), since the last startup of the PRTG core server. All values shown here are reset when the PRTG core server is restarted.

If you run PRTG in a cluster, this shows information for the system of the cluster node you are logged in to.

You must log in to the primary master node to 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 the PRTG core server and probes, as well as a calculated message speed value.

Raw Buffer Count

Shows the number of raw buffers and a corresponding status indicator.

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 is 0.

Configuration Requests With Response

Internal debug information. Usually, this value is 0.

• Account Settings—My Account
• Account Settings—Notification Templates
• Account Settings—Notification Contacts
• Account Settings—Schedules
• System Administration—User Interface
• System Administration—Monitoring
• System Administration—Notification Delivery
• System Administration—Core & Probes
• System Administration—User Accounts
• System Administration—User Groups
• System Administration—Administrative Tools
• System Administration—Cluster
• PRTG Status—System Status
• PRTG Status—Auto-Update
• PRTG Status—Cluster Status
• PRTG Status—Licensing Status and Settings
• Optional Downloads
• Desktop Notifications
• Support—Help and Support Center
• Support—Contact Support

There are some settings that you must make in the PRTG Administration Tool. For more details, see the sections:

• PRTG Administration Tool on Core Server System
• PRTG Administration Tool on Remote Probe System