Michael Hoffmann
Michael Hoffmann
It sounds like one should use nyan ( i have no idea what that is! ). Im looking for a good Issue to get started on this project, do you...
> Hello! Just stumbled onto this PR. I am very interested into Influx line protocol support for vector and looking at the issues list others are too. > > @MichaHoffmann...
I already prepared and built artifacts for 0.33 yesterday; since this is still ongoing ill earmark it for 0.33.1!
Hey, Instead of `sum(increase(...))` can you try another range vector query like `max_over_time(X[1d])`; just for the sake of debugging. Also, is it possible to provide the raw data to ease...
Oh wow, thats perfect thank you! Ill have a look in a bit.
If i replay the query in the browser and add the "max_source_resolution=300000" query parameter it returns data: `{"status":"success","data":{"resultType":"vector","result":[{"metric":{},"value":[1691413341,"4042.0929376461977"]}]}}`
There is this option in the querier: ``` instantDefaultMaxSourceResolution := extkingpin.ModelDuration(cmd.Flag("query.instant.default.max_source_resolution", "default value for max_source_resolution for instant queries. If not set, defaults to 0s only taking raw resolution into account....
Yeah, would be interesting if it works with the flag. Autodownsampling is fine to keep i think.
Thanks for the great repro. How to address the issue properly i dont know yet.
Can you maybe share the block and query that reproduce this so we can try debugging locally? That would be very interesting!