You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is useful but we feel like it might be even more useful to have instrumentation at the function call level. Currently all different contract calls/transactions to eigenlayer core and avs contracts only increase the eth_call metric, so we
Describe the solution you'd like
After we refactor the chainIO clients #26, we could create instrumented_contract_caller/transactor/filterer pretty easily following the same pattern, but these would instrument function calls and export prometheus metrics with call/tx counts + duration of each call to each function. We could then potentially also add those as eigen_ metrics... tbd.
The content you are editing has changed. Please copy your edits and refresh the page.
Is your feature request related to a problem? Please describe.
The avs node spec requires avs node software to instrument all of its json-rpc calls. We implemented this in instrumented_client.go
This is useful but we feel like it might be even more useful to have instrumentation at the function call level. Currently all different contract calls/transactions to eigenlayer core and avs contracts only increase the
eth_call
metric, so weDescribe the solution you'd like
After we refactor the chainIO clients #26, we could create instrumented_contract_caller/transactor/filterer pretty easily following the same pattern, but these would instrument function calls and export prometheus metrics with call/tx counts + duration of each call to each function. We could then potentially also add those as eigen_ metrics... tbd.
Tasks
The text was updated successfully, but these errors were encountered: