Closed turuslan closed 2 years ago
Add more metrics like lotus/metrics/metrics.go which can be collected by our node.
Our node already has prometheus metrics for counter and gauge. Maybe we need to implement buckets for histogram and summary. Integrating external library may be an option too.
UPD. Didn't find summary metrics usage in lotus yet.
UPD. Switching to prometheus-cpp.
not implemented:
info{commit version}
peer/count
block/failure
block/success
block/validation_ms
vm/applyblocks_total_ms
message/failure
message/success
message/validation_ms
mpool/getnonce_ms
mpool/getbalance_ms
mpool/addts_ms
mpool/add_ms
mpool/push_ms
api/request_duration_ms {endpoint=MpoolPushMessage}
block/delay
SyncSubmitBlock
pubsub/published
pubsub/delivered
pubsub/rejected
pubsub/duplicate
pubsub/recv_rpc
pubsub/send_rpc
pubsub/drop_rpc
Add more metrics like lotus/metrics/metrics.go which can be collected by our node.
Our node already has prometheus metrics for counter and gauge. Maybe we need to implement buckets for histogram and summary. Integrating external library may be an option too.
UPD. Didn't find summary metrics usage in lotus yet.
UPD. Switching to prometheus-cpp.
not implemented:
info{commit version}
532.
peer/count
block/failure
, *block/success
539.
block/validation_ms
vm/applyblocks_total_ms
).539.
message/failure
,message/success
,message/validation_ms
mpool/getnonce_ms
,mpool/getbalance_ms
,mpool/addts_ms
,mpool/add_ms
mpool/push_ms
api/request_duration_ms {endpoint=MpoolPushMessage}
is used instead.block/delay
SyncSubmitBlock
and/or pubsub?pubsub/published
,pubsub/delivered
,pubsub/rejected
,pubsub/duplicate
,pubsub/recv_rpc
,pubsub/send_rpc
,pubsub/drop_rpc