collectors: tolerate DeadlineExceeded in PeerCollector#126
Merged
Roasbeef merged 1 commit intolightninglabs:masterfrom Feb 20, 2026
Merged
Conversation
ChainCollector and ChannelsCollector already handle gRPC deadline exceeded errors gracefully by logging and skipping the scrape cycle rather than crashing. PeerCollector was missing this same guard, causing lndmon to exit whenever lnd was temporarily slow to respond to a ListPeers call.
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
2 participants
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.
PeerCollectorwas missing theIsDeadlineExceededguard thatChainCollectorandChannelsCollectoralready have, causing lndmonto crash whenever lnd was temporarily slow to respond to
ListPeers.This makes the behaviour consistent across all three collectors.