github-personal/firezone
1
0
Fork 0
mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-27 18:18:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

ci: use correct service name in docker-compose.yml (#6055)

Browse Source 
The compose service I defined is called `otel` not `otlp`. With this fix
in place, the relay successfully connects to the OTLP exporter.

it is worthwhile noting that the connection to the OTLP exporter itself
is not critical for relay operation. Even if it fails, it won't affect
the actual data plane. I do think it makes sense to still have a working
OTLP exporter in the compose definition. As it makes it easier to test
whether the ingestion of metrics and traces works as expected.
This commit is contained in:
Thomas Eizinger
2024-07-27 03:48:08 +01:00
committed by GitHub
parent 05e3a38701
commit 5687befc9d
2 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.github/workflows/_integration_tests.yml vendored
View File

@@ -145,6 +145,7 @@ jobs:
# Start one-by-one to avoid variability in service startup order
docker compose up -d dns.httpbin httpbin download.httpbin
docker compose up -d api web domain --no-build
docker compose up -d otel --no-build
docker compose up -d relay-1 --no-build
docker compose up -d relay-2 --no-build
docker compose up -d gateway --no-build

4
docker-compose.yml
View File

@@ -429,7 +429,7 @@ services:
RUST_LOG: ${RUST_LOG:-debug}
RUST_BACKTRACE: 1
FIREZONE_API_URL: ws://api:8081
OTLP_GRPC_ENDPOINT: otlp:4317
OTLP_GRPC_ENDPOINT: otel:4317
build:
target: dev
context: rust
@@ -470,7 +470,7 @@ services:
RUST_LOG: ${RUST_LOG:-debug}
RUST_BACKTRACE: 1
FIREZONE_API_URL: ws://api:8081
OTLP_GRPC_ENDPOINT: otlp:4317
OTLP_GRPC_ENDPOINT: otel:4317
build:
target: dev
context: rust