We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would it be possible to enable the use of SO_REUSEPORT when listening for SNMP traps?
I run a single-node Kubernetes cluster. I'd like to run multiple copies of Telegraf, each listening for traps, but they all listen on port 162.
This will allow me to run multiple replicas on the same node so that I can do rolling updates.
The text was updated successfully, but these errors were encountered:
I did find this implementation, but I don't really know Go, so I can't say whether it's good or not:
sleepinggenius2@ae781f4
Sorry, something went wrong.
Hi @loganmc10 , seems like a nice feature. Will take a shot at implementing this
No branches or pull requests
Would it be possible to enable the use of SO_REUSEPORT when listening for SNMP traps?
I run a single-node Kubernetes cluster. I'd like to run multiple copies of Telegraf, each listening for traps, but they all listen on port 162.
This will allow me to run multiple replicas on the same node so that I can do rolling updates.
The text was updated successfully, but these errors were encountered: