3/27/2026 at 11:36:03 AM
by lmazgon
3/31/2026 at 3:33:53 PM
This is cool. I could see it useful for ops and dev teams. Would still need Grafana to be visible in the UI for less tech savvy support teams, etc..by david1-618
3/29/2026 at 7:34:48 AM
If you're using Grafana for monitoring, you might also want to get those alerts as actual phone calls on iOS — Echobell (https://echobell.one) takes your Grafana webhook and turns it into a push notification or even a phone call that bypasses silent mode.by noobnooc
3/27/2026 at 11:40:34 AM
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.by mitul005
3/27/2026 at 3:38:51 PM
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.by lmazgon
3/27/2026 at 7:00:10 PM
Cool will tryby mitul005
3/29/2026 at 7:20:26 PM
Nice structure — separating the Grafana client from the TUI layer should make it easier to extend. Also cool to see testcontainers for integration tests.by spbuilds
3/28/2026 at 6:16:39 AM
We actually use Grafana at work. What was the reasoning behind choosing a terminal instead of a browser? Otherwise, it’s a nice tool.by mkellercz
3/29/2026 at 1:09:25 AM
this looks very interesting...I'm gonna give it a test drive later. Threw a star on the repo so I won't forget to come back to it.by munch-o-man
3/27/2026 at 4:50:26 PM
[dead]by SArndt
3/29/2026 at 6:26:05 PM
[dead]by jeninho