Goal is to help the user distinguish if RPCs are failing because:
- bad request (user need to fix it for succeeding)
- the network (retry later when network is OK)
As of right now, the proxy does not reflect JSON-RPC level errors in its statistics (but it is still seen transparently as an error to the proxy caller of course).
The proxy interpret and act only on errors at lower protocol layers (IP, HTTP), but not at "JSON-RPC" level.
The enhancement is to interpret the JSON-RPC to update the statistic and better reflect the "end result".
Related info: MystenLabs/sui#12989
Goal is to help the user distinguish if RPCs are failing because:
As of right now, the proxy does not reflect JSON-RPC level errors in its statistics (but it is still seen transparently as an error to the proxy caller of course).
The proxy interpret and act only on errors at lower protocol layers (IP, HTTP), but not at "JSON-RPC" level.
The enhancement is to interpret the JSON-RPC to update the statistic and better reflect the "end result".
Related info: MystenLabs/sui#12989