feat(metrics): instrument bitswap usage #13221
Merged
Conversation
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
Only enabled with LOTUS_ENABLE_MESSAGE_FETCH_INSTRUMENTATION=1 due to minor additional blockstore index usage.
d24b5f2 to
21ae17b
Compare
ZenGround0
approved these changes
Jul 18, 2025
8 tasks
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.
Only enabled with LOTUS_ENABLE_MESSAGE_FETCH_INSTRUMENTATION=1 due to minor additional blockstore index usage.
Looks a little like this during normal operation:
It's difficult to show this from Prometheus well but bitswap usage seems to be fairly rare, we're able to get most messages from pubsub. The occasional fetches make it look like it hovers a bit above 95% but it's very patchy.
The timings aren't quite as interesting as hoped due to the infrequency but they do show some interesting things about the local blockstore, just isolated to messages.