Show TOC

Process documentationOptimize Performance of Event Calculation

 

The core of E2E Monitoring and Alerting Infrastructure (MAI) is the Event Calculation Engine, which performs the most important MAI calculations. The Event Calculation Engine runs every minute by default, in the job SAP_ALERT_CALCULATION_ENGINE, which runs the report ACE_CALCULATION_CONTROLLER. Schedule the job in SAP Solution Manager configuration (transaction SOLMAN_SETUP), with the following steps: Start of the navigation path Basis Configuration Next navigation step Automatic Configuration Next navigation step Create Alert Calculation Job End of the navigation path.

The job has the following tasks as well as calculating events:

  • Load metrics from the metric store

  • Notifications for reporting about changes to metric work modes

  • Calculation of status and alerts by the Event Calculation Engine

  • Calculate metric aggregates

  • Calculate alert information for the Alert Consumer Connector

  • Pass information about long-term storage to the Business Warehouse

  • Other calculations

You can display the run time of the job and these tasks. Proceed as follows:

  1. Go to the Self-Monitoring overview view (Self-Monitoring Overview View).

  2. Go to the component Start of the navigation path Event Calculation Engine Next navigation step Total Run Time of the Event Calculation Engine End of the navigation path.

  3. Start the tool with ECE Performance History.

  4. In the group box Change Period, you can specify the time period for which to display the run time of these tasks.

  5. Expand the lower group box Performance Run Time, to display the job run times.

Although the job runs every minute, a run time of more than a minute causes no problems (as long as there are enough free background work processes), because several instances of the job can run at the same time. Parallel processing is only limited by the fact that when the metrics of a category are being processed, this category is locked to other job instances. There are four categories - Availability, Performance, Exceptions and Configuration. So up to four job instances can run in parallel.

If the run time of the job is still too long, check the following:

Process

Does the job have runtime errors?

Error messages for this job are not buffered, they are written directly to the database, which costs performance, so check for errors if you experience performance problems. If errors occur, they are output in the Self-Monitoring overview view in the component Start of the navigation path Event Calculation Engine Next navigation step Event Calculation Errors End of the navigation path.

Analyze the errors as follows:

  1. Start the application log (transaction SLG1) and enter the object E2E_ALERTING and subobject ENGINE.

  2. The logs are ordered by job executions, error messages are highlighted in traffic light colors. Expand the runs in which errors occurred; and expand the rows by double-click.

  3. The messages of the job run are displayed at the bottom of the window. Display the error message long text.

  4. A solution is usually proposed, as well as the cause of the error. Proceed according to the long text.

One possible cause of errors is an incorrect or out-of-date configuration. If errors occur, repeat the configuration of the managed objects affected. Proceed as follows:

  1. Run the Monitoring and Alerting analysis tools by calling transaction MAI_TOOLS.

  2. Go to expert mode by choosing (Activate Expert Mode).

  3. In the Configuration Tools group box, choose Find Config. Problems in Logs.

  4. The entry points at which event calculation errors occurred in the last 15 minutes are shown in a new window. Choose the entries with the technical scenario T_SYS_MON (System Monitoring) consecutively, by double-click, and reconfigure these points of entry, by choosing (Execute) in the next screen.

  5. Wait for 15 minutes and run this analysis tool again to determine whether the event calculation errors still occur.

Are all managed objects relevant for Technical Monitoring?

To improve the performance of the event calculation, check whether Technical Monitoring is really relevant for all managed objects for which it is active.

You can activate and deactivate it per monitoring use case, in the Solution Manager configuration (transaction SOLMAN_SETUP). The handling depends on the monitoring use case; to remove a system from s system monitoring, proceed as follows:

  1. In SAP Solution Manager configuration, choose Start of the navigation path Technical Monitoring Next navigation step System Monitoring End of the navigation path.

  2. Go to the Define Scope step.

  3. Go to edit mode, select managed objects, and choose Remove Monitoring.

Are the Event Calculation Parallelization Settings Optimal?

You can improve the performance of the ECE by optimizing its parallelization settings. Caution: the parallelization settings affect the event calculation intimitely. The parameter values can cause significant performance and load differences,so you must observe the consequences of each change carefully.

For more information, see Event Calculation: Configuring Parallelization.