feat: add base node responsiveness monitoring #6715
Merged
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.
Description
Added a base node responsiveness monitoring command, which can be executed from within the base node console or directly from the command line. A peer's specific public addresses can be tested if combined with a script that removes the peer_db and command-line options to isolate the base node. If instructed to exit after the test, the base node will either exit with a process exit status code of
0
indicating success or1
indicating failure. Test results can also be written to a file.Motivation and Context
Sometimes it is not enough to be able to dial a peer to know if it is responsive, it should also respond with pongs when pings are sent. This knowledge is especially useful when evaluating status of seed peers.
How Has This Been Tested?
System-level testing
What process can a PR reviewer use to test or verify this change?
System-level testing
Code review
Breaking Changes