This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
imp(rpc) Add support for EVM RPC metrics #1378
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #XXX
Description
This PR exposes EVM RPC metrics similar to the ones exposed by
go-ethereum
.The metrics correspond to:
This PR creates a separate metrics server to serve the metrics for RPC and will be used to expose other EVM/ application metrics in the future.
Based on this discussion, three approaches are identified to exposing the metrics:
go-ethereum
by passing a hardcoded flag in the CLI--metrics
. This option will expose metrics that are not relevant to Ethermint and does not allow for a config file option. This is the approach chosen in this PR.The metrics exposed in this PR correspond to the EVM RPC endpoint as opposed to the tendermint one discussed here. The metrics that will be exposed include latency, number of requests, and the request type.
Sample metrics:
For contributor use:
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerFor admin use:
WIP
,R4R
,docs
, etc)