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

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.

This information is not displayed in PRTG on demand.

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 run a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

When running PRTG on virtual systems, not all of the mentioned values may be available.

This information is not displayed in PRTG on demand.

Server Time

Shows the date and time of the system the PRTG core server is installed on. If you run 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 run 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.

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, a manual activation is necessary. For details, please see Activate the Product.

License Name

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

You will find the label License Owner in some documents from the Paessler shop. License Owner is the same as License Name for which you will 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 PRTG Auto-Update to get the most out of PRTG.

Maintenance until

Shows the expiry date and 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.

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, PRTG will set each new sensor that you add to a Pause status automatically. 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 core server (depending on your system's performance, sensor types, and scanning intervals). For details, see section Detailed System Requirements.

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

If there are any warnings, PRTG will show them here. Usually, you will see "None" system warnings.

This box is only visible if you run 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.

This box is only visible if you run 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.

This box is only visible if you run 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.

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

See the Knowledge Base for more information: What do the PRTG core system memory parameters mean?

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

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

Sensor Scans

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

Sensor State 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 this PRTG installation in the past.

Devices

Shows how many devices existed in this PRTG installation in the past.

Reports

Shows how many Reports existed in this PRTG installation in the past.

Maps

Shows how many Maps existed in this PRTG installation in the past.

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.

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.

Similar Sensors Analysis

Shows the current status and the selected setting for the analysis depth of the Similar Sensors analysis.

Recommended Sensors Detection

Shows the current status of the detection engine and the current tasks of the Recommended Sensors Detection.

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.

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.

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.

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

Shows all sensor types used in your configuration ordered by performance impact (from very low to very high). If your PRTG system is very slow, you can see which sensors might cause this issue. Please consider the recommended number of sensors in the respective manual sections for sensors with high and very high performance impact.

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

Shows all sensor types used in your configuration ordered by scanning interval. Please choose reasonable scanning intervals for sensors which can affect the system performance. See the respective manual sections for sensors for more information.

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

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 always runs on the PRTG core server.

If you run 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 are 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 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 open the Administrative Tools Settings.

Web Server URL

Shows the URL to access the PRTG web interface. If you run 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 run 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 run 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—Core & Probes settings. 0.0.0.0 means that the core server listens on all local network adapter IPs.

Incoming Probe Connection Port

Shows the port number on which your current PRTG installation listens to incoming remote probe connections. The default port is 23560.

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—Core & 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—Core & Probes settings and can be changed 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.

DataPath

Shows the path where PRTG stores its configuration, monitoring database, etc. If you run 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 Administration Tool on the system of the PRTG core server (or of the respective cluster node, if applicable).

Shows statistic information about the web server since last startup. All values are reset when the core server is restarted. If you run 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.

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 run a PRTG cluster, this will show information for the system of the cluster node you're currently logged in to.

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.

Raw Buffer Count

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

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.