Skip to main content
For technical support, please post your questions on the Boundless Discussions Forum.

​
Telemetry

The broker includes an optional telemetry service that reports anonymized health and performance metrics. When enabled, this helps the Boundless team identify issues, diagnose bugs, and prioritize improvements across the network. Telemetry is designed to be lightweight and non-intrusive — no sensitive data such as private keys or wallet balances is collected. Telemetry is enabled by default. To opt out, add the following to your broker.toml:
broker.toml
[market]
telemetry_mode = "logsonly"
This switches to local debug logging only, with no data sent to any remote service.

​
Grafana

The Bento / Broker Docker compose stack includes a Grafana instance with some template dashboards. To access them, Grafana is hosted at http://localhost:3000. Default credentials are defined in .env.broker-template as admin:admin.

​
Bento Dashboard

The Bento dashboard connects to the TaskDB PostgreSQL instance to get live data for the status of different proofs flowing through the proving cluster. It is useful to monitor performance and queue depth.

​
Broker Dashboard

The broker dashboard connects to the broker’s SQLite database to see the status of different orders and batches moving through the broker’s workflows.

​
Onchain

The recommended method to monitor your broker’s activity and health is via the Boundless Explorer.

​
Balances

For smooth broker operation, it is critical to monitor both your hot wallet balance of ETH and the market balance of collateral. If your broker runs out of ETH balance, it will be unable to cover gas costs for transactions and as such it will be unable to lock and fulfill orders. If you running low of collateral funds on the broker account on the market contract, the broker will be unable to lock-in orders with higher collateral values. It is strongly recommended to keep your market balance above the broker’s configured max_collateral parameter (which may be specified in ZKC or USD — check your broker.toml to see the current value).

​
Broker Logs

Unrecoverable errors may cause the broker process to exit. Make sure to have a restart policy on the container. As the software matures, more errors should become recoverable.
The broker logs are the very helpful for monitoring broker interactions with the market. It is designed with the intention that DEBUG / INFO / WARN log should not require manual intervention, but anything logged at an ERROR level should be a cause of concern. To see a live stream of the broker logs:
Terminal
docker compose logs -f broker
and to see the last 100 lines of the logs:
Terminal
docker compose logs --tail=100 broker