Difference between revisions of "Proxyd"
Jump to navigation
Jump to search
(→Logs) |
(→Logs) |
||
| Line 25: | Line 25: | ||
* <code>[[error forwarding request to backend]]</code> | * <code>[[error forwarding request to backend]]</code> | ||
* <code>[[Error forwarding RPC batch]]</code> | * <code>[[Error forwarding RPC batch]]</code> | ||
| + | * <code>[[error serving requests]]</code> | ||
* <code>[[error proxying websocket]]</code> | * <code>[[error proxying websocket]]</code> | ||
* <code>[[error writing clientConn message]]</code> | * <code>[[error writing clientConn message]]</code> | ||
| − | + | ||
WARN | WARN | ||
Revision as of 14:06, 23 August 2024
proxyd /etc/proxyd/proxyd.toml
Features:
- Whitelists RPC methods
- Routes RPC methods to groups of backend services
- Load balance requests across backend services
- Automatically retries failed backend requests
- Cache immutable responses from backends
- Provides metrics to measure request latency, error rates
Consensus related:
- Track backend consensus (latest, safe, finalized blocks), peer count and sync state
- Re-write requests and responses to enforce consensus
- Applies rate limiting on a per-sender basis to avoid being bombarded with signed transactions causing a DOS (Denial of Service) of the sequencer (Optimism Censorship Bug Disclosure)
Logs
ERROR
error forwarding request to backendError forwarding RPC batcherror serving requestserror proxying websocketerror writing clientConn message
WARN
backend request failed, trying againbackend banned - not healthybackend banned - unexpected block tagsproxied requests' XFF header will not contain the proxyd ip addresspeer count responded with 200 and 0 peersfailed requesterror updating backendbackend broke consensus
INFO
Related
- Consensus
- Emerald Dshackle load balancer
- dRPC
- Total number of primary candidates
- Optimism Censorship Bug Disclosure
See also
Advertising:
