Skip to content

agent: Add invalid peer enodes to disconnect log message#85

Merged
shazow merged 1 commit intomasterfrom
strictpeers-cleanup
Nov 15, 2019
Merged

agent: Add invalid peer enodes to disconnect log message#85
shazow merged 1 commit intomasterfrom
strictpeers-cleanup

Conversation

@shazow
Copy link
Copy Markdown
Member

@shazow shazow commented Nov 15, 2019

Adding some better logging to help debug in the future.

@ryanschneider Can you think of anything else that would help in this scenario?

@shazow shazow requested a review from ryanschneider November 15, 2019 15:05
Copy link
Copy Markdown
Collaborator

@ryanschneider ryanschneider left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, only thing I could think that might be helpful is the list of ActivePeers, but I think that makes the log message way to long and spammy, so maybe a later feature would be to add dynamic verbosity, possibly using the debug.vmodule RPC implementation from geth or something similar.

@shazow
Copy link
Copy Markdown
Member Author

shazow commented Nov 15, 2019

@ryanschneider I've been thinking of exposing local/private-only RPCs, or maybe a /health endpoint for agents that could include this info. What do you think?

@shazow
Copy link
Copy Markdown
Member Author

shazow commented Nov 15, 2019

Opened #86 for brainstorming the health endpoint.

@shazow shazow merged commit 220d402 into master Nov 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants