You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Based on this PRD and this RFC. We plan to move responsibility of sending notification to siren from provider. There is a need to flexibly send custom notification messages to each receiver type.
Describe the solution you'd like
The Flow
Custom notification message could be implemented with a pre-defined template assigned to each receiver in the subscription flow. When subscribing a notification, one should pass this struct.
Depending on the receiver type, receiver configuration could have various field. A new template field could be added to define that this receiver of the subscription would use the template for the notification message.
The Template
The template could be created with the same way as user create template for the rules. Instead of having a type rule, template would have type notification. The content of the template should be compatible with the contract of receiver type payload. For example, this is how the slack notification template is.
Template will be rendered when notification is being dispatched and before a notification message is generated. Therefore, notification message would contain the rendered version of the notification message. Other than that, variables are being populated based on labels that the notification has.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Based on this PRD and this RFC. We plan to move responsibility of sending notification to siren from provider. There is a need to flexibly send custom notification messages to each receiver type.
Describe the solution you'd like
The Flow
Custom notification message could be implemented with a pre-defined template assigned to each receiver in the subscription flow. When subscribing a notification, one should pass this struct.
Each receiver needs to be like this
Depending on the receiver type, receiver configuration could have various field. A new
template
field could be added to define that this receiver of the subscription would use the template for the notification message.The Template
The template could be created with the same way as user create template for the rules. Instead of having a type
rule
, template would have typenotification
. The content of the template should be compatible with the contract of receiver type payload. For example, this is how the slack notification template is.Template will be rendered when notification is being dispatched and before a
notification message
is generated. Therefore,notification message
would contain the rendered version of the notification message. Other than that, variables are being populated based on labels that the notification has.The text was updated successfully, but these errors were encountered: