algenty/grafana-flowcharting

Grafana-flowcharting changes not reflected on dashboard while it works in edit mode of the panel

debasishdas033 opened this issue · 13 comments

debasishdas033 commented

I have configured one grafana-flowcharting panel which shows the color change properly based on threshold. Mapping rule works only good when this panel is opened in edit mode. But it does not show the color change on the dashboard view when I save and apply all the changes to show on dashboard.

debasishdas033 commented

It works on Firefox but not on chrome.

algenty commented

ok, need to try

debasishdas033 commented

It is fixed now. After saving the changes in the panel, the browser should be refreshed to reflect the new changes on the dashboard.
I was not refreshing as I was expecting it will happen automatically.

traztor commented

Having the same type of issue, Mapping Rules won't save in between Apply even after the saved dashboard banner, tried on both Chrome and Firefox.

Metric Type set to Table under Mapping won't save to dashboard. But the Metric Type Series is working now.

Main Dashboard won't update on either!

traztor commented

Tried the snapshot version, now it is working only for metric type series. I also tried to downgrade to 8.1 and got similar results below.

Metric Type when set to Table is still not saving on either browsers and not working on dashboard outside of edit mode.

Also, when I set Aggregation for Last and Last (not null) they are both returning nulls. I inspected the data from inspect tab there are no nulls in data table.

My use case is heavily dependent on Metric Type Table and Aggregation Last/Last (not null) working correctly. What should I try next?

algenty commented

What is your version of grafana ?
I have the bug on grafana v7 not v6

traztor commented

Yes I am using the latest Grafana. Are you recommending to downgrade to Grafana v6 or should I wait for a fix in the next release.

algenty commented

no,i need to fix it in v7. it's a minor bug

algenty commented

I confirm, this bug is a regression in grafana 7.1

lennyoed commented

Is there any current update to this issue? Is the fix simply to downgrade Grafana to version 6? Is there a known patch? Does additional data need to be collected and provided?