APM can notify you by email when an important change occurs in path performance. The set of rules which determine when notices are generated and sent are called profiles. There is a default profile which applies to all paths, but you can add exceptions to it by creating additional profiles. Within a profile you can specify the organization, paths, and events that trigger notices; the addresses to which notices are sent; and the frequency of notices.
- Navigate to > Update Notification Options.
- ‘Default Email Addresses’—applies to all profiles that don’t have their own address list. Click the email address link to edit the default list.
- ‘Enable Service Bulletins’—Support occasionally needs to send service related emails. Emails are sent to the default addresses specified in your account settings.
- For profiles that should not use the default list, add addresses through the profile action menu.
The following events can be selected to trigger a notification. If you choose ‘digest summary’, all notices triggered during the digest period are aggregated into a single email, so that addressees receive fewer emails.
- Violation event
- Notices are triggered by alert threshold violation and clear events. To apply notification rules to only some paths in an organization, you’ll need to use saved Network Path Lists: first trash the ‘all paths’ list, then click Add List…. You may add more than one Network Path List to a profile. For violations, you can also choose to receive additional notices when a diagnostic completes and/or fails.
- Monitoring point availability
- Notices are triggered whenever the monitoring point loses its connection or reconnects to APM . For time windows, enter times according to monitoring point timezone.
The footer of event notification emails indicates which notification profile triggered that email, and contains a direct link to edit that notification profile.
You can optionally integrate APM with PagerDuty so that our alerts can also be managed from there. See PagerDuty.
You can configure monitoring points to generate SNMP traps upon delivery monitoring violation and clear events. SNMP trap are not available for usage monitoring events. See SNMP.