This monitor detects timeout for Ambari API.
This monitor detects timeout for Ambari API.
This monitor turns to Warning state if Ambari Management Pack gets a repeatable timeouts trying to connect to Ambari server. Ambari server might be overloaded.
- Check if Ambari server is overloaded
- Check for network issues which may affect connection between watcher and Ambari server
Target | Ambari.SCOM.AmbariWatcherNode | ||
Parent Monitor | System.Health.AvailabilityState | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Ambari.SCOM.RepeatedEventLogTimer2StateMonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Ambari.SCOM.TimeoutMonitor" Accessibility="Public" Enabled="true" Target="Ambari.SCOM.AmbariWatcherNode" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Ambari.SCOM.RepeatedEventLogTimer2StateMonitorType" ConfirmDelivery="true">
<Category>Custom</Category>
<AlertSettings AlertMessage="Ambari.SCOM.TimeoutMonitor.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="HealthyState" MonitorTypeStateID="TimerEventRaised" HealthState="Success"/>
<OperationalState ID="ErrorState" MonitorTypeStateID="RepeatedEventRaised" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Operations Manager</LogName>
<EventNumber>1904</EventNumber>
<TimeInterval>4500</TimeInterval>
<Count>3</Count>
</Configuration>
</UnitMonitor>