#Integrating dagger with otel collector
1 messages · Page 1 of 1 (latest)
by setting the standard OTEL exporter variables, Dagger will just use those. https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/
Endpoint Configuration The following environment variables let you configure an OTLP/gRPC or OTLP/HTTP endpoint for your traces, metrics, and logs.
OTEL_EXPORTER_OTLP_ENDPOINT A base endpoint URL for any signal type, with an optionally-specified port number. Helpful for when you’re sending more than one signal to the same endpoint and want one...
so I set OTEL_EXPORTER_OTLP_ENDPOINT where the dagger client is running? Let me try.
yep. That should be it
Appreciate this info, but it seems not to be working for me. I'm running a local collector, but export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318; dagger call ... does not result in any traces.
have you checked your collector logs? I'm confident this works because I use it regularly to send traces to some third-party collectors