Show TOC

Alert MonitorLocate this document in the navigation structure


The monitoring architecture, a solution within SAP NetWeaver, centrally monitors any IT environments - from individual systems through networked NetWeaver solutions, to complex IT landscapes incorporating several hundred systems. It is provided in SAP NetWeaver and can be used immediately after installation. You can easily extend the architecture to include SAP and non-SAP components.

Alerts form a central element of monitoring. They quickly and reliably report errors - such as values exceeding or falling below a particular threshold value or that an IT component has been inactive for a defined period of time. These alerts are displayed in the Alert Monitor; this reduces the workload for the system administration, since they now only need to watch the error messages, instead of endless system data.

The Alert Monitor is therefore the central tool with which you can efficiently administer and monitor distributed SAP NetWeaver solutions or client/server systems. The Alert Monitor displays problems quickly and reliably.

Implementation Considerations

If you want to use the Alert Monitor for central monitoring (that is, you want to monitor the systems of your IT landscape from a central monitoring system), you must perform various configuration steps yourself. These are described under Configuring the Monitoring Architecture.


The Alert Monitor provides the following functions:

  • You can use the Alert Monitor to perform complete and detailed monitoring of all SAP and non-SAP systems, the host systems, and the database.

  • All errors generate alerts, which are displayed in a tree structure.

  • The alerts contain a status indicator with a color and a numerical value. Yellow means a warning, red means a problem, and the numerical value shows the severity of the reported error. In the tree structure, the most severe alerts are passed upward in the display hierarchy. If a tree node is not displaying an alert, there is also no error in the entire branch below it.

  • You can assign certain analysis and auto-reaction methods to the alerts, which contribute to faster processing of the error. If you double-click an alert, the monitoring architecture starts the assigned analysis method (such as the job administration transaction for a prematurely terminated job). An auto-reaction method, on the other hand, starts automatically as soon as the alert occurs. This includes executing operating system commands and sending an e-mail or an SMS message to the system administration.

  • The Alert Monitor contains various view in which either the current or the open (that is, the unanalyzed) problem messages are displayed. Alerts are also archived.

  • Threshold values, methods, and detailed help for many monitoring attributes and three extensive monitor sets with monitors for all aspects of system management are predefined on the basis of Best Practices in the monitoring architecture and are available in every SAP system.

  • You can adjust all settings individually, and configure your own monitors.

  • You can also use the performance data from the alert monitor for reporting within the SAP Solution Manager.

  • As of SAP NetWeaver 7.0 EhP2, the Consistency Check of the CCMS Monitoring Infrastructure is available to you. The associated transactions RZ50, RZ521, and RZ52 provide a variety of functions to check the configuration and runtime of the CCMS monitoring infrastructure, to display errors, and to correct these automatically. The checks are called from the central monitoring system (CEN) and include both the CEN itself and the monitored systems.