Unix Heartbeat Monitor

Microsoft.Unix.WSMan.Heartbeat.Monitor (UnitMonitor)

Unix Heartbeat Health

Knowledge Base article:

Summary

This monitor ensures that the WS-Management Daemon is running and communicating. If the state is unknown, either monitoring has not begun for this object or there are no monitors defined that monitor availability.

Causes

An unhealthy state for this monitor indicates that the WS-Management Daemon fails to produce a heartbeat.

This can happen when:

View all current alerts from this object using this link:

Alerts

Resolutions

Recoveries may be enabled to restart the agent.

In the event that the recovery is disabled or was not successful, you can navigate to the "State Change Events" tab and run the recovery from the details pane.

Element properties:

TargetMicrosoft.Unix.Computer
Parent MonitorSystem.Health.AvailabilityState
CategoryAvailabilityHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Unix.WSMan.Heartbeat.MonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Heartbeat failed
The System is not responding to heartbeats.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Unix.WSMan.Heartbeat.Monitor" Enabled="true" Accessibility="Public" Target="Microsoft.Unix.Computer" TypeID="Microsoft.Unix.WSMan.Heartbeat.MonitorType" ParentMonitorID="SystemHealth!System.Health.AvailabilityState">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Unix.WSMan.Heartbeat.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState HealthState="Success" MonitorTypeStateID="Available" ID="Available"/>
<OperationalState HealthState="Error" MonitorTypeStateID="NotAvailable" ID="NotAvailable"/>
</OperationalStates>
<Configuration>
<Interval>300</Interval>
</Configuration>
</UnitMonitor>