#default OTEL env vars

1 messages · Page 1 of 1 (latest)

outer spruce
#

I am running into the same. Was there a workaround? I don't want these vars to be set by default. They are conflicting with what' I'm trying to run

Message: OTLP endpoint must be a valid URL: unix:///dev/otel-grpc.sock

leaden elm
outer spruce
#

hmm, till that gets merged, is the workaround, doing a withoutEnvVariable on the default OTEL vars?

median nova
#

Still trying to figure out what users expect here really, now that we're going to be integrating with OpenTelemetry "first-class" there are definite use cases for piggy-backing on it so it's all one big trace, so let me know if you have a use case that absolutely 100% does not want that. tl;dr is that you'll be able to set standard OTEL_* vars wherever you're running the dagger CLI and everything should "just work", including any telemetry your functions are recording

median nova
outer spruce
#

This is a multi module java library I am trying to run mvn test . Looks like it's using ths library - https://micronaut-projects.github.io/micronaut-tracing/snapshot/guide/index.html

And I think you are correct that it doesn't understand the unix:// socket as I see this in the log

Caused by: java.net.MalformedURLException: unknown protocol: unix
        at java.base/java.net.URL.<init>(URL.java:779)
        at java.base/java.net.URL.<init>(URL.java:654)
        at java.base/java.net.URL.<init>(URL.java:590)
        at io.opentelemetry.exporter.otlp.internal.OtlpConfigUtil.validateEndpoint(OtlpConfigUtil.java:212)
        ... 94 more
#

I don't think I care about sending any trace data for unit test. So looking for a way to disable tracing altogether.