-
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
Improve SNMP plugin error logging #1814
Comments
Agree. Its a trivial change. I'll try to get to it tonight, and see if there's any other errors which can benefit from more context. |
It would also be helpfull if the errorlog would contain the specific SNMP instance and/or device that is failing. Every once in a while I get a "snmp collection took longer than collection interval", but it is hard to find out which instance or device produces the error with 53 SNMP instances polling 400+ devices. |
@Ebrink The I will check how more verbose output can be provided there. |
@phemmer For the OID, I think it would suffice to append the string to the message as |
I have a local branch where I've done most of the work on this, just need to finish it up (mostly just make sure I didn't miss anything). I'll see if I can get to it this weekend. |
Sorry for the huge delay on this. For as trivial as a change as it was, I should have finished it up long ago :-( Anyway, PR is up (#2220). However the PR does not address the most recent comment (the "took longer to collect than ..."). This error comes from telegraf core, and not the snmp plugin. Trying to address this could be tricky as inputs don't really have a standard "name" identifier. The only way I can think to address it is to add the line number of the config where the input begins. |
It would help with troubleshooting if errors mentioned particular failing OID's in the SNMP plugin.
E.g. appending the OID that failed to the error log would help identify problematic ones: https://github.com/influxdata/telegraf/blob/master/plugins/inputs/snmp/snmp.go#L448
The text was updated successfully, but these errors were encountered: