If you want to be notified of alarms via email, you can configure alarm-specific notifications under Settings – Systems configuration in the Alarm configuration tab.

You configure the general settings for each alarm at the global level, which is the top-level folder in the directory tree on the left. At the system level, you can then turn the notification on or off as needed, but you cannot, for example, add other recipients.

Each alarm at global level has the following settings for email notifications:

Turn on email notifications

To receive email notifications, you must enable this option at the global level. You can enable or disable this option at the system level only if it is enabled at the global level.

Aggregation time

From the list, select the duration that ibaManagementStudio should wait after the first detected event before sending the email. All events covered by this rule occurring within this time are summarized in a single email.

Cooldown period

Set a minimum duration after sending an email during which no further emails will be sent for the same rule. New events of this type that occur during this period will not be ignored. They will be mentioned in the email sent after the cooldown period has expired.

If you disable the cooldown period, new emails will be sent immediately for any alarms that occur.

Send via email account

Select a sender account for the email notification here.

Recipients/Recipient Groups

Select the users or user groups from the user management of ibaManagementStudio who should receive the email. Users who belong to multiple selected groups will receive the email only once.

Send test email

Click this button to send a preview email to the selected recipients. This allows you to check the layout and delivery of the email.
Sending behavior with aggregation window and cooldown period

The ibaManagementStudio server checks every minute whether an alarm rule has been violated and an email should be sent. The email delivery process works as follows:

  1. Detection of a change: A new alarm for the rule has been triggered since the last email.

  2. Aggregation time: ibaManagementStudio waits for the aggregation time to elapse after a change is detected.

  3. Email delivery: Once the aggregation period has expired, ibaManagementStudio sends an email listing all changes if the alarm is still active.

    If the alarm has been canceled in the meantime, no email will be sent.

  4. Cooldown period: After an email has been sent, ibaManagementStudio waits to send any additional emails until the configured cooldown period has elapsed.

    If changes occur during this period, ibaManagementStudio sends an email after the cooldown period and the new aggregation period have elapsed.

Once the cooldown period is over, email delivery can resume following this pattern.

The next email always lists all events for an alarm rule with timestamps that have not been reported since the last email. This way, you are also notified of brief alarms.

When the ibaManagementStudio server is restarted, the aggregation time and cooldown period are not reset. The notification status is also retained.

If emails cannot be sent, for example because the SMTP server is unavailable, the cooldown period does not start. The next time ibaManagementStudio checks for changes, it will try sending the email again. Recipients will then receive only one email containing all events.