Rule detecting that a given HealthService cannot process configuration that it received.. These configuration may have been part of a recently updated Management Pack.
This rule is used internally by OpsMgr. Overrides to this rule will cause behavior that may not be what you expect.
This section is not applicable to this rule.
There is no resolution to perform for this rule since it does not generate state or alerts.
Target | Microsoft.SystemCenter.HealthServiceWatchersGroup |
Category | System |
Enabled | True |
Alert Generate | False |
Remotable | True |
Comment | HealthService config processing |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.SystemCenter.HealthServiceWatcher.DataSource.Composite | Default |
WriteAction | WriteAction | Microsoft.SystemCenter.HealthServiceWatcher.SetConfigProcessedStateAction.Error | Default |
<Rule ID="Microsoft.SystemCenter.HealthService.ConfigProcessed.Error" Comment="HealthService config processing" Enabled="true" Target="SCLibrary!Microsoft.SystemCenter.HealthServiceWatchersGroup" ConfirmDelivery="true" Remotable="true" Priority="High" DiscardLevel="100">
<Category>System</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.SystemCenter.HealthServiceWatcher.DataSource.Composite"/>
</DataSources>
<WriteActions>
<WriteAction ID="WriteAction" TypeID="Microsoft.SystemCenter.HealthServiceWatcher.SetConfigProcessedStateAction.Error"/>
</WriteActions>
</Rule>