Facilitate Flexible, Automatic Alerts as Part of Your SAP System Monitoring

  • by Jim Baxter, Independent SAP Basis Consultant
  • February 27, 2012
Manager
The number of monitor tree elements is astounding in the Computing Center Management System. It often leads to an overload of alerts being triggered, so much so that operators simply ignore them, not being able to keep up with the volume of alerts triggered. Examine this issue and define a concise, important set of alerts. This way, the system only triggers alerts that are meaningful and need to be addressed, reducing the volume of alerts sent to the operators.
Key Concept
The Computing Center Management System (CCMS) allows you to assess the well-being of SAP systems. It is fast, easy to configure, reliable, and — if correctly configured — highly effective. It has saved many SAP Basis technologists from embarrassment by providing advance warning of problems in their landscape. Using centralized monitoring in transaction RZ20 in the SAP Solution Manager system is a must in any SAP environment, even if you use only the basics, such as availability monitoring.

The core of system monitoring lies in providing you with an understanding of how well your system is performing. By setting up the proper monitor tree elements (MTEs), you can be sure that the alerts in your system are acting properly. For instance, with critical batch job monitoring, when a critical job fails, an automated process is triggered that informs the responsible person. This can be either if the job fails or is successful.

In my article “Set Up Your SAP System to Monitor and Alert on Its Base Elements” I explained how to implement this framework into transaction RZ20 using SAP Solution Manager as the centralized monitoring system (CEN). In that article I followed the first five actions in this eight-step process:

  1. Understand your landscape and determine which systems require monitoring
  2. Build a spreadsheet of your base monitors and decide on the thresholds
  3. Ensure all your agents are correctly installed, updated, stable, and running
  4. Create your monitor sets based on the spreadsheet and set the permissions for them
  5. Expand on each monitor set, creating rule nodes and virtual nodes to accurately describe the monitors
  6. Create your auto-reaction methods for alerting
  7. Use alert management to allow flexibility for sending out alerts
  8. Use the Generic Request and Message Generator (GRMG) for Java monitoring

In this article, I complement step 5 in the section on MTEs and explain the last three steps after that. This article is intended for system administrators and technical managers, and requires no prerequisites beyond using an SAP Solution Manager system prior to 7.1. First, I show you a spreadsheet with the required MTEs that I mentioned in the first article.

Jim Baxter

Jim Baxter is an independent SAP Basis consultant with a wide variety of experience in SAP Solution Manager setup and functionality. He is certified in the Implementation Tool and Root Cause Analysis and has worked on Service Desk setup for SAP value-added resellers.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.