Protecting dashboards from users
Graphite users may be novices and could easily delete, re-arrange dashboards that were created.
I understand some of the original intent to have Graphite not deal with user classes (public, user, admin); I use public in a general way to describe users that do not have write access in the previous sentence, but could still be authorized by another external mechanism.
There will always be a need for user classes, if simply to help make users and administrators jobs easier.
Edit: Okay, I am a donut. I had an sqlite database problem which was why my events and user management was not working...
I understand also, that pickle and raw sockets are not the safest means of communicating. My question is more on the usability standpoint and not really from a security/interity standpoint.
Is there a means to protect some dashboards so that they are read-only. So users can clone them if they wish, but only admins could modify them. How are others coping with protecting dashboards from fat fingered users??
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Graphite Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Francois Mikus
- Solved:
- Last query:
- Last reply: