Configuring an alarm: example 2

With the available alarms, we can configure an instance that will notify all ingestion jobs finished successfully, in the area ‘ObjectName Area’. This is for routine purposes, so a daily notification or a notification for as many as 25 jobs will suffice.

There is the preparameterized and easy to use alarm Ingestion job finished successfully, so we make good use of it.

The parameters to configure are:

1. General:

   1. Criticality = Normal.

   2. Importance = Normal.

   3. Check period: every hour. We want a daily notification, but by checking every hour we allow for several notifications in case of many finished ingestion jobs.

   4. User comment: something along the lines of ‘Ingestion jobs finished successfully in area ‘ObjectName Area’’.

2. Alarm (these parameters are specific of this alarm):

   1. Achieved state: we can see it is fixed to FinishedOK. As it is fixed, we know it is only for information purposes, and we can forget about setting it.

   2. Preservation area. We select the area ‘ObjectName Area’.

   3. Minimum size. We do not use it, so it is not taken into consideration.

3. Notification:

   1. Message building rule. As the text from several jobs may be added, we set it to Add the notification text under new execution.

   2. Maximum number of messages without sending e-mail. We set it to 25, meaning that if 25 or more messages are generated before the maximum time without sending e-mail (which will be configured to 1 day), the notification will be sent without the wait.

   3. Maximum time without sending e-mail. 1 day, that is the periodicity with which we want -in principle- to receive the notification about these jobs.

   4. Receiver (user). Whichever we want.

   5. Receiver (group). Whichever we want; a preservation administrator being most suitable, as this reports on usual preservation activities in an area.

   6. Can deactivate notification. Checked, as it makes no sense for these individual notifications to be persistent.

   7. E-mail sending deactivates notifications. Checked, as this alarm is mostly for routine information purposes, and it should not call our attention when accessing the notifications panel.