Influxdb reconnection failures
visibilityspots opened this issue · 10 comments
Seems like I'm having the issue as described over here: influxdata/telegraf#5905 I tried to run the container using the environment parameter through docker but that wasn't a success :(
I'm wondering in which file I should add this GODEBUG=http2client=0 parameter to test if this solves the issue with influxdb reconnecting behind a proxy like traefik
Hi Jan,
I created branch issue_27 and set the variable: https://github.com/mikenye/docker-readsb-protobuf/blob/a87f0aa9c78fd840c76f287d9b6b715d74733f9e/rootfs/etc/services.d/telegraf/run#L9
Are you able to build and test?
-M
I've builded the image and running as we speak, will keep an eye on it and try to reproduce the issue to see if it fixed the interrupts. Will keep you posted!
it didn't worked, but I have now a branch to play upon, will try some stuff and let you now when I got it fixed hopefully!
No worries, let me know if I can help.
btw, is there a guide setting up grafana with readsb, did not see much in https://mikenye.gitbook.io/ads-b/?q=grafana
@mo8Zomo0 currently no - I've been meaning to write one, however in the meantime InfluxDB v2 has been released, and it is completely different to v1. If you join the Discord server and message me, I would be happy to talk you through the process for InfluxDB v1.8, however I don't really want to spend the time documenting it, only to have to re-do it for v2... :)
@mo8Zomo0 you might also want to check out: https://grafana.com/grafana/dashboards/13168
It only works with InfluxDB v1.x, but might be useful to you.
Hello! Stumbled across this issue, I've been meaning to fix my output to InfluxDB to get my Grafan Dashboard working again after my container for InfluxDB updated to 2.0.
Are you working on the new connection to InfluxDB2.0 or is it worth my pinning my InfluxDB container to 1.8 and using the existing output for InfluxDB?
to me this issue can be closed since I switched to prometheus.