Customization of emitted notification using templates
Monasca by default supports EMAIL, PAGERDUTY, and WEBHOOK notification. As of now the notification format is hardcoded in the code. Operators want to have different formats for notification. Example, for email notificaiton a typical installation may want to customize the header, footer, body contents. Now there is no way to do that without code change. This blueprint is to allow customization of notification using jinja2 templates and yaml file. Operators can change the yaml file to customize the notification format without changing the code
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Haneef Ali
- Direction:
- Needs approval
- Assignee:
- Haneef Ali
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Roland Hochmuth
- Completed by
- Roland Hochmuth
Related branches
Related bugs
Sprints
Whiteboard
An implementation for HipChat: https:/
Example:
For email we need
1) sender address
2) Subject
3) Content
Of which Subject and Content varies from Operator to operator, and some operators want to add additional footer to the contents. So a typical customization will yam file will look like
Email_format:
email_
subject : Alarrm recieved for {{ notification.
content: |
Gerrit topic: https:/
Addressed by: https:/
Add custom formatting options for HipChat
