yesoreyeram-boomtable-panel
yesoreyeram-boomtable-panel copied to clipboard
yesoreyeram
[Bug] Appears a threshold value of zero is being treated like no data.
Describe the bug I have a boom table panel that I use as a Key so viewers can tell what icons mean when they appear in other panels. Using the Font Awesome character like a wrench, or check, or hour glass. While testing deployment options that grab the latest plug ins I found that the icons were not displaying properly in some cases. I was seeing lots of "No Data" when I was expecting a font awesome character. In the case of my Key panel the data value is 0. S0 thresholds are setup that a value of zero should display a green check mark. Instead I get "No Data". It looks to me like a value of zero is being interpreted as no data/missing data. Even when it is a legitimate value.
Screenshots
BoomTable v1.0.0 (current version we use)
Boom Table v1.4.0
(Also shows the sort order difference mentioned in another issue)
Version Details:
Grafana version : 7.2.1 Plugin version : 1.4.0
Additional context
after upgrade grafana 6.5.x->7.3.3 and then plugin to 1.4.0 have the same issue all zeros turned into "No Data" values :(
Same issue. Prometheus metric with a value of 0 is treated as Null / No Data.
Grafana 7.2.0 and plugin 1.4.0
I have a simple query checking if a service is up/down.
node_systemd_unit_state{instance="test-server",name="firewalld.service",state="active" results in a 0 as the service is down, but is shown as N/A on the current Boom Table.
This seems to be fixed in the latest in GitHub.
@yesoreyeram can the version in Grafana be updated?
In the meantime, try pulling this repo and building and deploying it to your Grafana cluster yourself.
If this fix can be released it would be great, I have a lot of Status checks that return 0/1 for fail/success.
The v1.5.0-alpha.3 release seems to fix this, as reported by mcbirse in a test here: https://github.com/jasonacox/Powerwall-Dashboard/issues/49#issuecomment-1179510741
@yesoreyeram if v1.5.0 is still too alpha, would it be possible to branch v1.4.1 tag and pull just this "No data" fix into a v1.4.2 release?
