PRTG Manual: Core Health Sensor
The Core Health sensor is a probe-dependent sensor that monitors internal PRTG parameters. It shows the status of the PRTG core server and checks various parameters of the PRTG core server that have an impact on the stability of the system.
Core Health Sensor
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Core Status
- French: État du serveur central
- German: Serverzustand
- Japanese: コアの正常性
- Portuguese: Funcionamento do servidor central
- Russian: Работоспособность базового сервера
- Simplified Chinese: 核心健康状况
- Spanish: Salud de servidor central
Consider the following remarks and requirements for this sensor:
Remark |
Description |
|---|---|
Performance impact |
This sensor has a very low performance impact. |
Limits |
This sensor has predefined limits for several metrics. |
Sensor creation |
PRTG automatically creates this sensor. You cannot delete it. |
Sensor usage |
You can only set up this sensor on a local probe device. |
Memory information |
You can also find information related to PRTG core server system memory under Setup | PRTG Status. |
Basic Sensor Settings
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
- corehealthsensor
For more information about basic sensor settings, see section Sensor Settings.
Sensor Display
Setting |
Description |
|---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how this sensor shows different channels:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click 
under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
|---|---|
Age of Code |
The time that has passed since the last update of your PRTG core server. Update regularly to get the best security and stability for PRTG, as well as the latest features. We recommend that you use the auto-update to automatically get new versions.
|
Committed Memory |
The amount of memory committed to the PRTG core server as reported by the memory manager |
Configuration Last Saved |
The time passed since the configuration file was last saved successfully. PRTG saves the configuration every 24 hours. If the configuration cannot be saved, PRTG creates a ticket as soon as the saving process has failed, and warns you via this channel after 26 hours. None of your changes to PRTG can be saved if this happens. In this case, restart your PRTG core server to save the file.
|
CPU Load |
The CPU load (%). Extensive CPU load can lead to false, incomplete, and incorrect monitoring results. This value should usually stay below 50%. |
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
Free Page File Memory |
The amount of free page file memory that is available on the system. Page file memory is aggregated RAM and the size of page file. It is the maximum amount of memory that is available on the system to be used for all running processes. If it gets too low, the system can break down, and at least some applications throw Out of memory errors. |
Free Physical Memory |
The amount of free physical memory that is available on the system. This is the RAM that is physically built into the computer. If it gets too low, the system becomes very slow and PRTG no longer works in a useful way. Some sensors might not be displayed correctly and show the Unknown status. |
Free Virtual Memory |
The address space on the system that PRTG can access. PRTG cannot use more memory than reported here, which is independent from free page file and physical memory. On a 32-bit operating system, the maximum is 2 GB (3 GB with special settings under Windows). On a 64-bit operating system, it is 4 GB if PRTG runs as a 32-bit version, and unlimited if it runs as a 64-bit version (PRTG core server only). If the free virtual memory gets too low, PRTG throws Out of memory errors or the message not enough storage to process this command. This message is visible in the Core log. |
Handles |
The counter for the data structures of the operating system. It is responsible for internal resource management. Investigate obviously increasing values that occur repeatedly. |
Health |
The sum of the PRTG core server state as a value between 100% (healthy) and 0% (failing). Investigate frequent or repeated health values below 100%.
|
Maintenance Days |
The remaining maintenance days of your PRTG Network Monitor license. If your maintenance is going to expire soon, act in time to make sure that you continue to get updates and access to new features for PRTG Network Monitor.
|
Notifications in Send Queue |
The number of notifications that are in the send queue |
Number of State Objects |
The number of user-specific state objects that are found in the memory of the PRTG core server system |
Probe Messages per Second |
The number of messages sent from all probes to the PRTG core server |
Raw Data Buffer |
The amount of raw data that is temporarily stored on the physical memory during I/O operations on the disk. Usually, this value should be 0 (or very low). Investigate increasing values. |
Threads |
The number of program parts that are running simultaneously. This number can increase with heavy load. Usually, this number should not exceed 100. |
KNOWLEDGE BASE
What security features does PRTG include?
