OneAgent health overview
The OneAgent health overview empowers you to discover all your deployed OneAgent modules at scale and detect anomalies before they become problems. With the OneAgent health overview, for example, you can discover:
- Outdated OneAgent modules that require an update to continue full Dynatrace support.
- Connectivity issues between OneAgent modules and your Dynatrace Cluster.
- Incompatible OneAgent modules that require corrective actions.
- Processes that require a restart to continue monitoring.
- OneAgent modules where auto-update is disabled.
Dynatrace version 1.265+
To get started with the OneAgent health overview, from the Dynatrace menu, go to Manage > OneAgent health.
The OneAgent health overview comprises
An area chart focusing on the Health state metric.
The area chart includes data on OneAgent modules during the selected timeframe. You can split the area chart by health state, monitoring state, module type, module version, process type, and operating system type.
A data table presenting a variety of attributes of the contributing OneAgent modules.
The data table contains real-time data of the OneAgent modules seen in your environment in the last 5 minutes. You can filter it by specific attributes. To display additional attributes, select Configure columns.
The environment permission View sensitive request data is required to visualize data in this table.
Select a specific data point in the area chart to see the contributing OneAgent modules in the data table.
Health state metric
The Health state metric indicates the health state of your deployed OneAgent modules. It is divided into four classes—Critical, Warning, Info, and Healthy. Each class has different implications.
Health state examples
The following conditions are applied to your OneAgent modules and result in specific recommendations.
Installer version date older than 11 months
Update OneAgent to a newer version to maintain full Dynatrace support.
Module heartbeat is 180 seconds overdue
Dynatrace hasn’t received data from this module for 180 seconds. There might be communication problems, or your process might have exited unexpectedly.
Host ID conflict
Multiple monitored hosts report that they’re using the same host identifier. This unexpected situation might be the result of machine cloning. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.
Host quota exceeded
Monitoring is currently disabled. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.
Installer version marked as faulty by Dynatrace
Update OneAgent to a newer version. Processes might also need to be restarted.
Module version marked as faulty by Dynatrace
Update OneAgent to a newer version. A process restart might also be required.
Installer version is between 9 and 11 months old
Update to a newer OneAgent version to stay current.
Minimum OneAgent version incompatible
Update OneAgent to a newer version. A process restart might also be required, even if you’ve already updated your module.
Process restart needed
Your module version is outdated. Restart your process to update the module to a newer OneAgent version.
Enable auto-update to stay current.
You can see an en example below of modules where the installer version is older than 11 months. The modules are therefore marked as Critical.
- Only the Health state metric includes the z/OS Java module and AWS Lambda, Azure, and GCP integrations.
- Only OneAgent modules seen in the last 5 minutes are shown in the data table.
- Only the data table can be filtered by management zone.