Repository navigation
Conversation
Contributor
|
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
inputs.snmpkeeps one connection per agent for the life of the process and only ever reconnects when the socket is gone. For SNMPv3 that connection also holds the engine ID discovered on the first request. When the agent restarts with a new engine ID, it answers with an unauthenticatedusmStatsUnknownEngineIDsreport, which gosnmp rejects as not authentic before it can act on it, so every gather fails until Telegraf is restarted. The same stale connection keeps a hostname resolved to an address that no longer answers.This closes and drops the cached connection when gathering from an agent fails, so the next interval sets up a fresh one and runs the engine discovery again. That is what a restart does today. It applies to all SNMP versions as it also re-resolves the agent address, and the cost is one socket and, for SNMPv3, one discovery exchange per failed interval.
Closeis added to thesnmp.Connectioninterface for this, the wrapper already provides it.Checklist
Related issues
resolves #19816
related to #16880