Hey unfortunately I suspect this is not possible, at least through any reasonable means… but will try and give some more thought to it. Could you explain some more about why you are looking to do this and where this view would be presented? I’m assuming a custom plugin?
In our case, users have many dashboards depending on a datasource plugin. In certain scenarios, this datasource returns no data or fails due to maintenance on the target API side, hardware/software upgrades, temporary data unavailability due to sensor response delays, and other similar situations. To be brief…
To avoid disruption, we do not stop the Grafana service during these periods.
However, in these scenarios, users often complain (a ticket is created) about no data being shown and errors on some panels. Even when notified, they usually don’t know or are unsure if there is maintenance or why there is a gap. Once the system recovers, the data gap for this period is filled with forecast values and properly tagged.
Ideally, we want to hide/notify/restrict access to these dashboards during these periods to prevent overloading the ticketing system and reduce the refresh actions on Grafana from around 100 dashboards.
Thanks for the detailed response - that helps! So what would be possible is to trigger a banner notification during those periods of maintenance. Filtering / restriction would quickly get messy. But with a notification you could advertise when this is the case and hopefully prevent those tickets
Can I ask how you’re running Grafana - OSS/Enterprise/Cloud?
Hi @davidharris
Thanks for you help.
We are using OSS.
Yes we have sort of alternative(banner).
We also leverage use Grafana RBAC to control accesses over dashboards but custom roles are only available with enterprise version.
So we may go for a more drastic approach by working on a fork.
Regards.
Yeah, there’s some upcoming features in Enterprise which also make displaying a banner easier, as well as a something you could use within your own app plugin which exists today. But not sure of a way to make this work easily OOTB in OSS