From c79ce9e3de9487f313e7323b115c167f9620edf4 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Sat, 14 Nov 2026 12:25:03 +0000 Subject: [PATCH] docs: A new Prometheus metric `tendermint_p2p_known_addresses` was added to track the number of distinct peers with a known address (connected peers plus those learned via PEX). (sei-protocol/sei-chain#4520) --- node/advanced-config-monitoring.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/node/advanced-config-monitoring.mdx b/node/advanced-config-monitoring.mdx index 8ecf662..9985984 100644 --- a/node/advanced-config-monitoring.mdx +++ b/node/advanced-config-monitoring.mdx @@ -541,6 +541,9 @@ The `tendermint` namespace also has these subsystems: | `tendermint_internal_autobahn_data_*` | Autobahn data metrics: `latency` (time from the production of a resource to each stage, with `resource` and `stage` labels), `next_block` (the next block to process in each stage), `gas_used` (gas used by executed blocks), and `tx_size` (size of executed transactions in bytes). | | `tendermint_internal_p2p_mux_*` | p2p mux stream metrics: the stream `latency`, the number of open streams (`in_flight`), and the per-stream counters `send_msgs`, `recv_msgs`, `send_bytes`, and `recv_bytes`. These metrics have `role` and `kind` labels. | + +The p2p subsystem also exposes `tendermint_p2p_known_addresses`, a gauge that reports the number of distinct peers with a known address: connected peers plus those learned via PEX. Like `tendermint_p2p_peers`, it is published at router construction and refreshed every 10 seconds. + ## EVM RPC OpenTelemetry metrics The EVM RPC layer emits OpenTelemetry metrics through the process-wide `MeterProvider` (for example, a Prometheus exporter). It emits these metrics in parallel with the legacy `sei_*` metrics, so you can migrate dashboards incrementally.