Skip to content

chore: rpc usage metrics #136

Description

@mfw78

Background

It's difficult to rationalise issues associated with RPC connections and the watch-tower. More metrics are needed around this.

Details

Add additional metrics that are able to comprehensively track all RPC usage throughout all code paths.

Acceptance criteria

The following metrics should be implemented:

  • RPC calls (eth_call)
  • Gas consumption for (eth_call)
  • Time elapsed between new block notifications
  • Time elapsed processing a block (ie. from receipt to polling finished)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions