Closed aharbis closed 1 year ago
Ugh, that has happened before. I think it is a symptom of having version mismatches (e.g. multiple versions) in certain parts of the otel ecosystem.
I'll have a look in a bit. Thanks for raising.
This is actually invalid. You will get non-zero TraceId from the controller provider you run with telemetry features:
just forward-tempo & # see below
just run-telemetry
this does require you having a valid place to point the exporter at (via OPENTELEMETRY_ENDPOINT_URL
evar) because we cannot initalize the tracer without that (and tonic will try to connect to that), and without a tracer (or without calling get_trace_id from inside a instrumented context), the traceids are always zero.
The
TraceId
returned bytelemetry::get_trace_id
is invalid (zero). This is also the case for theSpanId
. I suspect it's something to do with the integration betweentracing
andopentelemetry
(insrc/telemetry.go
):Running locally against my Kubernetes cluster, with the
lorem
example doc created, thetrace_id
value is always zero:Adding a getter and
Field
forspan_id
shows similar: