Looking to replace Alerta but need Multitenancy

[lorddaren]

It looks snooze would be a great alternative to Alerta (that has been maintained for a while). I noticed that there are groups that can be assigned, but I cannot tell if alerts can be hidden if an alert comes through and the rule assigns it to a group.

We want each of our teams to have access to alerts but having those users only see their alerts. Is that currently possible?

[rudexi]

Hi @Xorso,

While snooze doesn't support separate views from an RBAC perspective (you cannot restrict users to only see certain alerts in the main view), so if you want to handle data from different customer and provide them a view only them can see, it's not possible.

The following is possible though:

• You can use environments to make filters for the main view.
• You can make rules that set custom fields
• You can make multiple notifications based on the custom field you set in rules

Currently, we are using snooze in production in my current company with the following setup:

• A rule set a custom field "owner" based on who own the server (can be a regex, but we're using a script to populated a key-value to map hostnames to owners).
• We have one custom notification per owner (each goes to a custom google chat room), and a delayed "sink" notification that goes to our monitoring team. If the alert isn't acknowledged/closed by the time the delay is up, it goes to our monitoring team.
• We have "environments" filter per team and dev/test/prod. These environments can be combined with a "AND", so they act as
  an easy way for teams to filter alerts related to them,

Multi-tenancy is technically on our roadmap, and we're still thinking about how to make it, so comments are welcome.

[lorddaren]

Thank you for the quick response. I work with python and vue so I will poke around the code and see what I can find and see if I can make some educated comments.

[Nemega]

By the way if you need to try Snooze before deploying it to your infra, please use the following link: https://try.snoozeweb.net/
Try to inject logs by following the doc: https://snoozeweb.github.io/snooze/_build/html/general/04_Inputs.html (replace snooze.example.com:5200 with snoozeweb.onrender.com)