# Monitor validators

If you use the Clique or IBFT 2.0 Proof of Authority (PoA) consensus protocols, determine whether all validators are proposing blocks to identify possible network problems.

Enable monitoring of validators in the command line by specifying the POA metrics category and optionally specifying the number of recently added blocks to check.

Example

besu --metrics-enabled --metrics-categories=POA --plugin-metrics-recent-block-count=50

The command line statement:

## Viewing metrics

1. Configure and run Prometheus as described for Hyperledger Besu.

2. Open a web browser to http://localhost:9090 to view the Prometheus graphical interface.

3. Choose Graph from the menu bar and click the Console tab below.

4. From the Insert metric at cursor drop-down, select one of the following metrics, and click Execute. The values are displayed.

Name Metric Type Definition JSON-RPC Equivalent
plus_poa_ibft_recent_signed_count Gauge Number of times this node was a block signer in the last n blocks, where n is the value specified for --plugin-metrics-recent-block-count None
plus_poa_ibft_rounds_for_latest_block Gauge Number of rounds required to import the latest block None
plus_poa_ibft_unique_recent_signers Gauge Number of unique signers in the last n blocks, where n is the value specified for --plugin-metrics-recent-block-count None
plus_poa_recent_proposer_count Gauge Number of unique validators proposing blocks in the last n blocks, where n is the value specified for --plugin-metrics-recent-block-proposer-count clique_getSignerMetrics, ibft_getSignerMetrics
plus_poa_recently_proposed_block_count Gauge Number of times this validator proposed an accepted block in the last n blocks, where n is the value specified for --plugin-metrics-recent-block-count clique_getSignerMetrics, ibft_getSignerMetrics
plus_poa_validator_count_current Gauge Number of validators currently defined clique_getSignerMetrics, ibft_getSignerMetrics