hotfix: bridge benches per-destination chain dimension - #596
Merged
Conversation
Adds a 'dimensions.chain' block to bridge-quote-latency and bridge-fee with values matching the harness chain label (Solana / Base / Arbitrum / HyperCore). The site UI surfaces this as clickable tabs. Why: the aggregate cross-corridor view is misleading on bridges with asymmetric per-corridor performance. Near Intents in particular is bimodal (Arb to HyperCore ~30ms via solver-cached bid, Sol to Base ~3000ms full auction wait), and the aggregate histogram quantile produced 175ms p50 which represents neither corridor. Requires the matching mobula-api PR (chain label emission in the bridge-monitor harness).
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
1 participant
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.
Cherry-pick of #595 from dev. Scope is strictly the dimensions.chain block on bridge-quote-latency.yml and bridge-fee.yml. Nothing else from dev included.
Requires the mobula-api PR (chain label emission in bridge-monitor) to be merged and the harness redeployed before this dimension produces split data on the page. The 'All destinations' aggregate keeps working today regardless.