RBAC permission required to silence check or entity

[KendallChenoweth]

I have created a rbac setup, but somehow, have missed assign privileges to allow the user to silence (and probably unsilence) an entity or check result. Can you please tell me what I’m missing? Thanks!

sensuctl user create tom_webops --password=‘password’ --groups=webops
sensuctl role create webops-admin --verb get,list,create,update,delete --resource assets,checks,entities,events,filters,hooks --namespace webops
sensuctl role create webops-readonly --verb get,list --resource handlers,mutators --namespace webops
sensuctl role-binding create webops-oncall --role=webops-admin --group=webops
sensuctl role-binding create webops-reaodnly --role=webops-readonly --group=webops

[KendallChenoweth]

I figured it out. I had to add “silenced” to the resource list.

[jspaleta]

Hey,
I put together a gist with the start for a reusable pattern for good RBAC practice. Can you take a look at it. Now that you have successfully produced an RBAC scheme do you any suggestion on my pattern to make it better?

Jef Practice: Reusable RBAC to setup team namespace for self-service monitoring

Here’s a practical example of using RBAC to provide self-service monitoring for distinct teams in your organization using a single Sensu server configuration. The premise is each team will be running its own agents and will need its own check,assets, and handlers… all the things in a self-service manner…without bumping into each other. Before diving in to this practical example, take a look at this blog post describing how Sensu RBAC works: https://blog.sensu.io/understanding-rbac-in-sensu-…