-
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
Telegraf 1.22.0 / GoSNMP.Conn is missing #10890
Comments
This seems like a duplicate of #10554 |
Hi @Hipska , yes exactly. 1.20.4 was the last good version in regards to this issue. |
Okay, and what are your settings for |
# Polling interval
interval = "60s"
# Timeout for each SNMP query.
timeout = "10s"
# Number of retries to attempt within timeout.
retries = 3
# SNMP version
version = 2 and yes, TCP |
Okay, I was suspecting that. I think I can fix it. |
@bondskin can you please confirm that the linked PR fixes your issue!? |
Hi @srebhan , this is looking exceptionally great! it took 1-2 min until the hostnames of the SNMP clients were correctly resolved after restarting the new Telegraf (PR) instance
but then everything is working fine, no more errors and all clients are delivering results |
Hi @Hipska , thanks for asking, much appreciated. |
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf, 1.22.0, Raspberry Pi 4
Docker
No response
Steps to reproduce
...
Expected behavior
no errors and values are correctly captured.
Actual behavior
For some devices, it produces errors and no SNMP values are being captured
Additional info
no issue with telegraf_1.20.4-1_armhf.deb
The text was updated successfully, but these errors were encountered: