Add support for periodic notifications for Heat integration

Registered by Joe Keen

Add periodic notification support to the Monasca Notification and Monasca API projects to allow integration with the Heat project.

The Monasca API notification endpoint will accept a periodic interval argument of 0 or 1 representing off and a 1 minute interval. Webhook notifications allow a 0 or 1 for the periodic interval while Email and PagerDuty notifications only allow a 0.

In the Monasca Notification engine if a notification has a non-zero period it will be placed onto a Kafka topic for processing by the periodic engine and sent as normal. The periodic engine portion of Monasca Notification will read a notification from Kafka and send it once one minute has elapsed since the last send. Periodic notifications will stop sending once there is a state change in associated alarm.

Notification failures in the periodic engine are not sent to the retry Kafka topic.

This change requires the addition of a column to the notification method table in the MySQL database and the creation of a new Kafka topic that the periodic engine can use to store pending notifications.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Joe Keen
Direction:
Approved
Assignee:
Joe Keen
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Roland Hochmuth
Completed by
Roland Hochmuth

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.