Ways of notification are currently relatively hard coded in the Alert Mangers and GUI. So it is not easy for customers to add their own ways of notification We should take a more factory/plugin-like approach, where users supply a child class of AlertNotification which defines their way of delivering alerts. The class would host two things - methods to describe the ui requirements - methods that do the alert sending (and some persistence of that) So users would just need to write that class, compile it, put it "somewhere" in the server, restart the server and use their new way of sending alerts.
agreed, this is a fairly important feature so that we can integrate our alerting information with all of the other sys mgmt products out there. we need to think carefully about how to implement this correctly, specifically an API that is going to be good for customers but flexible for us in terms of backward compatibility. as new versions of the server come out, the interface may chance slightly, and we don't want to require customers that have written these integration points to have to update all of their code.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-585 This bug incorporates RHQ-797
This has been implemented as pluggable alert senders.
qa -> skondkar
This _newFeature_ has been tested as part of testcases for pluggable alert senders. Marking this bug as verified.
Mass-closure of verified bugs against JON.