Additional logging in cases one or multiple rpc endpoints become unavailable #1448
Description
Description
Additional logging in cases one or multiple rpc endpoints become unavailable.
Problem Statement
At the moment relay does not explicitly log which chain/rpc endpoint is affected. Example error log due to rate limits being hit:
2025-10-01 14:29:54.865
/app/src/chains.rs:435:33
2025-10-01 14:29:54.865
Location:
2025-10-01 14:29:54.865
2025-10-01 14:29:54.865
HTTP error: 429 Too Many Requests
2025-10-01 14:29:54.865
Caused by:
2025-10-01 14:29:54.865
2025-10-01 14:29:54.865
Error: HTTP error: 429 Too Many Requests
2025-10-01 14:29:54.857
2025-10-01T06:29:54.857867Z INFO alloy_pubsub::service: Pubsub service request channel closed. Shutting down.
2025-10-01 14:29:54.853
2025-10-01T06:29:54.853721Z DEBUG alloy_rpc_client::call: sending request method=eth_getBlockByNumber id=5
2025-10-01 14:29:54.850
2025-10-01T06:29:54.850349Z DEBUG poller{method=eth_getBlockByNumber}:ReqwestTransport{url=https://mainnet-preconf.base.org/}: hyper_util::client::legacy::connect::http: connected to 104.18.40.153:443
2025-10-01 14:29:54.849
2025-10-01T06:29:54.849754Z DEBUG poller{method=eth_getBlockByNumber}:ReqwestTransport{url=https://mainnet-preconf.base.org/}: hyper_util::client::legacy::connect::http: connecting to 104.18.40.153:443
2025-10-01 14:29:54.844
2025-10-01T06:29:54.844756Z DEBUG poller{method=eth_getBlockByNumber}:ReqwestTransport{url=https://mainnet-preconf.base.org/}: reqwest::connect: starting new connection: https://mainnet-preconf.base.org/
2025-10-01 14:29:54.844
2025-10-01T06:29:54.844695Z DEBUG alloy_rpc_client::call: sending request method=eth_getBlockByNumber id=4
2025-10-01 14:29:54.844
2025-10-01T06:29:54.844683Z DEBUG alloy_rpc_client::call: sending request method=eth_chainId id=3
2025-10-01 14:29:54.844
Implementation Hints
User story
- Easier troubleshooting