bridge: multi-region quote latency (eu-west / us-east / sgp) - #1563
Merged
Conversation
…t/us-east/sgp) - bridge-quote-latency.yml: add region dimension + per-region prom queries for all 5 bridges - prometheus.yml: add bridge-monitor 3-region scrape block (honor_labels, internal DNS) - /bridge page: update copy from single eu-west to 3-region description
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.
What
Upgrades the bridge quote latency bench from a single eu-west probe to 3 simultaneous regions.
Changes
benchmarks/bridge-quote-latency.ymlregiondimension: All regions / EU-West / US-East / Singaporeregions:query blocks for all 5 bridges (mobula, relay, lifi, debridge, near-intents)infrastructure/monitoring/prometheus/prometheus.ymlbridge-monitorscrape block with 3 Railway internal DNS targets:bridge-monitor-eu.railway.internal:2112bridge-monitor-us.railway.internal:2112bridge-monitor-sgp.railway.internal:2112honor_labels: trueso each instance'sregion=ConstLabel survives aggregationsrc/app/bridge/page.tsxRailway services to create (manual step)
Create 3 services in the
Dashboard OpenChainBenchRailway project fromharnesses/bridge-monitor/:bridge-monitor-euMONITOR_REGION=eu-westbridge-monitor-usMONITOR_REGION=us-eastbridge-monitor-sgpMONITOR_REGION=sgpAll 3: no
WALLET_EVM_PRIVATE_KEY/WALLET_SOL_PRIVATE_KEY,EXECUTION_MODEunset (defaults to dry-run). Bridge API keys optional (unkeyed mode works, just rate-limited).After creating services → redeploy Prometheus so it picks up the new scrape targets.
Safety
Zero execution risk: without wallet keys
CanExecute()=false. WithoutEXECUTION_MODE=productionthe scheduler never starts. See PR description of #1557 for full guard analysis.