On this page
Metrics & Monitoring
Brixs nodes expose a native Prometheus metrics endpoint on port 9100. Robust monitoring is required for production deployments.
Key Metrics to Monitor
P2P Peers
Monitor `brixs_network_peers` to ensure you remain connected to the gossip network.
Epoch Lag
Monitor `brixs_consensus_epoch` to ensure your node is perfectly synced.
DB Size
Monitor `brixs_db_size_bytes` to plan for storage volume expansions.
Alert Triage Volume
Setting up Alerts
Phase 1: Engine Initialization
The first phase requires a comprehensive setup of the execution environment. The Brixs Native EVM initializes the state and establishes secure connections with the P2P network. This ensures that when the DPoS Sequencer begins proposing blocks, there are no bottlenecks in transaction ingestion.
Transactions are ordered securely by the Encrypted Mempool to prevent MEV. The Native EVM processes transactions while the ZK-SNARK Prover Engine generates validity proofs. Once processed, the Sequencer commits the block to the Ethereum L1, achieving Rollup Finality and inheriting Ethereum's cryptographic security.