Stacked bars are not displayed correctly about influxdb-flux-datasource

[davkal]

The floating stacks one is a general Grafana issue and is caused by not all series having a value for the union of all time values, see: grafana/grafana#9294

The wide-bar issue is a bit of an outlier, so I created an issue to discuss where this needs to be fixed: grafana/grafana#14130

[nikolay-t]

@davkal Thanks. However we don't see same issues with other datasources, i.e. SQL InfluxDB or Prometheus. Can it be that Flux datasource provides data in a way that triggers those Grafana issues?

[davkal]

I believe so, namely, when asked for data in a time range the new flux datasource returns only the datapoints that are there, whereas classic Influx and Prometheus have returned null values for every interval (step) in the requested range. You can observe this by using the Query Inspector in the other datasources, they will return data that looks like [ts1, null], [ts2, null], [ts3, 4], [ts4, null], .... Classic Influx even has a query keyword to make that explicit: fill(null).

[nikolay-t]

Agree, see this too if I create InfluxDB SQL query without aggregation and group by time. However it does not seem like we will have fill(null) in Flux language any time soon. As the result, now it makes stacked bars not usable with Flux source. What if we change Flux plugin a way that it will add null values after certain time (will equal to width of bar). Or you feel like 9294 will be resolved soon?

[davkal]

grafana/grafana#9294 needs to be fixed in the vendored flot code, since it should work for all datasources that return interleaved data points. It's not on the immediate roadmap, but I encourage you take a stab at it.

The wide bars should be an easy fix too (max-limiting the calculated bar width in graph.ts) if you want to give it a go.

[bryanspears]

Any chance there a query Alias could be exposed? I did a join on two measurements and the resulting legend "name" for the result set is crazy long.

[bryanspears]

For anyone's future reference: doing a join causes the _field value to get all mucked up. Quick and dirty way to have your legend show a pretty value: |> set(key: "_field", value: "Label Here")

[ryantxu]

I'll close this unless there is something clear we could/should do in the datasource plugin to better support this