OpenTelemetry setup does not work with --env-file

[tolu]

Version: Deno 2.1.7

Configuration of OTEL via (at least these) environment variables from --env-file is not respected as stated in the OTEL docs.

• OTEL_SERVICE_NAME - default is unknown_service (/ext/telemetry/lib.rs#L626)
• OTEL_EXPORTER_OTLP_ENDPOINT - default is localhost:4318 (/ext/telemetry/lib.rs#L662)
• OTEL_EXPORTER_OTLP_PROTOCOL - default is http/protobuf (/ext/telemetry/lib.rs#L606)

Example repository with reproduction involving

1. A server bootstrapped with OTEL (either via env file, shell or dockerfile)
2. A logger that listens on the configured OTLP_ENDPOINT and print content-type and the payload of requests
3. A client that spams the server with some requests

Assigning values like:

• OTEL_SERVICE_NAME=my-service
• OTEL_EXPORTER_OTLP_PROTOCOL=http/json

Still uses protobuf and yields service.name: <unknown_service>

Changing the port of:

• OTEL_EXPORTER_OTLP_ENDPOINT=localhost:4317

results in no reports arriving at that endpoint.

[tolu]

I updated example repo with docker and (working) shell examples as well.

Setting environment variables in shell works supremely well.

When running the server in docker, the exporter seems to fail on TCP connection issues, but that might just as well be me that have failed to configure something correctly. 🤔 🙈

name="BatchSpanProcessor.Flush.ExportError" reason="Other(hyper_util::client::legacy::Error(Connect, ConnectError(\"tcp connect error\", Os { code: 111, kind: ConnectionRefused, message: \"Connection refused\" })))" message=Failed during the export process
deno-otel-container  |  name="BatchSpanProcessor.Flush.ExportError" reason="Other(hyper_util::client::legacy::Error(Connect, ConnectError(\"tcp connect error\", Os { code: 111, kind: ConnectionRefused, message: \"Connection refused\" })))" message=Failed during the export process