Skip to content

fix(pm-freshness): scrape via Railway internal DNS#311

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Flotapponnier merged 1 commit into from
Jun 4, 2026
Merged

fix(pm-freshness): scrape via Railway internal DNS #311

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions infrastructure/prometheus/prometheus.yml
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -109,12 +109,19 @@ scrape_configs:
# Cross-correlates Polymarket CLOB WebSocket (T0) vs Mobula PM WS vs
# Codex (defined.fi) GraphQL WS for the same trade. Reports per-provider
# millisecond lag.
#
# Scraped over Railway internal DNS because the harness lives in the
# same `Dashboard OpenChainBench` Railway project as this Prometheus.
# Public *.up.railway.app routes go through the edge and Railway does
# not always allow same-project traffic to loop back via the public
# gateway. Internal DNS is HTTP on port 2112 (the harness's exposed
# /metrics port) — never goes through Cloudflare / edge.
- job_name: pm-freshness
metrics_path: /metrics
scheme: https
scheme: http
static_configs:
- targets:
- pm-freshness-bench-production.up.railway.app
- pm-freshness-bench-production.railway.internal:2112
labels:
benchmark: pm-freshness
host: mobula
Expand Down
Loading