From b90aca2816841226ed8723d0fc0857c0ceac6b35 Mon Sep 17 00:00:00 2001 From: Chris Raible Date: Thu, 12 Sep 2024 10:37:54 -0700 Subject: [PATCH] Removed jaeger container from docker compose (#20994) no issue - OpenTelemetry has been problematic in a number of ways (boot time, breaking the frontend). May revisit it at some point in the future, but for now it is only exporting metrics via prometheus and not traces, so there's currently nothing sending data to this jaeger container - Cleaning it up for now as it's just sitting there idly consuming resources --- .github/scripts/docker-compose.yml | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/.github/scripts/docker-compose.yml b/.github/scripts/docker-compose.yml index 43a67ffbca..c9ba7eda1c 100644 --- a/.github/scripts/docker-compose.yml +++ b/.github/scripts/docker-compose.yml @@ -28,15 +28,5 @@ services: ports: - "6379:6379" restart: always - jaeger: - image: jaegertracing/all-in-one:1.58 - container_name: ghost-jaeger - ports: - - "4318:4318" - - "16686:16686" - - "9411:9411" - restart: always - environment: - COLLECTOR_ZIPKIN_HOST_PORT: :9411 volumes: mysql-data: