search

hmscott4 / AlertManagement

Manage SCOM Alerts
2 stars 3 forks source link

Exceptions which need to match a specific alert Property need to be prioritized over those that do not. #39

Closed hmscott4 closed 3 years ago

hmscott4 commented 3 years ago

Alert exceptions need to be processed in a prioritized fashion (ignoring the ID number in certain circumstances).

For alert assignment exceptions, if the exception has an AlertProperty element, it needs to be processed before exceptions that do not have an AlertProperty element. This allows admins to create assignment exceptions to meet different requirements.

Examples:

    <exception ID="1" Name="Server Offline" Owner="EFG Windows Team" enabled="true">
      <Alert Name="Health Service Heartbeat Failure" >
        <AlertProperty>MonitoringObjectDisplayName</AlertProperty>
        <AlertPropertyMatches>efg\.lcl</AlertPropertyMatches>
      </Alert>
    </exception>
    <exception ID="2" Name="Server Offline" Owner="EFG Windows Team" enabled="true">
      <Alert Name="Failed to Connect to Computer" >
        <AlertProperty>MonitoringObjectDisplayName</AlertProperty>
        <AlertPropertyMatches>efg\.lcl</AlertPropertyMatches>
      </Alert>
    </exception>
    <exception ID="3" Name="Server Offline" Owner="Windows Team" enabled="true">
      <Alert Name="Health Service Heartbeat Failure" />
    </exception>
    <exception ID="4" Name="Failed to Connect to Computer" Owner="Windows Team" enabled="true">
      <Alert Name="Failed to Connect to Computer" />
    </exception>

ID 3 and 4 are used to override these alerts to the Windows Team (from the Monitoring Team). ID 1 and 2 are used to override to members of the EFG Windows Team. 1 and 2 must be processed before 3 and 4 (because 1 and 2 are more specific). They should be processed first, ignoring the sequence of ID.

hmscott4 commented 3 years ago

Fixed