Sirene - Models
Reference
Sirene App provide a one-clic notification system to contact users about an important business event.
When an important event occurs, like a scheduled Maintenance, an IT outage, or a security breach, you may need to communicate with your users to inform, warn, provide recommandations, activate emergency response plan, etc.
Sirene is a tool included in Cavaliba to provide fast and high-quality notifications.
Key points:
Sirene is not intended to be an “automated notification system”, connected to some monitoring solution. It is rather designed to be used manually by a human operator in charge of decisions and notifications. You can still decide to use the Sirene API for automatic notifications though.
Sirene uses the following model : Sites, Groups of Sites, Applications and Services, Users, Groups of users, Customers.
The relationship between applications and sites is a key element to understand : Sites object contains a list of subscribed applications for which they want to be notified when a notification targets an application. Subscription means this site wants to be notified for this applicaiton.
A Sirene Operator can send notifications to any combination of targets : Sites, Groups of Sites, Applications, Users, Groups of Users, Customers.
Sirene computes automatically the list of users to be notified with the following rules:
a notification to a site will reach all users registered with the Site (under the “site notification” attribute)
a notification to a group of site will reach all users of each Site in the Group of Sites.
a notification to a group of users will obviously reach each user in the group
a notification to an application/service will reach :
Each users is notified once per message notification, that is he receives only one Email / SMS notification even if he belongs to several notifications targets.
Cavaliba Sirene can send notifications through various communication channels :
At a later point, Cavaliba may provide Slack or Teams Channel notifications
It’s not a good idea to write a message from a blank formular in the middle of the night during an urgent situation.
That’s what templates are for. You can prepare as many messages models as you wan’t, including target groups, hints, public web page content, private web page content and more.
During the notification process a Sirene Operators will :
Of course, an operator can always craft a new message from a blank form during an event, but templates are really there to improve the quality and speed of notifications.
When the triggering condition is over, or after a configurable period of time, Sirene will remove notifications displayed in the various Web Page and move the message to an Archive Repository.
Sirene Users and Operators can consult this archive to view past events and the communication around them.
An operator can send updates to a an active notification before it is removed and sent to archive.
It’s a good idea to send an Update before removing (archiving) a message to inform users about the end of the event.
For example, you can keep your users updated with the progress of a long / important maintenance, and expected time of reopening of the service.
Users can configure individual preferences regarding the notifications channels :
Reference