Hacker News Reader

Comment by ATsch | Hacker News Reader

I disagree with the idea that they can't work on both, but I have to agree that this is my #1 wish for Grafana. The frontend is filled with an incredible amount of ux papercuts, performance issues and silent breakage that make me resent having to edit dashboards at all. It's a perpetual state of being scared my next click will trigger "a script is not responding" or randomly break something I won't know how to fix.

It feels like Grafana Labs is stepping into the same "if it doesn't help sales tick checkboxes it's not getting development time" trap so many B2B companies hit as they grow and it's a shame. I wish there was something else I could switch to.

View on HN

Yeah, I too would prefer that they fixed their bugs and focused in their UX for the dashboards. There are a lot of tickets in the backlog on github which have been there for years and aren't being prioritized... I can't imagine wanting to associate distributed tracing with Grafana which is a data visualizer...

Which version are you using? And if you could tell us which datasources, that would help us as well. Narrowing this down helps us prioritise bugs.

I/We are using the latest 7.3.0 with Prometheus, however most of the issues are more general. I think they'd be hard to prioritize as they are so minor (outside of perhaps a "minor bugs only" sprint or similar, as some projects do). But they do add up very quickly.

To illustrate, here's some of the paper cuts that instantly come to mind: mod-s not working in panel editor, gradient fill incompatible with series overrides, various missing tooltips, missing query error reporting and syntax highlighting in variable editor, variable editor needing many clicks for most common actions, hidden variables can only be changed by repeatedly opening and closing the settings, some dashboard settings pages being easy to accidentally close without saving, g+[key] keyboard shortcuts randomly not working, random scroll jumps with multiple queries in a panel, switching between cursor modes with mod+o is super slow, Prometheus autocomplete not working when editing existing queries, clicking the dashboard name filters by folder while clicking the folder name shows all dashboards, adhoc filters silently don't work, etc.

The "not responding" one specifically happens a lot while editing queries. It'll randomly decide to evaluate the query while I'm typing, get thousands of results and lock up.

Oh man "random scroll jumps with multiple queries in a panel" that just hit me so hard, it drives me absolutely insane. I've now learned to stop using the mouse when navigating through the query text. Also annoying with the graph panel, when you apply a series override and want to change it later, you have to navigate the whole way to the setting again to change it. Makes you lose so much time just to try out some new colors for example.

can you report an issue on github for this and how to replicate? We have no reports of this scroll jumping and that sounds super annoying and something we want to fix asap.

Upgraded to 7.2.2 today and hasn't happened today, so fingers crossed.

No way to set a minimum axis extents: https://github.com/grafana/grafana/issues/979

Open since 2014, hitting it on every other panel...

Reply on news.ycombinator.com