Error, Usage Site encountered Collection Cycle Error. This monitor is timed reset, you can overwrite the TimerWaitInSeconds parameter in the OM Console Override Properties dialog.
Checks for the occurrence of a Notification Unexpected Error, Event 210.
If the monitor is in Error state then the Collection Cycle encountered an unknown exception specified in the corresponding Error Event Log entry
Check the affected Site Event Log for the event 210, determine which entity and exception details were reported.
For this monitor to work correctly, it must have permission to access the Event Log. An account with the right permissions may be needed.
The following options can be configured on this monitor:
Option | Definition | Default |
Alert On State | Health state for the monitor that generates an alert. | The monitor is in a critical health state |
Alert Priority | Priority of the alert generated for this monitor. | High |
Alert Severity | Priority of the alert generated for this monitor. | Critical |
Auto-Resolve Alert | Specifies whether the alert should automatically be resolved when the monitor returns to a healthy state. | True |
Enabled | Specifies whether the monitor should run. | True |
Generates Alert | Specifies whether the monitor should generate an alert when changing to a warning or critical state. | True |
Interval | Number of seconds between times that the monitor is run. | 300 |
Target | WindowsAzurePack.UsageCollector | ||
Parent Monitor | System.Health.AvailabilityState | ||
Category | AvailabilityHealth | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | WindowsAzurePack.MonitorType.CustomSingleEventLogTimer2StateMonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default | ||
Comment | WAP Monitor Event for UsageCollector |
<UnitMonitor ID="WindowsAzurePack.Monitor.CollectionCycleError.UsageCollector" Accessibility="Public" Enabled="true" Target="WindowsAzurePack.UsageCollector" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="WindowsAzurePack.MonitorType.CustomSingleEventLogTimer2StateMonitorType" ConfirmDelivery="false" Comment="WAP Monitor Event for UsageCollector">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="WindowsAzurePack.Monitor.CollectionCycleError.Usage.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
</AlertSettings>
<OperationalStates>
<OperationalState ID="ErrorEventRaised" MonitorTypeStateID="EventRaised" HealthState="Error"/>
<OperationalState ID="TimerEventRaised" MonitorTypeStateID="TimerEventRaised" HealthState="Success"/>
</OperationalStates>
<Configuration>
<!-- Computer name for the first event. We will use a variable to get the target computer name. -->
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<!-- Name of the log containing the first event. -->
<LogName>Microsoft-WindowsAzurePack-MgmtSvc-Usage/Operational</LogName>
<!-- Expression for the first event -->
<Expression>
<And>
<!-- Expression for the first event number -->
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">210</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<!-- Expression for the first event source -->
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-WindowsAzurePack-MgmtSvc-Usage</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
<TimerWaitInSeconds>10800</TimerWaitInSeconds>
</Configuration>
</UnitMonitor>