feat(gdd): report incremental derived data processing latency - #121030
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
cvxluo
approved these changes
Aug 3, 2026
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
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.
Adds 'issues.derived.incremental_processing_latency' to track how long it takes us to incrementally process a new action.
To limit our reporting to incremental (and not bulk regen, where it's nonsensical) tracks mode and incrementality at the logging location.
To make that reasonable, we introduce a DerivedMetrics class to be responsible for context-awareness and logging details, aiming to keep the functional behavior lighter on the page.
Fixes ISWF-3065.