Mechanisms for launching alerts

Registered by Nick Barcet on 2013-03-05

As we develop alerting in Ceilometer, it might be a good idea to provide a simple destination endpoint for alerts to be forwarded as:
- events on the oslo RPC bus
- emails (SMTP)
- SMS
- Nagios alerts

This should be a run by a set of distributed workers running a plugin based on the type of alarm to raise.

Blueprint information

Status:
Complete
Approver:
Julien Danjou
Priority:
High
Drafter:
Nick Barcet
Direction:
Approved
Assignee:
Julien Danjou
Definition:
Approved
Series goal:
Accepted for havana
Implementation:
Implemented
Milestone target:
milestone icon 2013.2
Started by
Julien Danjou on 2013-06-21
Completed by
Julien Danjou on 2013-07-16

Related branches

Whiteboard

From the summit discussion ( https://etherpad.openstack.org/CeilometerSimpleMessagingAlertingH ):

Third-party services
- opsgenie.com
- PagerDuty.com
Use openstack.common.notifications library to send alarms, and have a separate listener for those messages do some work.
- fails silently, so maybe not reliable
Need option to do continuous alarming while alarm state is still on

Gerrit topic: https://review.openstack.org/#q,topic:bp/alarm-notifier,n,z

Addressed by: https://review.openstack.org/34217
    Implement a basic alarm notification service

Addressed by: https://review.openstack.org/36688
    Implement a basic REST alarm notification

Addressed by: https://review.openstack.org/37211
    Implement a https:// in REST alarm notification

Addressed by: https://review.openstack.org/37219
    alarm: Global setting to disable ssl verification

Addressed by: https://review.openstack.org/37218
    alarm: Per user setting to disable ssl verify

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.