ws-head-latency: multi-region (harness region label + spec region tabs)#1198
Merged
Conversation
added 2 commits
July 16, 2026 13:09
Adds a static region ConstLabel to every ws-head-latency metric, bound at process startup from OCB_REGION (preferred) or RAILWAY_REPLICA_REGION (Railway auto-set), with eu-west fallback matching the historical single-vantage Paris VPS deployment. No observation site needs to change: the label is baked into every counter, gauge and histogram at registration, so all existing WithLabelValues(provider, chain) calls stay identical. Adds railway.toml so Railway can build the harness from Dockerfile with a /health check, matching the rpc-capabilities service layout. Follow-up: create the Railway ws-head-latency service with 3 replicas (us-east, eu-west, sgp) and OCB_REGION set on each, then decommission or leave the Paris VPS container as a 4th vantage.
Adds `dimensions.region` block + `rank_matrix_query` on provider, region + per-provider `regions:` sub-arrays with region-scoped queries on the 3 ws-head-latency specs, following the polkadot-rpc pattern. Depends on the harness region label change (previous commit): every metric now carries a region ConstLabel so the region-scoped histogram queries return values as soon as multi-region replicas publish. Until Railway 3-replica deploy lands, only region=eu-west has data and the other tabs render empty; the All regions tab keeps working because the aggregate query is unscoped by region.
Flotapponnier
added a commit
that referenced
this pull request
Jul 16, 2026
…on support to main (#1199) Consolidates 3 dev merges (#1170 harness + #1196 per-chain benches + #1198 multi-region) so main matches dev on the ws-head-latency cluster: * benchmarks/ws-head-latency.yml: parent bench 081 (Ethereum) * benchmarks/ws-head-latency-base.yml: bench 087, adds regions arrays * benchmarks/ws-head-latency-solana.yml: bench 088, adds regions arrays * harnesses/ws-head-latency/: full harness (was dev only), including region ConstLabel from OCB_REGION or RAILWAY_REPLICA_REGION * railway.toml: Railway build config so the service can be created After merge, create the Railway ws-head-latency service with 3 replicas (us-east, eu-west, sgp), set OCB_REGION on each. Railway auto-builds from main, metrics start flowing per region. Co-authored-by: Florent Tapponnier <contact@mobula.io>
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.
Two commits. Harness patch adds region ConstLabel via OCB_REGION or RAILWAY_REPLICA_REGION env, eu-west default. Spec changes add dimensions.region tabs + regions arrays on 3 providers per spec (081, 087, 088). Follow-up on your end: create Railway ws-head-latency service with 3 replicas (us-east, eu-west, sgp), set OCB_REGION on each. bun run validate: 78 specs valid. go build passes.