chore: cherry-pick pm-api-latency cohort + venue dimension#726
Merged
Conversation
Root cause: rank_matrix_query + uptime panels matched any venue label present in pmapi_* metrics — codex, codex-polymarket, codex-kalshi, predexon-*, mobula crept in via the pm-rate-limits harness scraping the same gauges. The leaderboard mixed real venues with paid relays and broken probes (success<70%), and surfaced bogus /products/<slug> pages. Fix: - Pin venue=~"polymarket|kalshi|limitless|manifold|myriad" on rank_matrix_query + uptime_24h/7d/30d + cold_connect_p50 panels. - Add dimension.venue so each native venue gets its own sub-leaderboard alongside the per-region tabs (Polymarket × us-east, etc.), matching the original PM cluster design.
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 #725 from dev.