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
{{ message }}
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.
From what I could tell there is no way to block the Servers Tab or turn off the ability to create/delete directories and dashboards. It would be great if the PromDash had a kiosk mode or immutable mode configuration flag that blocked access the CUD of CRUD. (with exception of the date/time range / interval selection etc..)
It doesn't need to be a full authentication system. Just a way to expose a PromDash for use without it being destroyed either unintentionally or maliciously.
The text was updated successfully, but these errors were encountered:
@skyscooby One workaround to currently achieve that is to put a reverse proxy in front of it that only allows GET requests.
Btw., we generally recommend using Grafana these days, as it is already a very popular dashboarding solution and has had Prometheus support for a while now. There'll be less effort going into PromDash in the future, unless users feel strongly about it and pick it up.
@juliusv I am just getting started with Prometheus and I have self discovered this about Grafana in the past 3 hours.. I do say however I have never had a more positive experience with two pieces of software working together both are rich at what they do, high performance and don't try and solve problems outside their scope.. Keep up the great work guys!
From what I could tell there is no way to block the Servers Tab or turn off the ability to create/delete directories and dashboards. It would be great if the PromDash had a kiosk mode or immutable mode configuration flag that blocked access the CUD of CRUD. (with exception of the date/time range / interval selection etc..)
It doesn't need to be a full authentication system. Just a way to expose a PromDash for use without it being destroyed either unintentionally or maliciously.
The text was updated successfully, but these errors were encountered: