Want to understand the Events and Alerts and Incident relation with bi-directional flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-02-2023 11:56 PM
We are implementing a connector which will create events for any device failures and multiple events will be created one or more alerts and the alerts may create an incident .
Once the alerts and incidents are being created from multiple and similar events , how can the events know about the incident status if it is closed.
Use case 1:
===========
Our Existing connector <-- > SNOW Incident :
Our connector will create an incident directly in ServiceNow and it will get the incident details back along with incident number and it's id.
When ever the the issue at our end is solved the connector update the incident to closed state and also clear the alarm from the connector.
Use case 2:
=========
In this scenario we want to replace the direct incident creation form our connector for each issue , we want to create events, if the issues are similar using some rules in SNOW we'll create one or more alerts and based on the alert rules we will create one or more incidents.
Here the relation ship is :
Issue1 -- event1 --alet1
Issue2 -- event2 --alet1
Issue3 -- event3 --alet1
Issue4 -- event4 --alet1
Issue5-- event5 --alet1
Here of we observe multiple issues are creating multiple events and as those are similar we are creating it to only 1 alert . If some changes happened to the alert say it is closed in SNOW how the alerts are being informed back. What is the relation ship for the same?
Thanks,
Balamurali
- Labels:
-
Architect