The use case that immediately jumps out to me: being SSHed into a prod server during an incident and not wanting to context-switch to a browser just to eyeball a dashboard. Right now that context switch feels small but it breaks the flow at exactly the wrong moment.
Curious how it handles Grafana's templating variables (the dropdowns that filter by host, environment, etc.) — those are load-bearing for most of our dashboards. If that's supported, this goes from "neat demo" to genuinely useful in incident response.
It should handle the templating variables, at least from what I've tested on our dashboards. It gives you a list of available options just like in the Grafana UI. Try it out, once you select a dashboard you can press `v` and set the vars.
The use case that immediately jumps out to me: being SSHed into a prod server during an incident and not wanting to context-switch to a browser just to eyeball a dashboard. Right now that context switch feels small but it breaks the flow at exactly the wrong moment. Curious how it handles Grafana's templating variables (the dropdowns that filter by host, environment, etc.) — those are load-bearing for most of our dashboards. If that's supported, this goes from "neat demo" to genuinely useful in incident response.
It should handle the templating variables, at least from what I've tested on our dashboards. It gives you a list of available options just like in the Grafana UI. Try it out, once you select a dashboard you can press `v` and set the vars.
Cool will try
We actually use Grafana at work. What was the reasoning behind choosing a terminal instead of a browser? Otherwise, it’s a nice tool.
[dead]