-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
udp json listener #477
udp json listener #477
Conversation
I think having a UDP listener would be good. I think it should follow the same conventions as the graphite listener. Have the database configured through the config file, use an admin account to write data. And have the body of the UDP request be an array of objects (like the query responses) so you can post points to any time series. With those updates we'd take it. |
ok I will complete it then. do you know if there is limit on datagram size on the loopback interface ? That's not the first time I look for an answer to this question but never found a decent one xD |
Not sure, but I think you can still go over that size and have it work. On Tue, Apr 29, 2014 at 5:52 AM, Julien Ammous notifications@github.comwrote:
|
here you go, I added the config part and rebased on master. |
great ! :) The idea is pretty simple: having as much as possible of the code related to a plugin in the plugin subfolder itself instead of lying around in core files. |
Can you please define what do you mean by "core files", and what do you intend to change ? Probably github isn't the best place for this. Hit me up on irc or start a thread on the mailing list. I'll be happy to see more code reuse between the different api, if that's what you mean. |
I will open a new thread on the mailing and try to be more explicit about what I mean, I already made an attempt previously but the thread did not get much traction. Now that I tried it I should be able to provide more precise ideas. |
Here is the new thread: https://groups.google.com/forum/?q=#!topic/influxdb/ap1yiVeXrIc |
(This is not ready to be merged as is)
I want something lighter than http for sending data to my influxdb and since my influxdb server and the producer are both on the same host I started with this simple listener which take UDP packets in with the standard json used for the http listener.
I want to know if this could be merged before working more on it (it may be simple but since I don't know much of go so it took me some time to even reach that point), it should works for simple use cases:
So far this works but there is no config part and I still need a way to tell in which series the data will be written (currently hardcoded).
So.. what do you think ? Could it be merged ? (if I add the missing part namely the config and a way to tell which serie to write to)
(This interface is only meant to write data, obviously)