How does a typical SAP customer deal with technical Basis operations?
SAP operations is normally managed by:
- in-house teams, or
- outsourced to an application service provider (ASP), managed service provider (MSP) sometimes also referred to as application management services (AMS), or
- a hybrid support model
SAP monitoring and incident management are big parts of SAP support and regardless who is responsible for it, needs to be performed. Let's revisit the top areas which needs constant monitoring. In the next few weeks, we'll share our experiences around the top SAP Basis Monitoring areas. We will use this main page as an anchor to the various topics below, relisted from the blog BASIS or BASICS and will be added to as time goes on. The first topic will be included in this post.
Monitoring Areas (in no particular order of importance)
- Database Lock waits & Deadlocks
- Spool Management
- Database Allocation & Utilization
- Backup / Restore Information
- Scheduled DB jobs
- DB Performance Analysis
- Application Server Resource Utilization: Processes, Dispatcher Queues
- Update Records
- tRFC & qRFC Queues
- System Logs (App, DB, OS)
- Background (Batch) Jobs
- Application Locks and Enqueue
- ABAP Dump Analysis
- Workload: Application Performance Analysis
- O/S Monitor
|Database Lockwaits and Deadlock||SAP||IT-Conductor|
Any of the monitors above can have an exception (known in IT-Conductor as Threshold Overrides or for an Alert matching a filter called Object Template) which triggers an Alert and optional Notification. Furthermore, a Recovery Action, such as a SQL query or MiniCheck report triggered when the exception is caught. This can be used for further analysis but giving historical context along with all the metrics and alerts monitored above.