Monitoring a Windows host

You can monitor your Windows host with Instana. Instana provides comprehensive insights into the Windows host's performance, health, and resource utilization. This enables efficient troubleshooting, performance optimization, and proactive issue detection.

Configuring custom polling rate

Note:
Instana host sensor 1.2.1 and later support configuring the polling rate to reduce data ingestion. This feature is supported on self-hosted Instana backend 311 and later.

You can configure how often Instana polls the host to collect data and metrics by using the poll_rate parameter in the agent configuration file <agent_install_dir>/etc/instana/configuration.yaml as shown in the following example:

#Host Sensor Configuration
com.instana.plugin.host:
  poll_rate: 1 # values are in seconds. Default value is 1 second. Valid range: 1 to 600 seconds.

System information

Instana retrieves various system details from the host. You can view the following details of the host on the Instana GUI in the System pane:

Table 1. System information parameters
Parameter Description
OS The details of the operating system, the kernel version, and the architecture.
CPU The details of the CPU and the count.
GPU The details of the GPU, including model and clock speed.
Memory The amount of system memory in GiB (gigabytes).
Hostname The hostname of the host machine.
FQDN The fully qualified domain name. It is the complete domain name of the host, including the subdomain and top-level domain.
Machine ID The unique identifier for the host that is generated during the installation of the host distribution.
Host ID The MAC address of the host's network interface, which is a unique identifier for the network adapter.
Started At The time at which the host machine started.

Interfaces

You can find the following details:

  • Interfaces: The list of network interfaces and IP addresses.
  • Instana agent: The Instana agent for the host.
  • Process: The count and details of the processes that are running on the host.

Reporting status

You can see the historical availability of a Windows host in the Reporting Status chart in the Windows host dashboard. You can see three color indicators that identify the status of a host reporting to Instana.

Status Description Color indicator
Reporting The host reported to Instana without any interruptions. Green
Reporting - monitoring issues The host reported to Instana with some interruption (such as, network interruptions or agent monitoring issues) and was not fully available. Orange
Not Reporting The host was not reporting to Instana at all during this time. Red

The metric that is used to show this data on the host dashboard is based on the aggregation of messages received from the agent monitoring the host. Instana classifies a host as Reporting if Instana receives at least 98% of the expected messages in a given timeframe.

For example, if the metric aggregation time window is 5 minutes and the poll rate of the host is once per second, Instana expects to receive 300 messages from the host during that timeframe.

  • If at least 294 messages are received (98% of 300), you see the host status as Reporting.
  • If less than 294 but greater than 0 messages are received, you see the host status as Reporting – Monitoring Issues.
  • If no messages are received, you see the host status as Not Reporting.

Performance metrics

Instana displays the following performance metrics for the host.

CPU usage - percentage

Combined, the CPU usage values give a detailed view of how the host utilizes CPU resources.

Table 2. Reporting status indicators
Metric Description Granularity
CPU Usage The total CPU usage in percentage for the time range that you set. 1 second

Memory usage

Table 3. CPU usage percentage metrics
Metric Description Granularity
Memory Usage The total memory usage in percentage 1 second

CPU usage - total

Table 4. Memory usage metrics
Metric Description Granularity
User The amount of CPU time spent running user-space processes (applications and services). 1 second
System The amount of CPU time spent running kernel-space processes (OS core functions). 1 second
Wait The amount of CPU time spent waiting for input/output operations to complete. 1 second
Nice The amount of CPU time spent running processes with a lower priority (nice value). 1 second
Steal The amount of CPU time lost due to the hypervisor managing other virtual machines or containers on the same physical host. 1 second

Individual CPU usage

The CPU usage metric displays the following metrics in percentage on a graph for a selected time period for each CPU:

Table 5. CPU total usage metrics
Metric Description Granularity
User The amount of CPU time spent running user-space processes (applications and services). 1 second
System The amount of CPU time spent running kernel-space processes (OS core functions). 1 second
Wait The amount of CPU time spent waiting for input/output operations to complete. 1 second
Nice The amount of CPU time spent running processes with a lower priority (nice value). 1 second
Steal The amount of CPU time lost due to the hypervisor managing other virtual machines or containers on the same physical host. 1 second

Datapoint: Filesystem

Individual GPU usage

The following table outlines the individual GPU usage values:

Table 6. Individual GPU usage metrics
Metric Description Granularity Unit
Gpu Usage GPU usage percentage 1 second %
Temperature GPU temperature in Celsius 1 second °C
Encoder Encoder utilization 1 second %
Decoder Decoder utilization 1 second %
Memory Used Memory usage 1 second %
Memory Total Total GPU memory 1 second bytes
Transmitted throughput Transmitted data rate 1 second bytes/s
Received throughput Received data rate 1 second bytes/s

Instana collects the metric from nvidia-smi. The following table outlines the supported version of Nvidia graphics cards:

