op-node: add follow source reorg observability - #22106
Open
jelias2 wants to merge 1 commit into
Open
Conversation
jelias2
force-pushed
the
jelias2/light-node-reorg-observability
branch
from
July 29, 2026 21:55
668baf3 to
ab5643d
Compare
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
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
This pull request adds new metrics and logging to improve observability around reorg events in the
op-nodecomponent. It introduces Prometheus counters to track "follow source" and "super authority" reorg events, and integrates these metrics into key reorg-handling code paths. Additional logging is also added to provide more context during reorgs.Metrics instrumentation and logging improvements:
metrics.go:FollowSourceReorgs(tracks follow source reorg decisions by action) andSuperAuthorityReorgSignals(tracks super authority reorg signals by reason). Corresponding methods were added to theMetricerinterface and implemented in both the real and noop metricers. (op-node/metrics/metrics.goengine_controller.go, integratedRecordSuperAuthorityReorgSignalcalls at points where the super authority safe head is unknown or non-canonical, to record the reason for these reorg signals. (op-node/rollup/engine/engine_controller.go)FollowSourcemethod, added detailed warning and info logs to capture the state of local and external heads during reorgs, and instrumented the code to record follow source reorg actions (force_resetfor sequencer resets andsoft_updatefor verifier updates) using the new metric.These changes make it easier to monitor and diagnose reorg-related events in the system by providing structured metrics and richer logs.
Tests
Additional context
Metadata