Currently the script builds a query for the user.
For maximum flexibility, it'd probably be good if it were also possible to specify a custom Flux query in YAML.
It should use placeholders for start, stop and window (probably best to stick with the existing v.timeRangeStart
etc.
Activity
05-Feb-23 11:47
assigned to @btasker
05-Feb-23 12:03
mentioned in commit 9a8534a53e555cd80b20e9e2a85449a1d3018aa6
Message
Add support for new
query
attribute in jobs, to define a custom flux query utilities/python_influxdb_downsample#605-Feb-23 12:03
mentioned in commit e4b2f579fcb72c1f1276da39799f3ef57e49dd5c
Message
chore: Move query generation to dedicated function in prep for utilities/python_influxdb_downsample#6
05-Feb-23 12:09
mentioned in commit 2dc0e4976efc59005f041d4e504092589fe06ce1
Message
docs: update docs for utilities/python_influxdb_downsample#6