Chat now with support
Chat with Support

Foglight for Hyper-V 7.1.0 - User Guide

About Hyper-V Monitoring in Foglight Evolve Cloud Agent administration Performance monitoring with the Hyper-V Environment dashboard Performance investigation with the Hyper-V Explorer Hyper-V Monitoring in Foglight Evolve Cloud alarms Appendix: Hyper-V Agent error codes

Setting the alarm sensitivity level

Alarms are triggered by bottlenecks in your monitored environment. Hyper-V Monitoring in Foglight Evolve Cloud generates alarms when a rule determines that certain pre-defined conditions are met.

The alarm sensitivity in Hyper-V Monitoring in Foglight Evolve Cloud dictates the level of alarms the system generates, stores, and displays. You can configure the level of alarm sensitivity through the Hyper-V Configuration dashboard. The alarm sensitivity level you set here applies to your entire Hyper-V infrastructure.

3
On the navigation panel, under Dashboards, choose Hyper-V > Hyper-V Agent Administration.
4
On the Hyper-V Agent Administration dashboard, click Set Alarm Sensitivity Level.
The Set Alarm Sensitivity Level dialog box appears.
Figure 254. Set Alarm Sensitivity Level dialog box
5
In the Set Alarm Sensitivity Level dialog box, select the desired sensitivity level: Essential, Normal, or Tuning.
6
Click Save.
The Set Alarm Sensitivity Level dialog box closes.
3

Appendix: Hyper-V Agent error codes

This appendix lists the error codes that the Hyper-V Agent returns when it encounters a connection problem. The error codes result in messages that appear in the alarms raised by the HPV Cluster CPU Estimated Fill Time rule.

Null command

Controller failure

Unsupported platform

End point failure

Async not enabled

Null listener

Null host configuration

Thread service failure

Login failure

Unknown host

Connection failure

Connection time-out

Internal error

Access denied

Unknown error

Invalid WQL (WMI Query Language)

Unsupported query type

Invalid commandlet

Invalid commandlet parameter

Server error commandlet

No scheme

No domain

No agent home

Unsupported scheme

Unsupported authorization

WinRM service unavailable

No key domain controller

Sub-system controller

Sub-system wiseman

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating