You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, lighthouse das branch provides specific metrics;
Full runtime of data column sidecars gossip verification (counter)
Number of data column sidecars verified for gossip (counter)
Total count of reconstructed columns (counter)
Time taken to reconstruct columns (histogram)
Time taken to compute data column sidecar, including cells, proofs and inclusion proof (histogram)
Time taken to verify data_column sidecar inclusion proof (histogram)
Runtime of batched data column kzg verification (histogram)
Runtime of single data column kzg verification (histogram)
Counts on custody could be useful. column_index as labels?
Total count of columns in custody (counter)
Gossipsub domain metrics will be very handy imo. Should contain topic data_column_sidecar_{subnet_id} as labels;
Number of gossip messages sent to each topic (counter)
Number of bytes sent to each topic (counter)
Number of gossip messages received from each topic (including duplicates) (counter)
Number of bytes received from each topic (including duplicates) (counter)
Number of gossip messages received from each topic (deduplicated) (counter)
Number of bytes received from each topic (deduplicated) (counter)
Req/Resp domain metrics would be nice to have. Should contain protocol ID /eth2/beacon_chain/req/data_column_sidecars_by_root/1/ and /eth2/beacon_chain/req/data_column_sidecars_by_range/1/ as labels;
Number of requests sent (counter)
Number of requests received (counter)
Number of responses sent (counter)
Number of responses bytes sent (counter)
Number of responses received (counter)
Number of responses bytes received (counter)
The text was updated successfully, but these errors were encountered:
For example, lighthouse das branch provides specific metrics;
Counts on custody could be useful. column_index as labels?
Gossipsub domain metrics will be very handy imo. Should contain topic data_column_sidecar_{subnet_id} as labels;
Req/Resp domain metrics would be nice to have. Should contain protocol ID /eth2/beacon_chain/req/data_column_sidecars_by_root/1/ and /eth2/beacon_chain/req/data_column_sidecars_by_range/1/ as labels;
The text was updated successfully, but these errors were encountered: