-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
chore(inputs.statsd): Refactor internal stats into their own struct #16419
Conversation
Thanks so much for the pull request! |
…ruct Summary: Later in this stack of diffs, I add a field named `MaxConnections` to `Statsd` because it controls the max number of connections for all listener types, not just TCP listeners. That creates a naming collision with the existing field named `MaxConnections`, which is an internal stat tracker. This diff eliminates that name collision by encapsulating all of `Statsd`'s internal stat trackers in a struct. Test Plan: Existing unit tests pass.
!signed-cla |
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
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.
Linter failure is unrelated to this PR. Thanks for the work!
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.
Thanks @Manbeardo!
Summary:
Later in this stack of diffs, I add a field named
MaxConnections
toStatsd
because it controls the max number of connections for all listener types, not just TCP listeners. That creates a naming collision with the existing field namedMaxConnections
, which is an internal stat tracker. This diff eliminates that name collision by encapsulating all ofStatsd
's internal stat trackers in a struct.Test Plan:
Existing unit tests pass.
Stack created with Sapling. Best reviewed with ReviewStack.