-
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
internal_gather - include errors field #7057
Comments
I think this is only a documentation bug, the
|
Indeed. However something is not quite right. I'm having some problems with the iptables plugin, due to locking. There's some other agents on my systems that a few times a day call iptables without -n to avoid DNS reverse resolution. On systems with very large rule sets, this is an issue, because iptables -L can take minutes to finish. If I have the plugin running every 60 seconds, it will fail while that other agent is doing that. Of course that's not the plugin fault, but I would expect to see errors > 0 for the iptables input on those occasions, but no, it's always 0. However, the aggregated errors counts is updated in internal_agent.gather_errors for the affected hosts. Using 13.3. |
Don't you want to call iptables with In the mean time, I'll dig into the errors issue. |
Is it possible to have gather errors tagged by input?
This would be handy.
The text was updated successfully, but these errors were encountered: