-
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
Add lock option to the IPtables input plugin #2201
Conversation
is there a reason we wouldn't want to always use the lock feature? |
The "-w" option was added to the 1.4.20 version of IPtables in august 2013 (https://www.netfilter.org/projects/iptables/files/changes-iptables-1.4.20.txt). Maybe this feature should be kept optional for compatibility reasons, in the case where someone would be using Telegraf on a system shipped with an IPtables version older than 1.4.20 ? |
ok, fair enough 👍 |
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.
documentation needs cleaning up and tweaking
use_sudo = false | ||
## Setting 'use_lock' to true will run iptables with xtables lock support. | ||
## This option is useful to avoid iptables concurrency errors when running multiple instances of this plugin. |
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.
limit line length to 80 chars and mention that use_lock
simply adds the -w
option to the iptables
Doc cleaning
Doc has been cleaned up |
* Update README.md * Add lock support to the IPtables input plugin * Update iptables.go Doc cleaning
* Update README.md * Add lock support to the IPtables input plugin * Update iptables.go Doc cleaning
This PR adds IPtables lock support to the input plugin, related to #2144
Required for all PRs: