You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
danielnelson
added
bug
unexpected problem or unintended behavior
docs
Issues related to Telegraf documentation and configuration descriptions
labels
Feb 20, 2020
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.
There's some other agents on my systems that a few times a day call iptables without -n to avoid DNS reverse resolution
Don't you want to call iptables with-n to avoid dns resolution? Seems like that's why it's taking minutes to complete (or did you mean they're intentionally running it without -n to gather names? I guess you can read that sentence two different ways).
Is it possible to have gather errors tagged by input?
This would be handy.
The text was updated successfully, but these errors were encountered: