cdm iostat QOS metrics are not being collected
Article ID: 196553
Updated On:
Products
Issue/Introduction
We have enabled cdm iostat metrics using cdm MCS profile but QOS metrics are not coming in. Is iostat supported on Windows?
Environment
- Release: Any supported UIM version
- Component: UIM - CDM WITH IOSTAT
Cause
- Windows OS
- Guidance
Resolution
cdm iostat metrics need to be configured from the Admin Console
New metrics are introduced for Windows in cdm probe 7.10 and higher.
(Linux, AIX and Solaris platforms only) Monitor iostat: enables the iostat monitoring of the host system devices.
The cdm iostat probe functionality was merged into the cdm probe beginning with cdm v4.80, and higher.
Additional Information
Additionally, if you need to collect disk IO metrics on Windows systems it is also possible to use ntperf for disk IO metrics and you could create an ntperf probe package to implement the monitoring and alarming for multiple hosts.
IMPORTANT:
Additionally, ensure that the data_engine QOS has an override set for retaining any disk IO metrics, e.g., set that to 1 day or only a few days so you don't end up with huge RN tables due to aggressive collection with short intervals.
Also consider the monitoring interval in your decision. Try using 5 minutes or more but if you set it more aggressively, say 1 or 3 minutes, then keep the retention number low so you don't end up with large RN tables as a result. Try it out on one system first and note the results and collection, and growth of the table. Then adjust your configuration based on the results/table growth.
CDM itself includes all the iostat monitoring functionality and no additional probe is needed such as “iostat” to be deployed for the monitoring.
See also:
Feedback
