Ok thats enough for me

[torkel]

@dev11

In the latest Grafana there is a bug when you add new panel to dashboard it gets added but when you click on panel title and want to edit it, whole panel randomly disappears -> this leaves “shadow” of this panel -> this causes error on both saving dashboard and on loading dashboard (empty space with red exclamation mark) -> this is undeleteable and unreplaceable (=you cannot place other panel over the “shadowed” one).
This is perfect example of how one bug can start cvascade of other bugs.

This is a completely new an (up unitl now) unreported bug. Unable to replicate it in latest stable & master.

Can you replicate it here? Grafana What version of Grafana & Browser & OS are you using to replicate this bug?

@dev11

Another (cascading) bug :: when you hover mouse over graph (doesnt matter its type) to display tooltip -> its all ok, but data update while tooltip is displayed causes tooltip text to disappear, leavinjg tooltip frame on the screen… When you move your mouse out of tooltip area, the tooltip (or better named:: its background) stays on screen -> this stops whole graph from refreshing.
Whats interesting is that this can be observed on Azure dashboard only . Other dashboards are ok as of tooltips.

This is also a new unreported bug that we have not heard before. Maybe because Azure is yet not that common a plugin. Can you open a bug report on GitHub - grafana/grafana: The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more. with instruction on how to replicate it?

@dev11

As of alerting :: its only available with graphs. Why? Whyt cannot we set alerts for, say, heatmap or other types?

Because we have not yet added this feature. There have been a million other things to add & improve.

@dev11

Incompleteness of UI:: Add graph type table, go to Edit it > open Column Styles pane. There is a group called Type ? Type of what?

Type of style to apply.

@dev11

lick +Add link on the left and set Type to String , configure value mappings and than switch Type to whatever else, configure and switch Type back to String … you will notice that preview stays on what you’ve changed Type to…

Ok, not sure I 100% understand the issue but does not sound like a critical bug (not that it shouldn’t be fixed).

@dev11

Also - explain to me whats the rationale behind restricting alerting only to graph instead of allowing alerting from any type of visualisation? Also what the hell is alerting icon on the left panel for, if - when clicked - loads page that will not let you add alerts?

Since we did the first iteration of Alerting the core Grafana team has been focusing on other core Grafana features (UX & dashboard grid & missing visualizations and reviewing & refactoring thousands of community pull requests & bug reports). There has been no big PRs & community enhancents to alerting in the mean time so the feature has not improved much since it’s inception.

@dev11

Speaking of it:: when you create an alert, save it, click on Alert icon on the left pane, your alert is visible there, but its colored orange with exclamation mark; once clicked you are sent to corresponding graph with red error msg saying that (hold yourself) :: The datasource does not support alerting queries

This error message should be there from the start when you create the alert (it is for me). Only a limited core set of data sources support alerting since they are executed by the backend and old datasource plugins where frontend only (js). We have since then added support for backend plugins so now external plugins can also add alerting support but this requires more work for each data source.

@dev11

Not to mention there is no way of correctly saving alert on “unsupported” graph - it will leave “shadowed” alert and this will render as red exclamation marks instead of graph…

I am not sure what “unsupported” graph means. We have no similar reports to what you describe so not sure what your experiencing.

@dev11

By ‘cascading’ I mean bug(s) that triggers either other bugs or unwanted behavior.
All of the above bugs leads to problematic/being unable to/corrupted saving dashboard…

Thanks for reporting this. We have no other reports like it so this is very valuable. Can you open a github issue with server & chrome network logs for when you get this corrupt dashboard that wont save / load?

@dev11

Many of the above bugs have been here from 2-3 releases. It feels like you (=developers in general; not you personally) stopped taking care of quality…

We care a great deal and are very thankful for any bug reports that lets us know that things are not working as they should.

@dev11

EDIT2:: Just noticed:: when you select specific region on one visualisation (regardless its type), what gets enlarged (zoomed in)? Every visualisation on open dashboard.

Not sure what you mean by this sentance. When you zoom in a region on a graph you change the time range on the dashboard so all other panels will show data for the new time range. This is how Grafana (and 99% of other dashboards) work. Is this unexpected to you or do you mean something else?