grafana-discrete-panel
grafana-discrete-panel copied to clipboard
NatelEnergy
Indicating state into the future
I'm not sure whether this is a bug or whether I've incorrectly constructed my query. The custom zoom shown in the image below spans a few days into the past and a few into the future. The discrete panel doesn't stop showing state at the point where data is no longer available
Just to put this into context, below is a screenshot showing this compared to some of our other data.
Interesting! right now it fills up everything to right right with the last value. (actually every value fills up to the right and they just stack)
I'll add an option to cover up the future too
This will be super useful. I am using this panel to display active internet connection and obviously don't receive any data when there is no connection. So the panel keeps displaying active even though the connection is down until the data is backfilled. It would be great if the panel had an option to customize "no data" instead of using the last value.
That's interesting -- I think you're all reporting behavior that I would like to see. I'm using v0.0.6 on grafana 4.5.1. My data is single point values of "on" or "off". I see 'null' displayed between on/off entries. I think I've frobbed every option available but haven't seen a change in behavior.
@tczerwonka
I see 'null' displayed between on/off entries
If you are using influx, consider using fill(previous) if you have a group by clause.
+1
It would be great if the panel had an option to customize "no data" instead of using the last value.
Just to add on here with another example, I track my furnace off/on state and visualize it with this panel. If the furnace is on and the time range includes a future time (e.g. "Today"), it is a little funny to see the total runtimes. Of course, at least in my case I can just use the "Today so far" range to avoid it, but that might not work for everyone and obviously there are valid reasons to use future times.
In this image, the time range is set to "Today" and now is currently 18:00 and the furnace is running. (Also, you can see here I'd really like to have #69 fixed!)
