Jack
Jack
just stumbled across this as a workaround in the mean time https://github.com/prometheus/influxdb_exporter can confirm it seems to do the job
Yeah it's by design, your actual Prometheus instance ends up keeping it stored if that makes sense. So speed test -> exporter -> prom -> grafana
you need to have an actual prometheus instance hit the exporter, that prometheus instance is what stores it. If your main instance is blatting your data youll need to google...
@jiriteach fyi i found there is this flag `--influxdb.sample-expiry 30m` by default its only 5 mins
just thought id add, i just started running into this. was booleans as investigated. and the fix referenced worked for me a soon as i updated 👍
@Laakso yes, i can confirm from ~ 6.10 of helm chart its out or ~2.11 of argo. whatever your install method is.
that could work, only reason id suggest we shouldnt is it would just be very tedious to make the feature useful in a large scale use imo, before we add...
@bwoodsend thanks for the tips, ill just add it also gets a little more complicated when you then use the action within composite actions and using those composite actions multiple...
Ah sorry i missed this reply somehow, @grv231 we moved away from synk for the image scanning as we couldn't get it working and found that what it would have...
@daftping can confirm this worked for me