Two state monitor with 'Error' critical state used particularly for reflecting state of Custom User Policies which have Database as Facet and one of the predefined error categories as Policy Category.
This monitor checks the evaluation result of policy in the SQL server instance. The monitor is healthy if the policy was evaluated successfully. Otherwise it is unhealthy.
To diagnose this issue, contact the database administrator or the policy owner with the policy name. The policy owner can determine the root cause of the policy execution evaluation that resulted in an unhealthy state of the monitor.
Target | Microsoft.SQLServer.2012.DatabaseErrorUserPolicy |
Parent Monitor | System.Health.AvailabilityState |
Category | AvailabilityHealth |
Enabled | True |
Alert Generate | False |
Alert Auto Resolve | True |
Monitor Type | Microsoft.SQLServer.2012.TwoStatePolicyMonitorType |
Remotable | True |
Accessibility | Public |
RunAs | Default |
<UnitMonitor ID="Microsoft.SQLServer.2012.DBErrorUserPolicyStateMonitor" TypeID="Microsoft.SQLServer.2012.TwoStatePolicyMonitorType" Accessibility="Public" Enabled="true" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Target="SQL2012Core!Microsoft.SQLServer.2012.DatabaseErrorUserPolicy" Priority="Normal">
<Category>AvailabilityHealth</Category>
<OperationalStates>
<OperationalState ID="Success" MonitorTypeStateID="HealthState" HealthState="Success"/>
<OperationalState ID="Critical" MonitorTypeStateID="ErrorState" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ConnectionString>$Target/Host/Host/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ConnectionString$</ConnectionString>
<PolicyName>$Target/Host/Property[Type="SQL!Microsoft.SQLServer.Database"]/DatabaseName$.$Target/Property[Type="SQL2012Core!Microsoft.SQLServer.2012.Policy"]/PolicyName$</PolicyName>
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
<TimeoutSeconds>300</TimeoutSeconds>
</Configuration>
</UnitMonitor>