Repository navigation
feat(dogstatsd): listen on UDP and the named pipe together #181
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
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
1954990
feat(dogstatsd): listen on UDP and the named pipe together
Lewis-E 1829fcc
fix(dogstatsd): log the UDP listener only when it binds
Lewis-E e0d97bf
feat(dogstatsd): turn UDP off for port 0 when a pipe is set
Lewis-E 7c47762
feat(dogstatsd): run UDP and the named pipe in separate tasks
Lewis-E ffb439e
fix(dogstatsd): skip bad UDP datagrams beside the named pipe
Lewis-E 739137d
feat(serverless-compat): listen on UDP beside the pipe only when asked
Lewis-E f92a041
fix(serverless-compat): report the real DogStatsD port and flag bad p…
Lewis-E 010683b
refactor(dogstatsd): give UDP beside the pipe its own read loop
Lewis-E 2a78aed
docs(dogstatsd): point read_loop at the UDP loop beside the pipe
Lewis-E ce70c72
test(dogstatsd): wait for metrics instead of sleeping in pipe tests
Lewis-E d7af94f
docs(dogstatsd): tighten comments on UDP beside the named pipe
Lewis-E 1b79b66
docs: simplify comments around UDP beside the named pipe
Lewis-E 989a7ce
fix(serverless-compat): log the invalid DD_DOGSTATSD_PORT warning aft…
Lewis-E File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the UDP bind fails here,
/infostill reports statsd_port as the configured port. Does any tracer readstatsd_portfrom/infoto decide where to send metrics? Should we report 0 when the UDP port bind fails?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked x2 and it looks like only java reads this value, and reporting 0 for a failure would just lead Java to default to the same thing we're reporting: 8125. Maybe we can get a better flow of port/config when we do the config crate though?