feat(reexecution): collect leveldb and meterdb metrics #4804
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.
Why this should be merged
Enables reexecution benchmarks to collect leveldb and meterdb metrics. This allows existing leveldb or meterdb related Grafana dashboards to work with metrics from benchmark runs.
With this change, metrics like
avalanche_db_non_level_0_compsandavalanche_meterdb_calls{method="get"}are available during reexecution tests as well, allowing us to monitor db performance.How this works
avalanche_dbnamespaceavalanche_meterdbnamespaceHow this was tested
I ran a reexecution benchmark and confirmed that the leveldb and meterdb metrics are visible.
Need to be documented in RELEASES.md?
No