Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions node/advanced-config-monitoring.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -541,7 +541,10 @@
| `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

Check warning on line 547 in node/advanced-config-monitoring.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/advanced-config-monitoring.mdx#L547

Use sentence case for headings: '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.

Expand Down Expand Up @@ -577,11 +580,11 @@

Before the legacy metrics are removed, update your Prometheus and Grafana dashboards to use the `evmrpc_*` metrics. The latency unit changed from milliseconds (`sei_rpc_request_latency_ms`) to seconds (`evmrpc_request_latency_seconds`). Adjust any thresholds and panel formatting to match.

## FlatKV OpenTelemetry metrics

Check warning on line 583 in node/advanced-config-monitoring.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/advanced-config-monitoring.mdx#L583

Use sentence case for headings: 'FlatKV OpenTelemetry metrics'.

The FlatKV state store emits OpenTelemetry metrics through the process-wide `MeterProvider` (for example, a Prometheus exporter). With these metrics, you can observe commit throughput, catchup progress, snapshotting, rollbacks, and snapshot imports.

### Available FlatKV metrics

Check warning on line 587 in node/advanced-config-monitoring.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/advanced-config-monitoring.mdx#L587

Use sentence case for headings: 'Available FlatKV metrics'.

| Metric | Type | Description |
| --- | --- | --- |
Expand Down Expand Up @@ -671,11 +674,11 @@
sc-hash-logger-enable = false
```

## LittDB OpenTelemetry metrics

Check warning on line 677 in node/advanced-config-monitoring.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/advanced-config-monitoring.mdx#L677

Use sentence case for headings: 'LittDB OpenTelemetry metrics'.

LittDB emits its metrics through the process-wide OpenTelemetry `MeterProvider` instead of a private Prometheus client. If `MetricsEnabled` is `true`, LittDB records its metrics in that provider. By default (`MetricsServeEndpoint = false`), the application that uses LittDB exports the metrics, and LittDB does not start a `/metrics` server. If `MetricsServeEndpoint` is `true`, LittDB serves `/metrics` on `MetricsPort` (default `9101`). LittDB no longer has the `MetricsNamespace` and `MetricsRegistry` config fields, and all metric names use a fixed `litt_` prefix.

### Available LittDB metrics

Check warning on line 681 in node/advanced-config-monitoring.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/advanced-config-monitoring.mdx#L681

Use sentence case for headings: 'Available LittDB metrics'.

| Metric | Type | Unit | Description |
| --- | --- | --- | --- |
Expand Down
Loading