From 3cc9f330418667b80fc9c65835ef6a8058835461 Mon Sep 17 00:00:00 2001
From: Pratik Mankawde <3397372+pratikmankawde@users.noreply.github.com>
Date: Tue, 22 Sep 2026 13:58:18 +0100
Subject: [PATCH] fix(telemetry): publish the Prometheus ports on the host
 loopback

The StatsD port beside them was already loopback-bound with a comment saying
why; the Prometheus exporter and Prometheus itself were not. Prometheus
scrapes the collector as otel-collector:8889 over the compose network, so the
published port had no consumer.
---
 docker/telemetry/docker-compose.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docker/telemetry/docker-compose.yml b/docker/telemetry/docker-compose.yml
index 13da6a56c9..5d61f58131 100644
--- a/docker/telemetry/docker-compose.yml
+++ b/docker/telemetry/docker-compose.yml
@@ -30,7 +30,7 @@ services:
       # receiver has no auth, and xrpld runs on the host, so it reaches the
       # collector via 127.0.0.1. Do not expose on 0.0.0.0 in shared setups.
       - "127.0.0.1:8125:8125/udp"
-      - "8889:8889" # Prometheus metrics (span_metrics + statsd)
+      - "127.0.0.1:8889:8889" # Prometheus metrics (span_metrics + statsd)
       - "13133:13133" # Health check
     volumes:
       # Mount collector pipeline config (receivers → processors → exporters)
@@ -59,7 +59,7 @@ services:
     # Pinned to an exact patch release for reproducible, config-stable runs.
     image: prom/prometheus:v3.13.2
     ports:
-      - "9090:9090"
+      - "127.0.0.1:9090:9090"
     volumes:
       - ./prometheus.yml:/etc/prometheus/prometheus.yml:ro
     depends_on: