PRTG Manual: Application Server Health (Autonomous) Sensor
The Application Server Health (Autonomous) sensor monitors the health of the PRTG application server and checks various parameters that can affect the quality of the monitoring results.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Application Server Health (Autonoom)
- French: État du serveur d’application (autonome)
- German: Zustand des PRTG Application Servers (Autonom)
- Japanese: アプリケーションサーバーの正常性(自律)
- Portuguese: Funcionamento do servidor de aplicativos (autônomo)
- Russian: Состояние сервера приложений (автономного)
- Simplified Chinese: 应用程序服务器运行状况(自治)
- Spanish: Salud de servidor de aplicaciones (autónomo)
- This sensor has a very low performance impact.
- PRTG automatically creates this sensor. You cannot add it manually.
- This sensor is part of the new UI and API. For more information, see the Knowledge Base: I want to use the new UI and new API. What do I need to know?
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets. If the name contains angle brackets (<>), PRTG replaces them with braces ({}) for security reasons. For more information, see the Knowledge Base: What security features does PRTG include? |
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe. This setting is for your information only. You cannot change it. |
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited. It is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>). For performance reasons, it can take some minutes until you can filter for new tags that you added. The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority () to the highest priority (). |
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor. You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab. |
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you select Stack channels on top of each other above. Select a unit from the list. All channels with this unit are stacked 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.
For more information, see section Root Group Settings, section Scanning Interval.
For more information, see section Root Group Settings, section Access Rights.
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
For more information, see section Root Group Settings, section Channel Unit Configuration.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
API Requests |
The number of API requests |
Average CPU Utilization (%) |
The CPU usage of the PRTG application server process (%) |
Core Messages |
The number of messages that the PRTG application server receives from the PRTG core server |
CPU Utilization of Garbage Collector (%) |
The CPU usage of the PRTG application server garbage collector (%) |
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 |
Dropped API Requests |
The number of API requests per second that were dropped due to timeouts This channel has default limits
|
Free Memory (%) |
The free system memory of the PRTG application server system (%) |
Health |
The sums of the PRTG application server state as a value between 100% (healthy) and 0% (unhealthy). Investigate if values are frequently under 100%. This channel is the primary channel by default. |
Heap Size (%) |
The heap size of the memory that the PRTG application server uses (%) |
Process Memory Usage |
The memory usage of the PRTG application server process |
Response Time |
The average response time of the new API |
Response Time 95th Percentile |
The 95th percentile of the response time of the new API |
Routines |
The number of concurrently running routines in the PRTG application server |
Sessions |
The number of active user sessions |
Stack Size (%) |
The relative stack size of the memory that the PRTG application server uses (%) |
KNOWLEDGE BASE
I want to use the new UI and new API. What do I need to know?