search

vegaprotocol / vega-monitoring

MVP to store more data for metrics
MIT License
2 stars 1 forks source link

feat: limit number of blocks for filter logs #27

Closed daniel1302 closed 2 months ago

daniel1302 commented 2 months ago

Issue

We had a following errors on one of the monitoring servers tonight:


May 01 21:34:10 m2.vega.community vega-monitoring[204155]: {"level":"error","@timestamp":"2024-05-01T21:34:10.319Z","logger":"root","caller":"ethereummonitoring/service.go:136","message":"Failed to filter logs for the events counter(UMA Termination on Arbitrum One): failed to run handler for 3 times, last error: failed to filter ethereum logs for contract 0x6d0b3a00265b8b4a1d22cf466c331014133ba614 for block <206821664; 206845974>: block range is too wide, all errors: [failed to filter ethereum logs for contract 0x6d0b3a00265b8b4a1d22cf466c331014133ba614 for block <206821664; 206845961>: block range is too wide failed to filter ethereum logs for contract 0x6d0b3a00265b8b4a1d22cf466c331014133ba614 for block <206821664; 206845972>: block range is too wide failed to filter ethereum logs for contract 0x6d0b3a00265b8b4a1d22cf466c331014133ba614 for block <206821664; 206845974>: block range is too wide]"}
May 01 21:34:55 m2.vega.community vega-monitoring[204155]: {"level":"info","@timestamp":"2024-05-01T21:34:55.784Z","logger":"root","caller":"config/config.go:201","message":"Reloaded config, because config file changed","event":"/home/vega/vega_monitoring_home/config.toml"}