Table 7. Supported GPU card models
Brand Model
Tesla S1070, S2050, C1060, C2050/70, M2050/70/90, X2070/90, K10, K20, K20X, K40, K80, M40, P40, P100, V100
Quadro 4000, 5000, 6000, 7000, M2070-Q, K-series, M-series, P-series, RTX-series
GeForce Varying levels of support, with fewer metrics available than on the Tesla and Quadro products

Prerequisites

You must install the latest official Nvidia drivers.

For more information about starting a Docker container for Instana Agent with GPU support, see Enable GPU monitoring through Instana Agent container.

Instana designs GPU metric data collection for minimal impact by splitting polling and querying into two processes by using nvidia-smi. The background process is started in a loop mode and kept in memory. This process significantly improves the performance of metrics collection and prevents any potential overhead.

The sensor queries GPU metrics based on the configured poll rate (every second by default). The solution enables the sensor to collect accurate and up-to-date metrics every second for multiple GPUs without the overhead.

GPU Memory/Process

The following list of processes uses GPU:

Table 8. Individual CPU usage metrics
Datapoint Collected from Granularity
Process Name nvidia-smi 1 second
PID nvidia-smi 1 second
GPU nvidia-smi 1 second
Memory nvidia-smi 1 second

The following table outlines the supported version of Nvidia graphics cards for GPU memory:

Table 9. Supported GPU card models
Brand Model
Tesla S1070, S2050, C1060, C2050/70, M2050/70/90, X2070/90, K10, K20, K20X, K40, K80, M40, P40, P100, V100
Quadro 4000, 5000, 6000, 7000, M2070-Q, K-series, M-series, P-series, RTX-series
GeForce Varying levels of support, with fewer metrics available than on the Tesla and Quadro products

Memory

The following table outlines the unit for memory:

Table 10. Memory metrics
Metric Unit Description Granularity
Used Percentage Amount of memory in use 1 second

Instana displays the values on a graph for a selected time period.

Datapoint: Filesystem

File system

These metrics provide insights into file system performance, capacity, and usage, allowing administrators to monitor and optimize their storage systems effectively.

Table 11. File system performance metrics
Metric Description Granularity
Device The name of the device. 60 seconds
Options The options or parameters that are used when mounting the file system. 60 seconds
Free The amount of free space available on the file system. 1 second
Leaked Space that is allocated but not used, considered "leaked" or wasted. 1 second
Type The type of file system. 60 seconds
Capacity The total capacity of the file system. 60 seconds
Used The amount of space used on the file system. 1 second
Read/s The number of read operations per second. 1 second
Write/s The number of write operations per second. 1 second
Bytes read/s The number of bytes read per second. 1 second
Bytes written/s The number of bytes written per second. 1 second

Datapoint: Filesystem

* The total, read, and write usage datapoint metrics display the disk I/O utilization as a percentage.

* Leaked (refers to deleted files that are in use and equates to capacity - used - free. You can find these files with lsof | grep deleted).

By default, Instana only monitors local file systems. You can list the file systems that are monitored or excluded in the configuration.yaml file.

The name for the configuration setting is the device name, which you can obtain from the output of Get-PSDrive -PSProvider FileSystem.

The following example shows the list of file systems that are monitored:

com.instana.plugin.host:
  filesystems:
    - 'C'
    - 'D'
 

The following example shows the file systems that are included or excluded:

com.instana.plugin.host:
  filesystems:
    include:
      - 'C'
      - 'D'
    exclude:
      - 'E'
 

Server Message Block (SMB)

Note:

SMB share monitoring is supported on Windows Server 2019 and later.

To monitor the SMB shares, use the smb configuration parameter as shown in the following example:

com.instana.plugin.host:
  smb:
    - "\\\\server\\smbshare"
    - "Y:"

Network interfaces

The following table outlines the network traffic and errors per an interface.

Table 12. Network interface metrics
Metric Description Granularity
Interface The network interface that is used for communication. 60 seconds
Mac The Media Access Control (MAC) address of the network interface. 60 seconds
IPs The IP addresses assigned to the network interface. 60 seconds
RX Bytes The total number of bytes received by the network interface per second. 1 second
RX Errors The percentage of errors encountered while receiving data on the network interface. 1 second
TX Bytes The total number of bytes transmitted by the network interface per second. 1 second
TX Errors The percentage of errors encountered while transmitting data on the network interface. 1 second
Received/s The number of packets received by the network interface per second. 1 second
Transmitted/s The number of packets transmitted by the network interface per second. 1 second

Datapoint: Filesystem

TCP activity

These metrics provide insights into TCP connection activity, including established connections, segment transmission rates, and error occurrences.

Table 13. TCP activity metrics
Metric Description Granularity
Established The number of established TCP connections. 1 second
Open/s The number of new TCP connections opened per second. 1 second
In Segments/s The number of incoming TCP segments per second. 1 second
Out Segments/s The number of outgoing TCP segments per second. 1 second
Established Resets Percentage of established TCP connections that were reset per second. 1 second
Out Resets Percentage of outgoing TCP connections that were reset per second. 1 second
Fail Percentage of failed TCP connection attempts per second. 1 second
Error Percentage of TCP errors per second. 1 second
Retransmission Percentage of TCP retransmissions per second. 1 second

