Skip to content

Expose cumulative tx bytes as a Prometheus metric#6536

Merged
dnadales merged 2 commits intoleios-prototypefrom
dnadales/cumulative-tx-bytes-metric
Apr 21, 2026
Merged

Expose cumulative tx bytes as a Prometheus metric#6536
dnadales merged 2 commits intoleios-prototypefrom
dnadales/cumulative-tx-bytes-metric

Conversation

@dnadales
Copy link
Copy Markdown
Member

, ("delegMapSize", "Delegation map size")
[ ("utxoSize", "UTxO set size")
, ("delegMapSize", "Delegation map size")
, ("cumulativeTxBytes", "Cumulative transaction bytes on the selected chain")
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Add ledgerCumulativeTxBytes to LedgerQueries and wire it through
LedgerMetrics so that the periodic ledger metrics trace emits an
IntM "cumulativeTxBytes" gauge.

This creates a Prometheus metric cardano_node_metrics_cumulativeTxBytes_int
that can be used with rate() to compute confirmed tx throughput (txkB/s).

The field is read from shelleyCumulativeTxBytes on the ShelleyLedgerState
(added in ouroboros-consensus on the cumulative-tx-size branch). Byron
returns 0.

Picks up shelleyCumulativeTxBytes, the new top-level field on
ShelleyLedgerState that tracks cumulative transaction bytes on the
selected chain.
@dnadales dnadales force-pushed the dnadales/cumulative-tx-bytes-metric branch from 2649cc5 to 987d6b2 Compare April 21, 2026 23:43
ouroboros-consensus#1988 has merged, so point the SRP at the tip of
leios-prototype
@dnadales dnadales force-pushed the dnadales/cumulative-tx-bytes-metric branch from 987d6b2 to a9ae633 Compare April 21, 2026 23:45
@dnadales dnadales merged commit 45bc900 into leios-prototype Apr 21, 2026
7 of 13 checks passed
@dnadales dnadales deleted the dnadales/cumulative-tx-bytes-metric branch April 21, 2026 23:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants