Incidents raised by AIOps should raise or lower priority if later Alerts meet the requirements to do so

See this idea on ideas.ibm.com

Operations teams expect that the priority of Incidents generated and reported by AIOps to reflect the current priority of the underlying issue, not the priority of the issue at the time of Incident creation.

Currently, an Incident is raised at a specific priority determined by the criteria specified at the time of creation. If later Alerts are grouped into the incident that would be expected to increase the priority (for example a "warning" incident regarding loss of redundancy later being grouped with an Alert indicating actual service failure), then the incident's priority should similarly be escalated.

Policy execution explicitly states "no Incident will be created if the new/changed Alert is already grouped into an Incident". This prevents the behaviour above - either by forcing creation of a newer Incident (at higher priority) or by escalating the existing Incident when the later Alert comes in.

Idea priority

Medium

Post comment

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use

Incidents raised by AIOps should raise or lower priority if later Alerts meet the requirements to do so

Please enter your email address

RELATED IDEAS

Incidents raised by AIOps should raise or lower priority if later Alerts meet the requirements to do so