search

hmscott4 / AlertManagement

Manage SCOM Alerts
2 stars 3 forks source link

Assignment Exceptions by Management Pack can't be configured #58

Closed hmscott4 closed 3 years ago

hmscott4 commented 3 years ago

This should be a valid configuration (according to the code in escalate-alert.ps1)

    <exception ID="3" Name="EfgSQL" Owner="EFG DBA Team" enabled="true">
      <ManagementPack Name="Microsoft.SQLServer.Windows.Monitoring">
        <AlertProperty>MonitoringObjectName</AlertProperty>
        <AlertPropertyMatches>efg\.lcl</AlertPropertyMatches>
      </ManagementPack>
    </exception>

However, this configuration raises the following alert: ConfigFile => \abcd\home\Public\OperationsManager\Config\AlertManagement\assign.alert.config AssignedResolutionStateName => Assigned UnassignedResolutionStateName => Assigned DefaultOwner => Unassigned DebugLogging => true The element 'ManagementPack' cannot contain child element 'AlertProperty' because the parent element's content model is text only.

hmscott4 commented 3 years ago

The goal is to allow for exceptions by alert properties for selected Management Packs. For example, there might be a group of Windows Servers in a separate domain/network that are supported by a different Windows team. Ideally, I would like to be able to fit a number of management packs under one owner, but tied to an AlertProperty (like MonitoringObjectName) that's different.

hmscott4 commented 3 years ago

Fixed.