Use case
Grafana wallboards and TV dashboards that stay up
Put Grafana on the wall and stop worrying about kiosk mode, session timeouts, and Chromium memory leaks.
For: DevOps and SRE teams, NOCs, and anyone running Grafana, Prometheus, or Kibana dashboards.
grafana-wallboard Raspberry Pi 5
Online99.98%412 rps24 ms
- CPU temp
- 51.2 °C
- Wi-Fi
- -58 dBm
- Storage
- 6.1 / 29 GB
- Uptime
- 41 d 3 h
- Browser
- Healthy
- Agent
- v0.4.2
RefreshScreenshotRestart playerReboot
The usual pain
- Grafana kiosk mode needs a browser that never dies and a session that never expires.
- Playlists and refresh behaviour differ by browser version.
- A wall of screens becomes a wall of snowflakes.
With DisplayOps
- Use Grafana kiosk URLs and service-account tokens; DisplayOps keeps the page loaded and refreshed.
- Detect a hung page or crashed browser and restart it automatically.
- Rotate several dashboards with a slideshow, or override all screens during an incident.
Setup
- 1Create a Grafana service account token or a public dashboard link.
- 2Pair the Pi and set the kiosk URL.
- 3Add an incident message content item and push it to every screen when needed.
Questions
How do you handle Grafana login?
Public dashboards and token-based URLs work today. Managed authenticated sessions are on the roadmap.
Connect a screen. Tell it what to display. We keep it running.
Three displays are free. No card, no sales call, no signage jargon.