Support sending result to InfluxDB with UDP protocal #302
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Thank you for your contribution, there are some issues I indicated, either fix them or I'll do when I have time ( not before 2 weeks) . |
Author
|
@pmouawad Thanks for your reviewing. I provide the usage of this sender below and hope it help. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we have HTTP support for InfluxDB backend listener. But sometimes people may apply UDP one because it is much faster and in most cases people don't care about a pot of packet loss.
This sender is similar with the http one and share the same backend listener UI. In "influxdbUrl" section, let's type in "[udp address]:[port]". For example, 1.2.3.4:9999