-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support relay of collectd UDP #83
Comments
Just to prove the concept of forwarding the UDP payload works, I made this change and tried it out..
What this is doing Is taking the incoming UDP buffer (without trying to parse for the line protocol) and simply writing it out to the list of backends. I am new to golang & influxdb-relay code - I am not completely sure I have written the code in a way there are no leaks, etc). If you guys think this should work - I can work on a patch that introduces a "collectd" relay (in addition to existing HTTP and udp relays). Do you guys foresee any issues? |
…InfulxDB UDP line protocol to support sending over collectd traffic over UDP influxdata#83
…InfulxDB UDP line protocol to support sending over collectd traffic over UDP > influxdata#83
…loring for InfulxDB UDP line protocol to support sending over collectd traffic over UDP > influxdata#83
…loring for InfulxDB UDP line protocol to support sending over collectd traffic over UDP > influxdata#83
I looked at #54 and #29
this seems to be couple of years old.
Is there no way to use HA-based deployment for collectd based ingest traffic?
What is the problem that one type of UDP payload (line protocol) can be relayed but not the other (Collectd). Is there any technical problem that prevents relay of collectd based ingest data?
The text was updated successfully, but these errors were encountered: