-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
feat(consensus): add tracing instrumentation to consensus store #2546
Conversation
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.
Nice, more visibility is surely going to help you understand what's happening. Keeping the code readable at the same time is a balancing act.
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.
Mostly LGTM
🤖 I have created a release *beep* *boop* --- ## [24.14.0](core-v24.13.0...core-v24.14.0) (2024-08-01) ### Features * Adding SLChainID ([#2547](#2547)) ([656e830](656e830)) * **consensus:** add tracing instrumentation to consensus store ([#2546](#2546)) ([1e53940](1e53940)) * Poll the main node for the next batch to sign (BFT-496) ([#2544](#2544)) ([22cf820](22cf820)) * Support sending logs via OTLP ([#2556](#2556)) ([1d206c0](1d206c0)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: zksync-era-bot <[email protected]>
What ❔
This PR adds instrumentation to consensus store layer which should serve as a good starting point. Most other layers are heavily intertwined with the
era-consensus
codebase so we will need to introduce instrumentation there first.Why ❔
Better visibility of what we spend our time on, including waiting time
Checklist
zk fmt
andzk lint
.