-
Notifications
You must be signed in to change notification settings - Fork 22
Is compatibility with InfluxDB 1.7.x broken? #100
Comments
This plugin is now using this client: https://github.com/influxdata/influxdb-client-go/ I'm not sure what is involved in getting that client to read flux results from 1.7... |
Any more details on the error you see? Is there anything in your browser console log? or maybe in the server logs? |
Here is what information I managed to collect From "Network" tab:
InfluxDB logs (v1.7.3):
The time window in the request is set by the range function:
Please let me know if you need anything else. |
Hi I also had the same error. This happens when you have setting |
In my case, the parameter is List of what I redefine:
|
@Akira74 not working ( |
Hello! Is there any news on this and #101? |
@M0rdecay for your time filter, can you try:
rather than $range? if that change works, I'll look at adding some of the old macro expansions to help with migratoin. In v7, we aimed for getting copy/paste from chronograph to work |
Thank you, I will try this solution:
IMHO, this breaks uniformity with Grafana as a whole. Variables are expected to have the same syntax everywhere. |
Let me know if it works! I wish variables had the same syntax everywhere! weirdly there are two concepts "template variables" and "macros" -- they look the same, but are actually totally differnt, when this switched to a backend plugin, it switched form a frontend template variable to a backend macro |
Hm...
But it fails when request has
Very strange, but everything is fine in the InfluxDB log:
Upd. group statement: |
It seems that the situation is also happening on other versions of InfluxDB - #109 |
This is an example of a query that has a problem. The first filter is intentionally replaced by neutral data, but still displays the essence of the situation: errs = from(bucket: "$database/$ret_policy")
|> range(start: v.timeRangeStart, stop:v.timeRangeStop)
|> filter(fn:(r) => (r._measurement == "cpu"
or r._measurement == "mem")
and (r._field == "used_percent"
or r._field == "usage_system"))
|> group(columns: ["host"], mode:"by")
|> derivative(unit: $coll_interval, nonNegative: true)
|> aggregateWindow(every: $coll_interval, fn: sum)
|> filter(fn: (r) => r["_value"] >= 0)
|> yield() But this request is working fine: errs = from(bucket: "$database/$ret_policy")
|> range(start: v.timeRangeStart, stop:v.timeRangeStop)
|> filter(fn:(r) => (r._measurement == "cpu"
or r._measurement == "mem")
and (r._field == "used_percent"
or r._field == "usage_system"))
|> derivative(unit: $coll_interval, nonNegative: true)
|> aggregateWindow(every: $coll_interval, fn: sum)
|> filter(fn: (r) => r["_value"] >= 0)
|> yield() |
Let's leave this issue open with the following wording - for compatibility with previous versions of the plugin needs support for the A discussion of the function of the |
How are dashboard variables handled? Are those still supported with their |
Yes, the rest of the variables work, I had no problems using them. Only plugin-specific variables have changed. The full list can be found here - https://github.com/grafana/influxdb-flux-datasource/blob/master/pkg/influx/macros.go This plugin really needs documentation! |
After upgrading to Grafana 7.0, panels using Flux stopped working. The error is as follows:
In this case, the data source is ok:
This is a big problem, because InfluxDB newest than 1.7.3 cannot be used in highly loaded environments due to this error - influxdata/influxdb#13318
Are you planning to return compatibility with versions 1.7.x?
The text was updated successfully, but these errors were encountered: