andig
Unfortunately, as the docs say: > This plugin allows Telegraf to provide an InfluxDB 1 /write compatible proxy. This will not allow you to read from InfluxDB, should you be...
You can write to Telegraf, but why should this increase performance?
> Telegraf service is running on the same machine, but InfluxDB is running on another machine, right? yes > So, I want to avoid network overhead You mean by using...
See https://www.influxdata.com/blog/influxdb-2-migration-path-instrumentation/ for how to use input listener/ influxdb output. I have not tested if this really improves performance.
Any chance to get this fixed? Happens again after every docker version bump... Would be happy to do a pr. Even simpler without json handling: ``` docker context inspect -f...
Unfortunately that doesn't suffice: ``` ../flyctl/bin/flyctl deploy --local-only ==> Verifying app config Validating /Users/.../htdocs/fly.toml Platform: nomad ✓ Configuration is valid --> Verified app config ==> Building image host unix:///Users/.../.docker/run/docker.sock
It seems that there is an issue with connecting to user's socket: Cannot connect to the Docker daemon at unix: This happens when pinging the new client. No idea why...
Yikes, fixed! Thank you for noticing. I don't see the Docker change in 4.19, so might really be 4.20.
Fixed for me after setting Docker to use the global path again. Still- I think users explicitly need to enable that.
Or preferably, solving captcha should just use an io.Reader as input for a go-ish implementation with maximum flexibility.