Client information exposed by the tBTC v2 staking client.
The client exposes metrics and diagnostics on a configurable port (default:
The data can be consumed by Prometheus to monitor the state of a node.
The client exposes the following metrics:
- connected peers count,
- connected bootstraps count,
- Ethereum client connectivity status (if a simple read-only CALL can be executed).
Metrics are enabled once the client starts. It is possible to customize the port at which metrics endpoint is exposed as well as the frequency with which the metrics are collected.
Exposed metrics contain the value and timestamp at which they were collected.
Example metrics endpoint call result:
$ curl localhost:9601/metrics
# TYPE connected_peers_count gauge
connected_peers_count 108 1623235129569
# TYPE connected_bootstrap_count gauge
connected_bootstrap_count 10 1623235129569
# TYPE eth_connectivity gauge
eth_connectivity 1 1623235129789
The client exposes the following diagnostics:
- list of connected peers along with their network id and Ethereum operator address,
- information about the client’s network id and Ethereum operator address.
Diagnostics are enabled once the client starts. It is possible to customize the port at which diagnostics endpoint is exposed.
Example diagnostics endpoint call result:
$ curl localhost:9601/diagnostics