design doc: interop monitoring #222
Open
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
Begins to flesh out a plan for how we go about monitoring and alerting for the interop release.
This was referenced Mar 27, 2025
axelKingsley
reviewed
May 7, 2025
tynes
commented
May 7, 2025
tynes
commented
May 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Begins to flesh out a plan for how we go about monitoring and alerting
for the interop release.
This is meant to mitigate FM2 in the Message Passing FMA
In practice we could use the alternative backend for
op-supervisorfor the monitoring: ethereum-optimism/optimism#15128. We could write a simple client that subscribes to blocks in the dependency set and then calls out toop-supervisorfor everyExecutingMessagethat it finds to validate it