Datapoint: Filesystem

Windows services list

Instana does not monitor Windows services by default. This feature is enabled only when winServiceRegex is entered in the host agent configuration.yaml file. The winServiceRegex is a regular expression that is used to monitor services whose service name or display name matches the regular expression. For example, winServiceRegex: '(Sensor|Device)' monitors all services that include Sensor or Device in their service name or display name.

Table 14. Windows services metrics
Metric Description Granularity
Service Name Service name 60 seconds
Display Name Display name 60 seconds
PID Process ID 60 seconds
State Service state 60 seconds

Process top list

These metrics offer insights into running processes, including their process ID, name, CPU usage, normalized CPU usage, and memory consumption. The top process list is updated every 30 seconds and the list contains only the processes with system usage. For example, the processes with more than 10% CPU usage over the last 30 seconds or processes with more than 512 MB memory usage (RSS) are displayed in the process top list.

Linux top semantics are used. 100% CPU refers to full use of a single CPU core, and you can search a history of snapshots from the previous month. The normalized CPU is calculated by dividing the CPU by the number of logical processors.

Table 15. Process top list metrics
Metric Description Granularity
PID The unique identifier that is assigned to each process by the operating system. 30 seconds
Process Name The name of the process as defined by the application or service. 30 seconds
CPU The amount of CPU resources consumed by the process. 30 seconds
CPU (normalized) The CPU usage of the process, normalized to a scale. 30 seconds
Memory The amount of memory consumed by the process. 30 seconds

Datapoint: Filesystem

Windows failover cluster

Windows failover cluster monitoring provides comprehensive insights into the health, performance, and configuration of Windows Server Failover Clustering (WSFC) environments.

Instana does not enable Windows failover cluster monitoring by default. You must enable it explicitly in the agent configuration file:

com.instana.plugin.host:
  wsfcEnabled: true

After you enable the feature, the agent collects cluster metrics every 60 seconds.

Cluster information

Instana collects the following cluster-level metrics:

Table 16. Windows failover cluster information
Metric Description Granularity
Cluster Name The name of the failover cluster 60 seconds
Node Count The total number of nodes in the cluster 60 seconds
Nodes Up The number of nodes currently online 60 seconds
Nodes Down The number of nodes currently offline 60 seconds

Cluster nodes

For each cluster node, Instana collects the following metrics:

Table 17. Cluster nodes
Metric Description Granularity
Node Name The name of the cluster node 60 seconds
State The current state of the node (Up, Down, Paused, or Joining) 60 seconds
Drain Status The drain status of the node (NotInitiated, InProgress, or Completed) 60 seconds
Status Information Additional status information about the node 60 seconds

Resource groups

For each resource group in the cluster, Instana collects the following metrics:

Table 18. Resource groups
Metric Description Granularity
Name The name of the resource group 60 seconds
State The current state (Online, Offline, Failed, or Partial Online) 60 seconds
Owner Node The node currently owning the resource group 60 seconds

Resources

For each cluster resource, Instana collects the following metrics:

Table 19. Resources
Metric Description Granularity
Name The name of the cluster resource 60 seconds
State The current state of the resource (Online, Offline, or Failed) 60 seconds
Resource Type The type of resource (IP Address, Network Name, or Physical Disk) 60 seconds
Owner Node The node currently owning the resource 60 seconds
Owner Group The resource group containing this resource 60 seconds

Cluster Shared Volume (CSV)

For each CSV, Instana collects the following metrics:

Table 20. CSV
Metric Description Granularity
Name The name of the CSV 60 seconds
State The current state of the CSV (Online, Offline, or Failed) 60 seconds
Owner Node The node currently coordinating the CSV 60 seconds
Path The friendly path to the CSV 60 seconds
File System The file system type (NTFS, ReFS, or CSVFS) 60 seconds
Size (GB) The total size of the volume in gigabytes 60 seconds
Free Space (GB) The available free space in gigabytes 60 seconds
Used (%) The percentage of space used 60 seconds

Networks

For each cluster network, Instana collects the following metrics:

Table 21. Networks
Metric Description Granularity
Name The name of the cluster network 60 seconds
State The current state of the network (Up, Down, or Partitioned) 60 seconds
Role The role of the network (ClusterAndClient, ClusterOnly, or None) 60 seconds
Address The network address 60 seconds
Address Mask The network subnet mask 60 seconds

Health signatures

Instana continuously evaluates a knowledge base of health signatures against incoming metrics for each sensor. They are used to raise issues or incidents depending on the user impact.

Built-in events trigger issues or incidents based on failing health signatures on entities, and custom events trigger issues or incidents based on the thresholds of an individual metric of an entity.

For more information about the built-in events for the Host sensor, see Built-in events reference.