feat(telemetry)_: track peers by shard and origin #5819
Closed
Conversation
This file contains 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
Jenkins Builds
|
adklempner
force-pushed
the
feat/telemetry-peers-shard-origin
branch
from
aa81ecc to
00a9267
Compare
|
same commits merged in #5824 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Periodically calculates number of connected peers per shard and discovery method, reports to telemetry
If telemetry is enabled, starts an additional go routine in
wakuv2.Start()which periodically (currently set to 10 seconds) gets all connected peers. It iterates through each peer and counts how many were discovered using which method (viawakuPeerStore.Origin(peerId)) and how many peers support which shard ids. These counts are then reported to the telemetry service.Important changes:
Related to status-im/telemetry#21