ACE stands for Alert Calculation Engine which is also known as Event Calculation Engine (ECE). The Event Calculation Engine receives metric values from the Data Provider Connector, calculates the current status and the events from the metric values.
1- The Event Calculation Engine receives metric values from the Data Provider Connector.
2- The Event Calculation Engine calculates the current status based on central configuration and the rating for metrics based on the metric thresholds.
3- It writes the current status of metrics and events to the Event + Metric store
4- In addition provides the events to the Alert Consumer Connector.
The job in charge of this is "SAP_ALERT_CALCULATION_ENGINE" runs once a minute. The Report name is ACE_CALCULATION_CONTROLLER. The job evaluates the reported metrics and updates the status information of the monitored components for the monitoring and alerting infrastructure.
Optimize Performance of Event Calculation
GENERAL TROUBLESHOOTING
For general Issues with the MAI Infrastructure, the most important tool is the MAI Selfmonitoring. To start it, proceed as follows:
- Start transaction sm_workcenter and select tab Solution Manager Administration.
- Select Selfmonitoring.
You should perform the following checks
Check: Is the Event Calculation Engine Job running and performing?
You can find the corresponding check in Selfmonitoring under the component Event Calculation Engine - Status of the Alert Calculation Job.
The Event Calculation Engine job runs every minute under the name SAP_ALERT_CALCULATION_ENGINE (if not changed manually), which calls the report ACE_CALCULATION_CONTROLLER. Self-monitoring checks whether the job had been started in the last minutes. If it has not run within the last two minutes, the status is red.
If the status is not green, proceed as follows, depending on the status of the job:
- The job is not scheduled: Schedule the Event Calculation Engine job in the SAP Solution Manager configuration (transaction SOLMAN_SETUP). Configure the scenario SolMan Self-Monitoring in Technical Monitoring, and go to Configure Infrastructure --> Configure Automatically, which contains the activity Create Alert Calculation Job. Switch to change mode, select this activity and perform it, with Execute Selected.
- The job is delayed or did not finish: The job is scheduled, but ran late, because there was insufficient background processing capacity to run the scheduled jobs on time. Check the job in the Job Overview (transaction SM37), and provide more background processing resources, if necessary, e.g. by increasing the number of background processes.
Check: Are there error messages for the Alert Calculation Engine?
You can find the corresponding check in Selfmonitoring under the component Event Calculation Engine - Errors raised during Event Calculation.
Tf the status is not green, analyze the error messages in the Application Log, as follows:
- Start the transaction SLG1, and enter the object E2E_ALERTING and subobject ENGINE.
- 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.
- The messages of the job run are displayed at the bottom of the window. Display the error message long text.
- A solution is usually proposed, as well as the cause of the error. Proceed according to the long text.
Check: Is the Job for the Data Provider Connector running?
A prerequisite for the Data Provider Connector is the corresponding Job. The job name is EFWK RESOURCE MANAGER. Check in transaction SM37 that the job is scheduled. If not, proceed as follows:
- Schedule the job in the SAP Solution Manager configuration (transaction SOLMAN_SETUP).
- Go to step Basic Configuration -> Configure Automatically. The job is scheduled in the automatic activity Schedule Sol. Manager Background Jobs.
Check: Is the Data Provider Connector running without errors?
You can find the corresponding check in Selfmonitoring under the component Data Provider Connector and Data Provider Connector - Errors raised during Data Provider Connector configuration. The Data Provider Connector is responsible for transferring monitoring data into the End-to-End Monitoring and Alerting Infrastructure.
If the status is not green, proceed as follows:
- If there are Alerts for Data Provider Connector in the Alert Inbox, open the inbox and see the description of the alert text.
- If the status of Errors raised during Data Provider Connector configuration is not green, start the Application Log (transaction SLG1).
- Enter E2E_ALERTING in the Object field.
- Enter DPC_SETUP or DCC (Diagnostics Control Center) in the Subobject field.
- Display the logs. Select an error message by double-click, to display its long text, and proceed according to the long text.
Main issues: