Anomalies Detected in the Number of Messages Processed Event

Configure the settings for Anomalies Detected in the Number of Messages Processed event to detect anomalies in the message processing count. Define the calculation parameters, such as frequency and start time, and specify thresholds for warning and critical statuses. Use this event to monitor and manage message-processing anomalies across your landscape.

The Anomalies Detected in the Number of Messages Processed event lets you set up events when there are anomalies in message processing numbers in your landscape. This event allows you to specify warning and critical limits for maximum and minimum message processing scenarios. Use this to identify instances when the managed component processes abnormally high or low messages in a given period.

There are two sections to this configuration:

Calculation Parameters

In this section, you can specify the calculation interval and the calculation start time.

  • Calculation start time - This time is not an absolute time but an indicative time when the calculation should begin.

    For instance, if the calculation start time is set to 10.00 a.m. and the calculation interval is 60 minutes: then, the event will be calculated at every 60 minutes from 10.00 a.m.

  • Calculation frequency in minutes - This frequency is defined in minutes.

    For instance, if you set the interval to 120, then the system will calculate the event every 120 minutes.

If no start time is set, then the event calculation starts at the next event calculation process.

Message Count

In this section, specify the thresholds for this event. You can define the limits for warning and critical statuses for both minimum and maximum scenarios. There are three options that you can specify:

  • Upper Threshold - In the upper threshold, you specify the maximum number of messages for warning and critical statuses. Use this to configure the values for abnormally high number of messages in the service or system.

  • Lower Threshold - In the lower threshold, you specify the minimum number of messages for warning and critical status. Use this to configure the values for abnormally low number of messages in the service or system.

  • Upper and Lower Thresholds - By choosing this option, you can set both maximum and minimum values for warning and critical status. Use this to configure both abnormally low and high number of messages in the service or system in one setting.

AI Recommended Thresholds

You can get threshold recommendations from the app, which uses machine learning to analyze historical data of message count trends and suggest thresholds. This removes the need to estimate thresholds and provides suggestions based on previous records.

Open this video in a new window

To get recommendations:

  • Choose Recommend on the top right of the threshold values.

  • On the AI Recommended Thresholds screen, you can view historical data in chart format and the recommended values.

  • The recommended values are displayed on the left. You can change the threshold types using the Conditions dropdown. On the right, you can see the trend chart.

  • Choose Apply Recommendation to set the thresholds to the recommended values.

The recommended values are highlighted in blue. You can choose to change the threshold values, if required. And, If you have changed the values and want to re-apply the last recommended ones, choose Set to Last Recommended.

Additional Information

For more information, check out the blog post on SAP CommunityInformation published on SAP site.