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
Copy file name to clipboardExpand all lines: metrics.md
-29Lines changed: 0 additions & 29 deletions
Original file line number
Diff line number
Diff line change
@@ -50,35 +50,6 @@ The following metrics are proposed to be added to clients for PeerDAS monitoring
50
50
|`beacon_kzg_verification_data_column_batch_seconds`| Histogram | Runtime of batched data column kzg verification | On batched data column kzg verification |
51
51
|`beacon_custody_columns_count_total`| Counter | Total count of columns in custody within the data availability boundary | On custody collecting and verification |
52
52
53
-
#### Gossipsub metrics
54
-
Gossipsub domain metrics should contain topic `data_column_sidecar_{subnet_id}` as labels.
55
-
56
-
| Name | Metric type | Usage | Sample collection event |
|`gossipsub_topic_msg_sent_counts_total`| Counter | Number of gossip messages sent to each topic | On sending a message over a topic |
59
-
|`gossipsub_topic_msg_sent_bytes_total`| Counter | Number of bytes sent to each topic | On sending a message over a topic |
60
-
|`gossipsub_topic_msg_recv_counts_unfiltered_total`| Counter | Number of gossip messages received from each topic (including duplicates) | On receiving a message from a topic including duplicates|
61
-
|`gossipsub_topic_msg_recv_bytes_unfiltered_total`| Counter | Number of bytes received from each topic (including duplicates) | On receiving a message from a topic including duplicates |
62
-
|`gossipsub_topic_msg_recv_counts_total`| Counter | Number of gossip messages received from each topic (deduplicated) | On receiving a message from a topic deduplicated |
63
-
|`gossipsub_topic_msg_recv_bytes_total`| Counter | Number of bytes received from each topic (deduplicated) | On receiving a message from a topic deduplicated |
64
-
65
-
66
-
#### Req/Resp metrics
67
-
68
-
Req/Resp domain metrics 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.
69
-
70
-
| Name | Metric type | Usage | Sample collection event |
|`libp2p_rpc_requests_sent_total`| Counter | Number of requests sent | On propagating an RPC request |
73
-
|`libp2p_rpc_requests_bytes_sent_total`| Counter | Number of requests bytes sent | On propagating an RPC request |
74
-
|`libp2p_rpc_requests_received_total`| Counter | Number of requests received | On receiving an RPC request |
75
-
|`libp2p_rpc_requests_bytes_received_total`| Counter | Number of requests bytes received | On receiving an RPC request |
76
-
|`libp2p_rpc_responses_sent_total`| Counter | Number of responses sent | On propagating an RPC response |
77
-
|`libp2p_rpc_responses_bytes_sent_total`| Counter | Number of responses bytes sent | On propagating an RPC response |
78
-
|`libp2p_rpc_responses_received_total`| Counter | Number of responses received | On receiving an RPC response |
79
-
|`libp2p_rpc_responses_bytes_received_total`| Counter | Number of responses bytes received | On receiving an RPC response |
80
-
81
-
82
53
### Additional Metrics
83
54
84
55
The following are proposed metrics to be added to clients. This list is _not_ stable and is subject to drastic changes, deletions, and additions. The additional metric list is being
0 commit comments