Advanced Troubleshooting Techniques in Solution Manager for Technical Monitoring

  • by Jereme Swoboda, SAP Solution Manager and NetWeaver Consultant, NIMBL
  • November 9, 2015
Solution Manager 7.1 allows you to monitor almost anything in an SAP landscape. When an alert fails to generate an email alert, what tools do you have to find the root cause of an error? Review the tools that are provided by SAP to analyze the back-end processes of Technical Monitoring. See how to manage and use the monitoring infrastructure to its fullest potential.
Learning Objectives

Reading this article you will learn how to:

  • Prevent issues in the first place
  • Use the troubleshooting tools that are specifically designed for Technical Monitoring
  • Better administer Technical Monitoring through acquiring advanced knowledge
Key Concept
Technical Monitoring is designed to provide alerts on the critical components of an SAP landscape, allowing you to respond quickly to urgent situations that need immediate attention.

As time goes on, Solution Manager only becomes more advanced. It is increasingly designed to monitor more applications in various ways. This inherently means that issues can be more difficult to resolve, especially if you are not managing Solution Manager on a daily basis. This article is meant to assist in the process of troubleshooting issues with Technical Monitoring.

Technical Monitoring is an extremely dense tool provided by SAP’s Solution Manager 7.1. Beyond the standard operations that most people are accustomed to using, it allows you to monitor almost anything. As of Solution Manager 7.1 Support Package 12 (SP12), Technical Monitoring is divided into five specific types of monitoring:

  1. System monitoring
  2. Solution Manager self-monitoring
  3. End-user experience monitoring
  4. Interface and Process Orchestration (PO) monitoring
  5. Job and SAP Business Warehouse (SAP BW) monitoring

First and foremost I go over the basics to prevent issues from coming up in the first place. Then I describe the Monitoring and Alerting Infrastructure (MAI) analysis tools, the Data Provider Check, and the Metric Troubleshoot. You will see how the Extractor/Alerting Framework, diagnostics agent administration, E2e-MAI Servlet, and the Alerting Directory Browser tools allow you to find the root cause of an issue. These tools are available to troubleshoot the primary components that are used by Solution Manager to collect data on SAP systems.

Jereme Swoboda

Jereme Swoboda is an experienced SAP Solution Manager and NetWeaver consultant focusing on proactive technical monitoring of SAP and non-SAP systems, supporting critical business processes. He has tremendous experience pairing real-world scenarios with Solution Manager’s Technical Monitoring capabilities. He is an expert at collecting requirements, creating a monitoring strategy, and then putting that strategy to work for SAP customers. Jereme has had the opportunity to work on a variety of platforms for companies large and small integrating Solution Manager 7.1.

See more by this author


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.