Some json-rpc endpoints are a bit more strict

[roderik]

There are some json-rpc endpoints that are a bit more strict that others. When running on them I get these errors

{"component":"exporter","error":"Error -32600 (Params must be an array)","exporter":"execution","level":"error","module":"net","msg":"Failed to get peer count","time":"2023-02-09T07:49:42Z"}                                                                                       │
{"component":"exporter","error":"Error -32600 (Params must be an array)","exporter":"execution","level":"error","module":"web3","msg":"Failed to get node info","time":"2023-02-09T07:49:42Z"}                                                                                       

[samcm]

👋 Hey @roderik! That's interesting. What Execution client are you using here?

[roderik]

I think it is the loadbalancer I use: https://github.com/emeraldpay/dshackle

We run a bunch of metrics -> dshackle -> fleet of erigon, geth, bor, etc nodes groups