Create an alarm northbound implementation for Email
Description
Acceptance / Success Criteria
None
blocks
depends on
Lucidchart Diagrams
Activity
Show:
David Hustace January 5, 2016 at 4:25 PM
Makes sense to me.
Alejandro Galue January 5, 2016 at 4:00 PM
I know it looks nicer, but it not consistent with its siblings certainly I can apply the change, but I think all the NBIs should follow the same rule.
David Hustace January 5, 2016 at 3:56 PM
So, the concept is that each destination could have multiple email targets supporting a filter rule. LOOKS GREAT.
The only unnecessary change I would make
Alejandro Galue January 5, 2016 at 3:53 PM
Combining my idea with your idea, we can add from/to fields to the destination, and use them defaults if the filter that matches the incoming alarm doesn't have the fields:
That way, we can define the mailer like this in javamail-configuration.xml:
This is not on the code base yet.
Currently, OpenNMS has northbound implementations for Syslog, HTTP and JMS.
There are several use cases that justify forward alarms through Emails.
Similar to the Syslog NBI, we need a set of target SMTP Servers (destinations). For each destination, we need the FQDN or IP of the SMTP server, the port, the protocol, and a set of targets (email of the recipients).
We should be able to specify a template for the email subject and the email content based on the incoming alarm, and be able to define filters to map destinations with formats and send emails if the incoming alarm matches a specific rule.