Performance Metric Overrides Cause Veeam MP Monitors to Work Incorrectly
If you set an override for a Veeam MP performance metric in a way that the specified data collection time interval exceeds the OpsMgr time range configured to collect dependent metrics, the corresponding Veeam MP monitor will not be able to work correctly, and all dependent metrics will return zero values.
For example, if you override the Veeam Hyper-V Host CPU Usage MHz rule and set the Frequency parameter to a value that exceeds the Frequency value configured for the dependent aggregated Veeam Hyper-V Cluster CPU Used % rule, the Veeam HyperV: Cluster CPU Usage monitor will report zero metric values.
To avoid the issue, configure the performance metric override correctly taking into account the OpsMgr data collection time range:
Aggregated Performance Monitor on Management Server | Aggregated Performance Rule on Management Server | Performance Rule on Hyper-V Server |
|---|---|---|
Veeam HyperV: Cluster CPU Usage | Veeam Hyper-V Cluster CPU Used % | Veeam Hyper-V Host CPU Usage MHz |
Veeam HyperV: Cluster Memory Usage | Veeam Hyper-V Cluster Memory Used % | Veeam Hyper-V Host Memory Used MB |
Veeam HyperV: Cluster Disk Latency Analysis | Veeam Hyper-V Cluster Disk Highest Latency | Veeam Hyper-V Disk Read Latency |
Veeam Hyper-V Disk Write Latency | ||
Veeam Hyper-V Cluster Disk IOPS | Veeam Hyper-V Disk IOPS | |
Veeam Hyper-V Cluster Disk Usage MB/s | Veeam Hyper-V Disk Usage MB/s | |
Veeam Hyper-V SMB Volume Free Space GB | Veeam Hyper-V Host SMB Volume Free Space GB | |
Veeam HyperV: SMB Volume Free Space Analysis | Veeam Hyper-V SMB Volume Free Space % | Veeam Hyper-V Host SMB Volume Free Space % |