We have redesigned the host overview page.
As soon as data about hosts is collected, Dynatrace Davis® AI starts baselining the data instantly. Each metric displayed on the host overview page is part of Davis AI source data used for automatically identifying potential performance issues at the infrastructure or full-stack level.
How to get there:
All relevant host metrics are shown on a single page, which is divided into several logical sections.
The host notifications bar gives you a quick overview of the host state. Select a notification item to display more information.
Select Properties and tags on the notifications bar to display the Properties and tags panel, which displays metadata about the selected host:
On the notifications bar, Vulnerabilities indicates the top detected vulnerabilities affecting the selected host.
Select Vulnerabilities on the notifications bar to display the Vulnerabilities panel, which lists the most severe third-party vulnerabilities and code-level vulnerabilities related to this host.
Example third-party vulnerabilities:
Example code-level vulnerabilities:
If you're missing the security permissions for the selected management zone, the Vulnerabilities tab on the notification bar shows Not analyzed
.
On the notifications bar, Availability indicates the percentage of time that the host was online and responsive to requests. Dynatrace detects and shows operating system shutdowns (including reboots) and periods when a host is offline (for example, if the host is down unexpectedly).
Select Availability on the notifications bar to display the Host availability panel, which charts host availability over time.
For details, see Host availability.
An SLO is directly connected to a host when the entity selector of an SLO meets the following criteria:
"HOST"
.To see only SLOs that are directly connected to the host, make sure that Show only directly connected SLOs is turned on.
An SLO isn't directly connected to a host when, in the entity selector of an SLO, no entity ID is provided.
Example: When generic values, such as type("HOST"),tag("slo")
are provided, the query results in all SLOs for all hosts, including the current host.
To see SLOs that are not directly connected to the host, turn off Show only directly connected SLOs.
Select Details to view a chart of the respective SLO metrics.
In Actions, select
If no SLOs are found, you can
Select a different timeframe in the upper-right corner.
Select Add SLO to create an SLO in the SLO wizard.
The Incoming connections section displays a table of hosts that are upstream from the selected host.
The Outgoing connections section displays a table of hosts that are downstream from the selected host.
Go to the Host performance section for quick insights with relevant metrics: CPU, memory, and network metrics, with different metric aggregations for the selected timeframe. Timeline browsing lets you pinpoint selected anomalies in all metric charts simultaneously, making it easier to understand the relationships between the various infrastructure components at a specific point in time.
It is easy to inspect maximum or minimum peaks in resource consumption, as each metric chart allows the selection of a different aggregation. Custom metrics can also be displayed instead of the default metrics, allowing inspection of specific relationships across metrics that might be critical for any specific host configuration.
Select in the upper-right corner of a chart to:
To get a better understanding of process behavior, go to the Process analysis section, which charts and lists processes running on the selected host. Select a process to drill down for details about that process on the host.
Select in the upper-right corner of a chart to:
OneAgent version 1.237+
The Process instance snapshots section offers additional insights into the most resource-consuming processes running on your host and the processes defined for Process availability monitoring.
A single process instance snapshot is a set of monitoring data for processes. It contains data on the process CPU usage (%), Memory usage (B), Incoming network traffic (KB), and Outgoing network traffic (KB) measured at one-minute intervals. A single snapshot contains 20 minutes of monitoring data: 10 minutes preceding the trigger and 10 minutes after the trigger. Each host can report only 60 minutes of these metrics per day. A process is considered for the snapshot if its consumption of CPU, memory, or network is more than 1%.
A process instance snapshot is triggered by high CPU, memory, or network usage on your host. You can also request a process snapshot manually. Select in the upper-right corner of the section and select Request process snapshot now. Wait for a message confirming a successful snapshot trigger. Process snapshot data should appear after you reload the page within 90 seconds.
Additionally, for processes defined for Process availability monitoring, the snapshot shows how the processes behaved before they disappeared and if they reappeared within 10 minutes.
You can enable process instance snapshots at a host or environment level.
https://your-environment/ui/settings/HOST_GROUP-NAME
, select Process instance snapshots, and turn on Enable process instance snapshots.On the same settings page, you can also lower the limit of processes reported in a single snapshot. The maximum/default setting is 100 processes.
To identify disk performance bottlenecks, go to the Disk analysis section , which displays all mount points for Linux systems and all volumes for Windows. At a glance, you can see the disk space usage and throughput metrics, in addition to other selected disk metrics, to allow rapid identification of any disk performance issues.
Each mount point (Linux) or volume (Windows) has its own performance metrics in addition to the combined metrics. This allows spotting a slow or erratic disk much easier. Alerts can be set for individual disks as for the combined charts.
Select in the upper-right corner of a chart to:
Disk throughput read
File system read throughput in bits per second
Disk throughput write
File system write throughput in bits per second
Disk available
Amount of free space available for user in file system. On Linux and AIX it is free space available for unprivileged user. It doesn't contain part of free space reserved for the root.
Disk read bytes per second
Speed of read from file system in bytes per second
Disk write bytes per second
Speed of write to file system in bytes per second
Disk available %
Percentage of free space available for user in file system. On Linux and AIX it is % of free space available for unprivileged user. It doesn't contain part of free space reserved for the root.
Inodes available %
Percentage of free inodes available for unprivileged user in file system. Metric not available on Windows.
Inodes total
Total amount of inodes available for unprivileged user in file system. Metric not available on Windows.
Disk average queue length
Average number of read and write operations in disk queue
Disk read operations per second
Number of read operations from file system per second
Disk read time
Average time of read from file system. It shows average disk latency during read.
Disk used
Amount of used space in file system
Disk used %
Percentage of used space in file system
Disk utilization time
Percent of time spent on disk I/O operations
Disk write operations per second
Number of write operations to file system per second
Disk write time
Average time of write to file system. It shows average disk latency during write.
OneAgent installer based deployment:
OneAgent application-only deployment:
Application-only OneAgents provide a reduced set of Disk I/O metrics, such as:
Disk read bytes per second
Disk write bytes per second
Disk read operations per second
Write operations per second
Linux uses the file /proc/diskstats
that provides information about disk I/O activity on the system. /proc/diskstats
does not provide any information about network mounts.
Solaris doesn't provide any Disk I/O information.
AIX reports only the Disk I/O information about Disk read bytes per second
and Disk write bytes per second
.
Windows only The disk page shows only local disks with a letter and/or a mount point. For remote disks, the system recognizes and displays only the shares with CIFS protocol. For details, see https://dt-url.net/jw03uor.
Set an exclusion filter to avoid problems with special mount points:
OneAgent version 1.293+
Use Disk Edge to set up alerts for automatic detection of performance anomalies related to disk infrastructure.
Disk Edge provides automatic detection of performance anomalies related to disk infrastructure. Use these settings to tailor detection sensitivity to a specific disk's name and/or custom metadata. Defining custom properties can help with the post-processing of the event.
You can define policies on the host, host group, and environment levels.
disk.all_mountpoints
disk.device_name
disk.mountpoint
dt.entity_host
dt.host_group.id
host.name
Event
Severity
Related OneAgent metric
Available disk space (%) below
Smaller value is more severe
DiskStats object field: availPercentage
Mintv2 metric: dt.host.disk.free
Timeseries: builtin:host.disk.free
Available disk space (MiB) below
Smaller value is more severe
DiskStats object field: avail
Mintv2 metric: dt.host.disk.avail
Timeseries: builtin:host.disk.avail
Available inodes (%) below
Smaller value is more severe
DiskStats object field: availINodesPercentag
Mintv2 metric: dt.host.disk.inodes_avail
Timeseries: builtin:host.disk.inodesAvail
Available inodes (number) below
Smaller value is more severe
Calculated from Diskstats: totalINodes
* availINodesPercentage
Mintv2 metric: dt.host.disk.inodes_avail
* dt.host.disk.inodes_total
Timeseries: builtin:host.disk.inodesTotal
* builtin:host.disk.inodesAvail
Is read only file system
N/A
Disk object field: readOnly
Mintv2 metric: N/A
Timeseries: N/A
Read time (ms) exceeding
Larger value is more severe
Disk object field: readTime
Mintv2 metric: dt.host.disk.read_time
Timeseries: builtin:host.disk.readTime
Write time (ms) exceeding
Larger value is more severe
Disk object field: writeTime
Mintv2 metric: dt.host.disk.write_time
Timeseries: builtin:host.disk.writeTime
To spot network-related issues rapidly, go to the Network analysis section, which lists all network interfaces and combined metrics for all of them, in addition to individual metrics per network interface.
Use this section to:
Select in the upper-right corner of a chart to:
Use the Memory analysis section to analyze:
Select in the upper-right corner of a chart to:
The events section displays recent host events that Davis AI has generated, with a clear timeline view to quickly identify critical events. The timeline view is interactive, filtering events around a specific moment, making it easier to isolate a particular event. In addition, different event types are color-coded for easier and faster identification and browsing.
The log viewer timeline is interactive, allowing a global timeline selection. Use it to identify issues around a specific log event and see how it relates to hosting performance or processes.
Select in the upper-right corner of the Logs section to: