-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture information on the list transport protocols supported by SPs #30
Comments
masih
added a commit
that referenced
this issue
Jul 7, 2023
Expand metrics and data collection to include: * stats on SP markets protocol * total number of Boost SPs * total Boost raw and quality adjusted power * state miner power for all SPs * total SPs with min power * list of transport protocols exposed by a SP queried via `/fil/retrieval/transports/1.0.0` * stats on number of SPs per transport protocol. * stats on agent version which can be used to see what software SPs run. Change the API server filtering by peer ID to also consider peer IDs that may be listed under transports. Fixes #30 #25
masih
added a commit
that referenced
this issue
Jul 7, 2023
Expand metrics and data collection to include: * stats on SP markets protocol * total number of Boost SPs * total Boost raw and quality adjusted power * state miner power for all SPs * total SPs with min power * list of transport protocols exposed by a SP queried via `/fil/retrieval/transports/1.0.0` * stats on number of SPs per transport protocol. * stats on agent version which can be used to see what software SPs run. Change the API server filtering by peer ID to also consider peer IDs that may be listed under transports. Fixes #30 #25
masih
added a commit
that referenced
this issue
Jul 7, 2023
Expand metrics and data collection to include: * stats on SP markets protocol * total number of Boost SPs * total Boost raw and quality adjusted power * state miner power for all SPs * total SPs with min power * list of transport protocols exposed by a SP queried via `/fil/retrieval/transports/1.0.0` * stats on number of SPs per transport protocol. * stats on agent version which can be used to see what software SPs run. Change the API server filtering by peer ID to also consider peer IDs that may be listed under transports. Fixes #30 #25
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a SP supports
/fil/retrieval/transports/1.0.0
, query it and capture information on the transport protocols that it offers.This would then expose a set of other peer IDs that a SP might be using which should also be captured.
See:
https://github.com/filecoin-project/boost/blob/main/cmd/boostx/stats_cmd.go#L159-L168
The text was updated successfully, but these errors were encountered: