Custom health monitor for execution and beacon #283
Merged
Conversation
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
canercidam
approved these changes
Jan 5, 2026
Contributor
canercidam
left a comment
canercidam
left a comment
There was a problem hiding this comment.
@ferranbt I tested this locally and didn't see the logging issues I was concerned of before. Also did a quick conflict resolution here on GitHub (it was quite simple - hoping that's okay). Thanks a lot! Merging this shortly to avoid more conflicts.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR creates a new internal service
healthmon(shipped on theplayground-utilsdocker image) intended to be a replacement of the current https://github.com/flashbots/ethereum-healthmon sidecar. Since this new bespoke version of the health monitor is intended to be used only on the playground, we have made certain design decisions to improve the UX. For example, the chains are considered ready at block 0 right away after the RPC endpoints are available.Closes #282