-
Notifications
You must be signed in to change notification settings - Fork 7
feat: update metrics #367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
feat: update metrics #367
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
76d66a0
feat: update metrics in chain orchestrator
greged93 e990ebb
feat: meter l2 block imports
greged93 0bc546c
fix: change metric visibility
greged93 b5388a6
chore: renaming
greged93 ba486d5
Merge branch 'main' into feat/update-metrics
frisitano 7cd2e66
Merge branch 'main' into feat/update-metrics
greged93 92f819a
Merge branch 'main' into feat/update-metrics
frisitano File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we don't allow empty blocks then the
finalizemethod below will returnNone. We should handle that case.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On second thought, maybe it was your intention to skip it such that we don't report metrics for empty blocks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes the idea was only to record the actual block building duration for blocks that get added to the chain. I think we could however also have a metric for block building regardless of whether they get added to the chain, and also for the duration between 2 consecutive block added to the chain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these could both be valuable to have