Details
-
New Feature
-
Resolution: Fixed
-
Minor
-
None
-
None
Description
Right now there is the ability to configure as the email alerting endpoint:
1. system default email contact in config.php
2. per device contact via snmp within device
Request:
We would like the ability to add an email contact per alert checker. This alert checker contact should override the default and device contact. If the alert checker contact isn't defined, then the two other contacts would be used as normal.
Use Case:
We have different groups that need to be alerted based on the content of the alert, even though the same device may have generated the individual alerts. Example - We have several PE routers with 100+ serial t1 interfaces to customers. We monitor the serial links for up/down, errors, and high bandwidth usage. The router itself is monitored for cpu, memory, bgp sessions, and sensor states. With this PE router as an example, I would like to send the serial link up/down and error alerts to our Support Department for followup with the LECs. The serial link high bandwidth usage alerts need to be sent to our Sales department for a bandwidth upgrade opportunity. The cpu, memory, bgp sessions, and sensor states alerts need to be sent to our Engineering department for their review.
Current Workaround:
Yes this could be done with rules in the email server if all email is sent to the same inbox as it currently does. This however leads to multiple systems having to be administered when an alert is created. Also we send as few alerts as possible directly to our email inboxes. Most alerts are sent directly to a third party alerting service which bypasses our email inbox rules.
Alert Contacts already implemented some time ago..