Chatee ahora con Soporte
Chat con el soporte

Foglight for Hyper-V 6.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

Alarm table

The Alarms List view shows all alarms fired in your Hyper-V® environment. For each alarm entry, it shows its severity, the time it was fired, the rule name that triggered the alarm, and the alarm message.

This view appears on the Hyper-V Alarms dashboard, just below the Alarm overview.

Figure 256. Alarms List view

Alarm Message. An explanation about why the alarm occurred.
Object indicator. Indicates if the alarm is related to a cluster , server , or virtual machine .
Rule Name. The name of the rule that triggered the alarm.
Severity. Indicates the alarm severity: Warning, Critical, or Fatal.
Time. The time at which the alarm was generated.

Drill down on:

Alarm Message, Object indicator, Rule Name, or Time. For server and virtual machine objects, the Select Drilldown dwell appears.
Figure 257. Select Drilldown dwell
From here, selecting Explorer shows the selected server or virtual machine in the Hyper-V Explorer, with the Hyper-V Explorer Summary tab open. Selecting Quick View shows the selected server or virtual machine in the Server Summary view or Virtual Machine Summary view.
Severity. Displays the Alarm Created dialog box, showing additional information about the alarm. For more information about alarms in Foglight Evolve Cloud™, see the Foglight Evolve Cloud User Help.
Figure 258. Alarm Created dialog box

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 Environment.
Figure 259. Administration tab
5
On the Administration tab, click Set Alarm Sensitivity Level.
The Set Alarm Sensitivity Level dialog box appears.
Figure 260. Set Alarm Sensitivity Level dialog box
6
In the Set Alarm Sensitivity Level dialog box, select the desired sensitivity level: Essential, Normal, or Tuning.
7
Click Save.
The Set Alarm Sensitivity Level dialog box closes.

Finding alarms using the action panel

The action panel gives you quick access to a number of useful actions and tasks. It provides additional actions provided with Hyper-V Monitoring in Foglight® Evolve Cloud when you are viewing the Hyper-V Explorer dashboard.

The action panel operates like a drawer. Its default position is closed. To open the action panel, click the arrow at the far right of the Hyper-V Monitoring in Foglight Evolve Cloudbrowser interface.

3
On the navigation panel, under Dashboards, choose Hyper-V > Hyper-V Explorer.
4
On the action panel, on the General tab, under Actions, click View Virtual Infrastructure Alarms.
The Hyper-V Alarms dashboard appears in the display area.

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

 

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación