<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: System Status
On the System Status tab, you can view relevant system information. Furthermore, this page shows interesting usage statistics. Use the quick links for fast access to status information.
You might need this data for debugging or when you contact the Paessler support team. They ask you in some cases to provide system status information to analyze any issues with PRTG.
This documentation refers to an administrator that accesses the PRTG web interface on a master node. Other user accounts, interfaces, or failover nodes might not have all of the options in the way described here. In a cluster, note that failover nodes are read-only by default.
If 15 minutes (900) seconds have passed since your last credential-based login and you open a setup page from a different setup page, PRTG asks you to enter your credentials again for security reasons. A dialog box appears. Enter your Login Name and Password and click OK to continue.
Quick Links
In this section:
Software Version and Server Information
This section shows information about the software version and the PRTG core server system.
Software Version and Server Information
|
|
PRTG Version
|
Shows the exact build version of the PRTG installation.
|
Auto-Update Status
|
Shows the latest auto-update message available from the auto-update. For example, the message indicates that an update was successfully installed.
This information is not displayed in PRTG Hosted Monitor.
|
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.
If you run PRTG on virtual systems, some of the information might not be available.
This information is not displayed in PRTG Hosted Monitor.
|
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.
|
User Name
|
Shows the user name of the user account that you are logged in to PRTG with.
|
Active User Sessions
|
Shows the user names of all user accounts that are logged in to PRTG.
When a user account logs out, it takes up to 1 minute until the user name disappears.
|
Browser
|
Shows the name and user agent string of the browser that you are viewing this page with.
|
License Information
This section shows information about your license.
License Information
|
|
License Status
|
Shows the activation status of this PRTG installation. Usually, PRTG automatically completes the activation during installation or when you change your license information.
If PRTG cannot directly connect to the internet, a manual activation is necessary.
For more information, see section Activate the Product.
|
License Name
|
Shows the owner of the license that you use for this PRTG installation, for example ExampleOrganization.
The License Name (PRTG Network Monitor only), license key, and system ID make up 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 when you install PRTG or when you change your license key.
|
License Key
|
Shows the license key that you use for this PRTG installation.
The License Name (PRTG Network Monitor only), license key, and system ID make up your license information.
|
System ID
|
The system ID is a fixed value that is automatically assigned to a PRTG installation.
The License Name (PRTG Network Monitor only), license key, and system ID make up your license information.
|
Licensed Edition
|
Shows the license that you use for this PRTG installation. This determines how many sensors you can use in PRTG.
|
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 number of days that remain for your active maintenance contract. You can buy maintenance for each license.
If you have an active maintenance contract, you have access to any available updates and to our premium email support.
This information is not visible in Paessler PRTG Enterprise Monitor.
|
Number of Sensors
|
Shows the number of sensors that you can use in PRTG. If you reach the limit, PRTG automatically sets each new sensor that you add to the Paused status.
Editions that allow an unlimited number of sensors do not restrict the number of possible sensors by license, so you can create sensors until you reach the performance limit. This means that you can use about 10,000 sensors per PRTG core server. However, this number depends on the performance of the PRTG core server system, and sensors and scanning intervals.
For more information, see section System Requirements.
|
System Startup Log
This section shows the log information that was 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.
System Startup Log
System Warnings
This section shows if there are any warnings. Usually, you see None.
System Warnings
Cluster Status
This setting is only visible if you have a failover cluster. This section shows all of your cluster nodes.
Cluster Status
|
|
Node x
|
Shows the name and type of the cluster node (primary node or secondary node) and its status (current master node or failover node). It also shows all connections from this cluster node to the other cluster nodes.
For more information, see section Cluster Status.
|
Local Status
This setting is only visible if you have a failover cluster. This section shows information about the cluster node that you are logged in to.
Local Status
|
|
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.
|
Cluster Connections
This setting is only visible if you have a failover cluster. This section shows information about the connections between the cluster nodes.
Cluster Connections
|
|
State of Local Node
|
Shows the treeversion and size of the server volume, both types of internal system information.
|
State of Cluster Members
|
Shows the name and IP address, a state cyclic redundancy check (CRC) code, the time stamp of the last "keep alive" signal, the size of the buffer, and the remote IP address of each cluster node.
|
Message State of Cluster Members
|
Shows the name and unique identifier, the connection state, and statistics about the cluster message system of each cluster node.
|
PRTG Core Server System Memory
This section 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.
PRTG Core Server System Memory
|
|
Committed
|
The amount of memory that your system commits to the PRTG core server system.
|
Allocated
|
The amount of memory that the PRTG core server system is currently using.
|
Unused
|
The amount of allocated memory that the PRTG core server system is currently not using.
|
Free Physical
|
The amount of free memory that is currently available in the physical memory of the PRTG core server system.
|
Total Physical
|
The total amount of memory that is provided by the physical memory of the PRTG core server system.
|
Free Pagefile
|
The amount of free memory that is currently available in your system’s pagefile(s).
|
Total Pagefile
|
The total amount of memory of your system’s pagefile(s).
|
Free Virtual
|
The amount of free memory that is available in the virtual memory of the PRTG core server system.
|
Total Virtual
|
The total amount of memory of the virtual memory of the PRTG core server system.
|
Free Effective
|
The effective amount of free memory on your PRTG core server system. This corresponds to Free Pagefile.
|
Object Count
|
The number of PRTG-internal data structures, also known as tree nodes, for example, the number of sensors, users, and reports.
|
BaseInstance
|
The amount of memory that is used for the tree node Instance.
|
BaseAccess
|
The amount of memory that is used for the tree node Access Rights.
|
BaseHistory
|
The amount of memory that is used for the tree node History of Configuration Changes.
|
BaseCurrent
|
The amount of memory that is used for the tree node Current Configuration Information.
|
BaseData
|
The amount of memory that is used for the tree node Configuration Data.
|
BaseChannel
|
The amount of memory that is used for the tree node Channel Settings.
|
BaseTrigger
|
The amount of memory that is used for the tree node Trigger.
|
BaseIDs
|
The amount of memory that is used for the tree node IDs.
|
BaseLookup
|
The amount of memory that is used for the tree node Sensor Lookups.
|
BaseCheck
|
The amount of memory that is used for the tree node Check Requests.
|
BaseDeplist
|
The amount of memory that is used for the tree node Dependency List.
|
Datasets
|
The amount of memory that is currently used for datasets, like for graphs.
|
State
|
The amount of memory that is currently used for user-specific datasets.
|
Interface
|
The amount of memory that is currently used for tree node-specific table objects.
|
IndexCache
|
The amount of memory that is currently used for the index dataset cache that is particularly important in a cluster.
|
TreeTotal
|
The total amount of memory that is used by the PRTG tree.
|
DatasetCache
|
The amount of memory that is currently used for the dataset cache, in particular regarding historic data. In parentheses, you see the number of datasets that are saved in the cache.
|
StorageSystem
|
The amount of memory space that is currently used for the storage system.
|
Sessions
|
The amount of memory that is currently used for sessions. A user can activate more than one session. In parentheses, you see the number of currently activated sessions.
|
StateObjects
|
The number of user-specific state objects that are found in the memory of the PRTG core server system.
|
Thread Information
The section shows machine-oriented information regarding threads that are 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.
Thread Information
Activity History
This section 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.
Activity History
|
|
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.
|
Auto-Discovery Tasks
This section shows information on the auto-discovery.
Auto-Discovery Tasks
|
|
Running
|
Shows the number of auto-discovery tasks that are running.
A high number of auto-discovery tasks can negatively influence system performance.
|
Background Tasks
This section shows information on background tasks.
Background Tasks
|
|
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, PRTG does this calculation after every PRTG core server restart.
|
Toplist Buffer
|
Shows the size of the Toplist buffer. When you use Flow (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 the buffer size reaches 500, PRTG drops Toplist data, which can lead to incorrect Toplist values for the sensors.
|
Similar Sensors Detection
|
Shows the status and the selected setting for the depth of the similar sensors analysis.
|
Recommended Sensors Detection
|
Shows the status of the detection engine and the tasks of the recommended sensors detection.
|
Database Objects
This section shows statistic information about your monitoring configuration. This information might be necessary when contacting the Paessler support team.
Database Objects
|
|
Probes
|
Shows the total number of probes in the PRTG installation.
|
Groups
|
Shows the total number of groups in the PRTG installation.
|
Devices
|
Shows the total number of devices in the PRTG installation.
|
Sensors
|
Shows the total number of sensors in the PRTG installation.
|
Channels
|
Shows the total number of channels in the PRTG installation.
|
User Groups
|
Shows the total number of user groups in the PRTG installation.
|
Users
|
Shows the total number of users in the PRTG installation.
|
Notifications
|
Shows the total number of notifications in the PRTG installation.
|
Schedules
|
Shows the total number of schedules in the PRTG installation.
|
Maps
|
Shows the total number of created maps in the PRTG installation.
|
Libraries
|
Shows the total number of created libraries in the PRTG installation.
|
Reports
|
Shows the total number of reports in the PRTG installation.
|
BitField/Boolean/Integer/Range Lookups
|
Shows the total number of used lookups by lookup type.
|
Requests/Second
|
Shows a value that is 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 that you use as well as on the performance of the probe system.
|
Sensors Sorted by Impact on System Performance
This section shows all sensors that you use 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 a high or 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.
For an overview list of sensors sorted by performance impact, see section List of Sensors by Performance Impact.
Sensors Sorted by Impact on System Performance
Sensors Sorted by Interval
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.
Sensors Sorted by Interval
Probes
This section lists all probes in your monitoring setup. If there are no remote probes, 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 you are logged in to a failover node, the cluster probe on this cluster node appears as local probe.
Probes
|
|
Probe #x "[Name]"
|
Shows information about the connection status. 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 address 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.
|
System Settings
This sections shows information about system settings.
System 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 IP Addresses
|
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 ports 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 type of port 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 to and from the PRTG web server.
This is only shown if you use an SSL/TLS-secured connection.
|
Web Server Ciphers
|
Shows the ciphers used by the PRTG web server.
This is only shown if you use an SSL/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 use an SSL/TLS-secured connection.
|
Incoming Probe Connection Binding
|
Shows a combination of the incoming probe connection IP address and the incoming probe connection port.
|
Incoming Probe Connection IP Addresses
|
Shows a list of all IP addresses on which PRTG listens for incoming remote probe connections.
This is the same information as in the Core & Probes settings. 0.0.0.0 means that the PRTG core server listens on all local network adapter IP addresses.
|
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 IP Addresses
|
Shows all source IP addresses that PRTG accepts for incoming remote probe connections.
This is the same information as in the Core & Probes settings. any means that all remote probe connections are accepted, regardless of the IP address of the remote probe system.
|
Probe Deny IP Addresses
|
Shows all source IP addresses that PRTG denies for incoming remote probe connections.
This is the same information as in the Core & Probes settings. Denied IP addresses are superior to allowed IP addresses. If this field is empty, there are no denied IP addresses.
PRTG automatically adds the IP address of a remote probe system to this list when you delete a remote probe from the 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.
|
Web Server Activity
This section shows statistics about the PRTG 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.
Web Server Activity
|
|
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 ms
|
Shows for how many (percent) of the HTTP requests above the page delivery took longer than 500 milliseconds (ms).
|
HTTP Requests > 1000 ms
|
Shows for how many (percent) of the HTTP requests above the page delivery took longer than 1,000 ms.
|
HTTP Requests > 5000 ms
|
Shows for how many (percent) of the HTTP requests above the page delivery took longer than 5,000 ms.
|
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.
|
Failed Logins (Recent/Total)
|
Shows the number of recent failed logins and failed logins in total.
PRTG only shows this statistic when the number of failed logins is larger than 50.
|
Synchronization
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 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.
Synchronization
|
|
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 need 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.
|
More
Knowledge Base
How can I speed up PRTG—especially for large installations?
Setup
Others
There are some settings that you must make in the PRTG Administration Tool. For more details, see the sections: