Monitoring
System monitoring keeps an SAP system healthy by watching its work processes, memory, database, jobs, updates and errors, so problems are caught early. SAP provides a rich set of monitoring transactions, and this is daily bread for Basis administrators.
For a system that runs the business, catching a filling file system, a stuck update, or a queue of failing jobs early prevents outages.
- Healthy operation means work processes not all busy or stuck, no update failures (SM13), no flood of dumps (ST22), the system log…
- Beyond manual checks, SAP Solution Manager / Cloud ALM and alerting automate monitoring, raising alerts on thresholds so…
- SM50 / SM66: work processes on the local/whole system.
- Watch out: Only reacting after users complain.
The core monitoring transactions
- SM50 / SM66: work processes on the local/whole system.
- SM37: background jobs.
- SM13: update records (failed updates).
- SM21: the system log.
- ST22: ABAP runtime errors (dumps).
- ST02 / ST04 / ST06: buffers, database, OS.
What to watch
Healthy operation means work processes not all busy or stuck, no update failures (SM13), no flood of dumps (ST22), the system log (SM21) free of serious errors, jobs completing on time, and database/OS resources within limits. Deviations are early warnings of trouble.
Proactive monitoring
Beyond manual checks, SAP Solution Manager / Cloud ALM and alerting automate monitoring, raising alerts on thresholds so administrators act before users are affected. Proactive monitoring is the mark of a well-run system.
Why it matters
For a system that runs the business, catching a filling file system, a stuck update, or a queue of failing jobs early prevents outages. Monitoring is how administrators stay ahead of problems.
Common pitfalls
- Only reacting after users complain.
- Ignoring update failures (SM13) or dumps (ST22).
- No automated alerting, missing off-hours issues.