Monitoring and alarms

Regular and automated monitoring of all processes, including appropriate alerts in the event of problems, is essential to ensure that applications are always supplied with up-to-date data.

With the help of ADIB, you can monitor all your processes in detail and trigger very specific alerts

Monitoring can be defined in detail for each job
- In which case should an alert be triggered : only in the event of a problem during execution – or always at startup (the latter could be useful in the case of recreation or troubleshooting)
- For which instance should the alarm be triggered
- Who should be alerted and how

Access and overview

Monitoring is configured via the job mask using the ‘Notification Settings’ button.

cest_notification-1 \Image 7: Access to the ‘Monitoring and Alarms’ function

The following elements are displayed on the mask that opens

List of configured monitoring
- The meaning of the columns in the table (status, job, instance is explained in the context of the new creation)
Create a new monitoring/alerting by clicking on the corresponding button

cest_notification-2 \Image 8: List of current monitoring/alerts

Creating a monitoring/alert

Click on the ‘AddRule’ button to create a new monitoring. A mask opens in which you can enter the following information:

(1) Status: Activate/deactivate the alert
(2) Instance: Select the instance for which the alert is defined
(3) Job: Select the job(s) to be monitored
(4) Channel: Medium through which the alert is sent (currently: email and Discord)
(5) Email Template: Template for the information to be sent (e.g. the content of the alert email)
(6) Event Trigger: What triggers the alert
- Failure: Alert if the job fails and aborts
- Partial failure: Alert if the job encounters an error that does not lead to an abort
- Progress: Alert when the job starts
- Success: Alert when the job has been successfully executed
(7) Email Address: Email address or Discord channel to which the alert is to be sent.

cest_notification-3 \Image 9: Creating a new alert

Changing/deleting a monitoring/alert

If you want to change an existing monitoring, click on the ‘Edit’ button in the list of monitors. This opens a window where you can see the current settings and change them.

If you no longer need a monitor, you have two options

Change the monitoring: You deactivate the monitoring
You delete the monitoring by clicking on the ‘Delete’ button in the list of monitoring tasks.

cest_notification-4 \Image 10: Changing an existing alert

The following figure shows an example of an alert triggered by ADIB. In this case, ‘eMail’ was set as the transmission method.

NOTE: You can freely define the mail text. TODO Daniel: is it possible for the user to change the mail template?

cest_notification-5 \Image 11: Example of an alert mail