Hyperlane
Project documentation
https://docs.hyperlane.xyz/docs/operate/validators/run-validators
Monitoring
We have a Hyperlane dashboard located here for production.
Logs are in docker can be access with docker logs -f hyperlane-ethereum-validator.
Maintenance
The hyperlane validator is deployed via docker and controlled by the usual docker commands,
e.g. docker start hyperlane-ethereum-validator.
The docker container is managed by a docker compose file stored in ansible. Configuration of the validator is controlled via a config file stored in ansible and installed at /home/docker/hyperlane/bin/ethereum/config.json. The per environment values are injected in to these files via ansible.
S3 Buckets
Hyperlane requires a public accessible S3 bucket for network participants to access the validated, details:
- IAM user:
hyperlane-validator-ethereum - S3 bucket:
hyperlane-validator-signatures-prod-01-ethereum
The Access key and Access secret is stored in ansible.
Alerts
| Alert Name | Description | Action |
|---|---|---|
| Incorrect number of hyperlane instances | We expect one instance running and we have found more or fewer | Find which instances should/should not be running and start/stop as appropriate. |
| Hyperlane block height not increased in 30 mins | The indexed block height has not changed in 30 mins. | This could indicate an issue with the associated RPC or connectivity to it. Check the logs and diagnose the problem (may need to restart the container). |
| Hyperlane warnings have increased by more than 2 in the last 10 mins | Unexpected increase in warnings. | Check the logs and investigate the warnings. |
| Hyperlane errors have increased by more than 1 in the last 10 mins | Unexpected increase in errors. | Check the logs and investigate the errors. |