Once you've created an alert, it will be automatically associated with your domain's default sending policy. This policy is partly defined by the delivery methods and the anti-flooding policy it is associated with.
- Sending policies: A sending policy dictates how to send an alert, to whom, when, and how often. When the domain is created, there is a default sending policy that uses the e-mail address of the domain's creator as the recipient. This policy will distribute the alert by e-mail, to the domain owner, at any hour, all while respecting the default anti-flooding policy.
You will want to set up new delivery methods and sending policies to accommodate your organization's needs but there must always be a sending policy marked as the default policy. This will be automatically assigned to newly-created alerts.
- Delivery methods: The delivery method dictates how an alert is sent and to whom. For example, a delivery method might be created to send an email to firstname.lastname@example.org, or to distribute the alert message via Pushover to mobile device users.
- Anti-flooding policies: The anti-flooding policy limits the number of alerts to distribute in the event that the alert is triggered frequently over a short period of time. This way, the anti-flooding policy associated with a sending policy determines how often the alert message will be distributed.
The following articles describe all the concepts and tasks related to configuring alerts.
- Manage sending policies
- Manage delivery methods
- Manage anti-flooding policies
- Make an alert available for panels
- Activate or deactivate an alert
- Pre-installed alert reference
These procedures are carried out in the Administration → Alert Configuration area and you need to have a role with manage permissions on this area to perform them (Administration → Roles → Permissions tab).