Skip to main content

ISBE Network Monitoring Dashboards

The ISBE network has monitoring dashboards designed so that technical teams can consult essential information about the network status and their regular nodes.
This information comes from internal metrics systems (Prometheus, Grafana, or equivalents depending on the environment).

The goal of this guide is to explain what each use case can consult and what information is relevant to validate the operation of their node or the network in general.

1. Access to Monitoring Dashboards​

Each environment (dev, pre, pro) may have independent dashboards.
The ISBE team will provide the corresponding links for each use case when its environment is active.

URLs:

  • ISBE-DEV: https://grafana.dev.portal.redisbe.com
  • ISBE-PRE: https://grafana.pre.portal.redisbe.com
  • ISBE-PRO: https://grafana.portal.redisbe.com

Access may be protected by username/password or IP whitelisting as appropriate.

2. Available Dashboards​

Dashboards are typically grouped into four categories:

2.1. General Network Dashboard​

Includes global metrics:

  • Real-time block height
  • Average block time
  • Active validator nodes
  • IBFT consensus status
  • Critical alerts (if applicable)

This dashboard allows identifying at a glance if the network is stable.

2.2. Regular Node Dashboard​

Allows seeing relevant information for each regular node connected to the network:

  • Peer count
  • Latency
  • Rate of processed transactions
  • Common error logs
  • RPC status
  • CPU/RAM usage (if the node is managed by ISBE)

Nodes operated by the use cases themselves will only show metrics if the participant has configured the corresponding exporters.

2.3. Block and Transaction Dashboard​

Useful for developers:

  • Number of transactions per block
  • Confirmation times
  • Detected on-chain events
  • Contracts with the highest volume of activity
  • Historical gas usage

Helps to detect:

  • Transaction retries
  • Blocks with anomalous failures
  • Excessive gas usage by a contract

2.4. Alarm Dashboard (if enabled)​

Includes:

  • Stagnant height alerts
  • Missing peer alerts
  • Abnormal block time variation alerts
  • Validator node down alerts

In many cases, this dashboard is internal and not visible to use cases, but ISBE notifies of relevant incidents.

3. What Use Cases Should Review​

Teams do not need to monitor the entire network; they should only review:

For nodes provided by ISBE:​

  • RPC status
  • Peer count
  • Block time
  • Block height
  • Alerts related to their node

For nodes deployed by the team itself:​

  • Host CPU and RAM
  • Availability of port 30303/tcp
  • Free disk in the data-path
  • Relevant Besu node logs

These metrics allow detecting 90% of typical problems.

4. Quick Analysis Examples​

Case A: My node shows 0 peers​

Interpretation:

  • Not permissioned or <NODO_IP> does not match.
  • Port 30303/tcp blocked. Actions:
  • Check net_peerCount.
  • Verify firewall.
  • Review data sent in the permissioning request.

Case B: The network shows block time > 5 seconds​

Interpretation:

  • Possible incident in validators.
  • Congestion or network update. Actions:
  • Verify in Blockscout if it affects everyone.
  • Escalate to ISBE if it persists.

Case C: Events are not arriving via WebSocket​

Interpretation:

  • Node with high latency.
  • WebSocket disconnected. Actions:
  • Check regular node dashboard.
  • Restart service if it is an own node.

5. Summary​

DashboardPurposeRelevance for Use Cases
General NetworkGlobal state, block timeHigh
Regular NodesRPC and P2P healthVery high
Blocks and TransactionsOn-chain activityMedium
AlarmsCritical incidentsHigh (if accessible)

The dashboards allow participants to detect common problems autonomously and validate the behavior of their deployments without needing internal access to the infrastructure.