-
Request for existing cases, user IDs, Portal navigation support and more
Intelligent Event Processing
Intelligent Event Processing in SAP Cloud ALM processes events from different sources in a unified and efficient way. It is the central intelligence for efficient event routing between internal and external producers and consumers. It provides the following features and benefits:
- Unified event processing based on rules for automatically as well as manually triggered events
- Enables centralized event handling via event log viewer as well as decentral alert handling via embedded alert inbox
- Foundation for intelligent correlation of events e.g., correlation of manually generated notifications with automatically generated alerts
The different SAP Cloud ALM applications trigger event situations or stateless events in Intelligent Event Processing. Intelligent Event Processing triggers then different event actions.
Event Situations
Event situations are opened, optionally updated and closed after a certain amount of time. Examples for event situations are the following:
- Health Monitoring monitors the availability of a HANA Cloud Database.
As soon as it detects that the database is unavailable it triggers a new event situation for the event "Database Accessibility" in Intelligent Event Processing.
Intelligent Event Processing triggers the event actions per corresponding event processing rules.
Health Monitoring checks the database status frequently and provides updates for the event situation.
As soon as it detects that the database is available again it closes the event situation in Intelligent Event Processing. - Integration Monitoring detects 10 new erroneous AIF messages and triggers a new event situation for the event "Erroneous AIF Messages Detected(Grouped)".
Per event processing rules, Intelligent event processing opens a corresponding alert. After some time, Integration Monitoring detects two additional AIF messages in error status and updates the event situation.
An user confirms the alert. This closes implicitly the event situation. But the user forgot to fix the 12 erroneous AIF messages.
After some time Integration Monitoring detects the 12 AIF messages in error state again and triggers a new event situation for the event "Erroneous AIF Messages Detected(Grouped)".
Stateless Events
A special case are event situations, which are opened and closed at the same time, as due to the nature of the event future updates and automatic closure is not possible. They are used to alert for example the occurrence of a specific message in application logs.
Event Actions
IEP can trigger the following event actions:
- Create Alert - creates an alert in the alert inbox of the respective monitoring application
- Send E mail - sends an E-mail notification to defined recipients
- Create Ticket - Creates or updates a ticket in an external ITSM system
- Start operation flow trigger an operation flow in an external automation engine (SAP Automation Pilot, SAP intelligent RPA or SAP Automation Pilot).
- Send Chat Message - Send a chat message to an external chat system
The following event actions are supported per use case:
Event Action | Business Process Monitoring | Integration & Exception Monitoring | Synthetic User Monitoring | Job & Automation Monitoring | Health Monitoring | Real User Monitoring | Business Service Management |
---|---|---|---|---|---|---|---|
Create Alert | Yes | Yes | Yes | Yes | Yes | Yes | No |
Send Email | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Create Ticket | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Start Operation Flow | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Send Chat Message | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Configuration and Security Analysis do not trigger events at the moment.
Event Processing Rules
The assignment of event actions to events in Intelligent Event Processing happens internally via Event Processing Rules. In most cases those rules are automatically created and managed by defining the event settings with the assigned Event Actions directly in the respective application. The manual maintenance of Event Processing Rules in Intelligent Event Processing is only needed in some limited scenarios.