Lesson 5 of 6
Alerting, intelligent event processing and Focused Run
9 min
Listen to this lesson
Every monitoring app in SAP Cloud ALM produces events. What happens next is decided in one place: Intelligent Event Processing. It turns events into alerts, emails, chat messages, tickets or automated operation flows. Getting this layer right is the difference between a run team that reacts in minutes and one that reads an inbox of 900 unread notifications.
Event actions
| Action | One-time setup | Use at Contoso |
|---|---|---|
| Create Alert | None; enable in the monitoring app's configuration | All critical interface, job and KPI events |
| Send Email To | Add recipients in Notification Management | On-call addresses for Theo's and Sam's teams |
| Start Operation Flow | Register operations automation engines and operation flows | Restart a known-safe job; collect diagnostics |
| Send Chat Notification | Integrate the external chat system | Team channel for integration alerts |
| Create Ticket | Integrate the external ticket system | Incidents for business-critical failures |
| Store Event Payload | Payload kept 24 hours in the event data store | Analysis by the on-call engineer |
Event actions in Intelligent Event Processing, from SAP's setup page.
Designing alert routing
- One owner per alert. A shared mailbox is nobody's mailbox.
- Severity decides the channel. Tickets and on-call email for business-critical; chat for awareness; alert inbox only for review.
- Group by business service. The owner of "Great Lakes EDI order to cash" sees its interface, job and KPI alerts together.
- Automate only safe reactions. An operation flow may restart an idempotent job or collect logs; it should not reprocess financial postings without a person.
- Use maintenance windows. During release imports, put the business service in maintenance so expected disruption does not page anyone, and end the window as soon as verification starts.
| Severity (Contoso) | Example | Channel | Response time |
|---|---|---|---|
| 1, business stopped | No Great Lakes orders posting; billing job aborted | Ticket plus on-call email | 30 minutes, around the clock |
| 2, business degraded | MRP runtime over threshold; deliveries without goods issue above range | On-call email and team chat | Next business hour |
| 3, needs attention | Single IDoc error for a minor partner | Alert inbox and chat | Same business day |
| 4, information | Warnings in application logs | Alert inbox, weekly review | Weekly |
Illustrative course data: Contoso's severity and channel matrix for operations alerts.
What stays in SAP Focused Run?
SAP Focused Run is SAP's on-premise operations platform for large and complex landscapes, typically used by very large customers and service providers. SAP states that its maintenance conditions are independent of Solution Manager's, so it is not part of the 2027 problem. SAP's transition guidance treats SAP Cloud ALM as the target for operations and describes adding Focused Run capabilities, for example full-featured system monitoring, integration monitoring and synthetic user monitoring, where a landscape needs more than SAP Cloud ALM offers. Contoso's questions are the ones every run team should ask.
- Do you already run Focused Run with deep custom monitoring that SAP Cloud ALM does not yet cover?Yes → keep those scenarios in Focused Run; move the rest · No → next question
- Must monitoring data stay on premise for regulatory or contractual reasons?Yes → evaluate Focused Run for those systems · No → next question
- Are you a service provider or do you run hundreds of systems with full-featured system monitoring needs?Yes → evaluate Focused Run alongside SAP Cloud ALM · No → SAP Cloud ALM only
Contoso runs a handful of production systems and services, has no Focused Run today, and has no data-residency constraint on monitoring data. Its decision, recorded by Sam and approved by Grace, is SAP Cloud ALM only, with a review if the planned Mexican acquisition adds systems with different requirements. Large customers that already run Focused Run often keep it for system monitoring and move integration, job and business process monitoring to SAP Cloud ALM; verify the current capabilities of both before deciding.
What would you do?
A consultant proposes buying SAP Focused Run "because Solution Manager monitoring ends in 2027 and Cloud ALM is too basic". Contoso has a handful of production systems and services and no on-premise data requirement. What should Sam recommend?
- Intelligent Event Processing routes events to alerts, emails, chat, tickets or operation flows.
- One owner per alert, severity-based channels, and only safe automated reactions.
- Focused Run has independent maintenance and suits large, complex or on-premise-bound landscapes.
- Decide on Focused Run from specific gaps, not from general impressions.
Check your understanding · not graded
Lesson check
1. Where are email recipients for event actions maintained?
2. How long is an event payload stored?
3. Which reaction is safest to automate?
4. What did SAP state about Focused Run maintenance?