Exception Monitoring
  • 01 Jan 2023
  • 3 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Exception Monitoring

  • Dark
    Light
  • PDF

Introduction

Business Activity Monitoring (BAM) allows users to log exceptions and exception codes in the stages of the business transaction. When the user selects the transaction instance, the logged exceptions will be displayed.

Users will also receive immediate alerts whenever an exception is logged in any of the transaction stages.

Serverless360 Business Activity Monitoring (BAM) Monitor provides an Exception Monitoring feature allowing users to receive Exception alerts.

Exception Monitoring

The Send alerts on exceptions in transactions checkbox determine the status of the Exception monitor.

Exception monitoring in Business Activity Monitoring (BAM) requires the following options to be configured before proceeding with monitoring:

Exception monitoring.png

Max number of Alerts

  • Users can determine the maximum number of alerts received within the specified period in the Max number of alerts field.

  • The alert value should range between 1 and 100000.

Duration

  • The Duration field allows the user to specify how frequently the maximum number of alerts is reset to 0.

  • With the help of the Duration field, the user can configure how often the maximum number of alerts is reset back to 0.

  • For example, if a user has a Max number of alerts set to 3 and Duration set to 10 minutes, Serverless360 will only send three alerts within 10 minutes.

Per transaction

  • This option restricts alerts globally at the Transaction level rather than the Business Process level.

  • If this option is enabled, the maximum alert count will be applied to all transactions in a business process.

  • As a result, if there are two transactions, and one of them has already reached the maximum alert count, the other will continue to send alerts until it reaches the maximum alert count.

Per exception code

  • If the user selects this option, the exception code will be used to filter the maximum number of alerts.

  • For example, the user may receive up to 3 alerts within 10 minutes period for each exception type. Thus, if 2 exception codes are logged, the total number of alerts is 6.

Modes of alert configuration

Exception monitor offers two different modes of alert configuration:

  • Basic alert configuration
  • Advanced alert configuration

Basic alert configuration

This alert configuration mode allows users to send alerts to the configured notification channels and email address(es), regardless of the exception code or message, within the maximum number of alerts and rules evaluation frequency.

Resolution Notes

  • A resolution note is a brief description provided by the user of any rule violation for which the user defines the appropriate action to be taken, or a customized description. The provided note will be displayed along with the corresponding alert notification in the configured channels.

  • The resolution note can be provided at global level that applies to any exception code (or) message rule violation for Exception Monitoring.

Basic alert configuration.png

Advanced alert configuration

This alert configuration mode allows users to enable monitoring for specified exceptions and notification channels configured for each exception individually.

Consider the following scenario: two teams handle the overall business process management of a business orchestration. The account owner wishes to send a specific exception code alert(Say, 402 error) to one team in priority while alerts for any other exception code or message that doesn't match the provided value sent to another team.

Advanced alert configuration.png

In the given scenario, one team will receive alerts to the configured channels when any 402 error exception occurs, whereas the other team will receive alerts whenever an exception other than 402 error occurs.

Resolution Notes

  • A resolution note is a brief description provided by the user for any rule violation.

  • The resolution note can be specified individually for each exception code and message rule violation that is configured by the user for Exception Monitoring.

Resolution note for specified exception monitoring.png

The image shown below depicts an exception alert received via email:

Exception alert.png


Was this article helpful?

What's Next