The Zcash Basis is happy to announce Zebra 4.1.0a launch targeted on increasing observability with complete Prometheus metrics and Grafana dashboards, whereas strengthening mempool compliance with zcashd. This launch incorporates no breaking modifications for node operators.
What’s New in 4.1.0
Observability: See Inside Your Node
Zebra 4.1.0 considerably expands monitoring capabilities to offer operators deep visibility into node well being, efficiency, and bottlenecks. We wish to carry Zebra’s observability on par with different fashionable node shopper implementations, so we recognized important gaps and stuffed them.
Worth Pool, RPC, and Peer Metrics
We are actually exposing new Prometheus metrics throughout three key areas:
Worth Pool Monitoring
- Pool balances: clear, sprout, sapling, orchard, and deferred
- Complete chain provide
RPC Efficiency Metrics
- Request counts by methodology and standing
- Latency histograms for per-method efficiency evaluation
- Energetic request gauge to trace concurrent load
- Error monitoring by methodology and error code
To assist operators to detect RPC bottlenecks and shopper points.
Peer Well being Metrics
- Handshake latency histograms to determine gradual peer connections
- Failure monitoring by cause (timeout, invalid signature, protocol mismatch, and so forth.)
These are important for understanding community well being.
Efficiency Histograms
We added period metrics to 3 important efficiency areas:
Sync Pipeline Latency
sync.stage.duration_seconds:Observe time spent inobtain_tipsandextend_tipslevelssync.block.obtain.duration_seconds:Per-block obtain latencysync.block.confirm.duration_seconds:Per-block verification time
To determine the reason for delays; community climate, block verification, or database operations.
Consensus Batch Verification
zebra.consensus.batch.duration_seconds{verifier,consequence}:Detailed period histograms, protectinged25519,redjubjub,redpallas,halo2andgroth16_saplingverifiers
To allow evaluation of proof verification efficiency, submit checkpoint synchronization.
RocksDB Database Metrics
- Complete disk and reside knowledge sizes (up to date each 30 seconds)
memtablereminiscence utilization- Breakdown of disk and reminiscence utilization per column household
To know database progress and reminiscence stress throughout sync.
RocksDB I/O and Sync Distance
Lastly, we targeted on observability within the state layer and chain synchronization progress
Sync Distance Metrics
sync.estimated_distance_to_tip:What number of blocks behind the community tipsync.estimated_network_tip_height:Estimated present community top
These metrics are important for detecting stalled nodes and monitoring catch-up progress.
RocksDB I/O Efficiency
zebra.state.rocksdb.batch_commit.duration_seconds:Write latency histograms
This permits detection of database bottlenecks throughout heavy sync load.
We’re additionally now measuring bytes pending compaction in addition to the lively compaction standing.
Documentation
For detailed documentation on configuration, deployment, and superior options, go to the Zebra E-book.
Get Concerned
Zebra is an open-source undertaking and we welcome contributions from the neighborhood:
Zebra is the Zcash Basis’s impartial, consensus-compatible implementation of a Zcash node, written in Rust for efficiency and security.

