Trace and span IDs not being updated about opentelemetry-go-instrumentation HOT 6 CLOSED

I think this may be resolved following a number of fixes including no longer using the keyval launcher, updating offsets, streamlining probes, updating eBPF maps, etc.

@rogercoll Please can you try again and report back?

from opentelemetry-go-instrumentation.

Latest main version work's fine. Thank you!

from opentelemetry-go-instrumentation.

Using the http server example shown in #17, the issue is similar, no trace or span id is reported in the traces.

from opentelemetry-go-instrumentation.

@rogercoll I tried to reproduce (unfortunately on different ubuntu and Go version) this issue with example from #17 and would like to clarify, when you say "no trace or span id is reported in the traces" you mean collector side or otel-go-instrumentation log as above (the thing is I'm not getting this kind of message from otel-go-instrumentation process).
On collector side I see some ids

Span #0
    Trace ID       : c14459cc25a670110260e3c052e2e6e9
    Parent ID      : 
    ID             : 34715626971844bf
    Name           : /books/title/page/page
    Kind           : Server
    Start time     : 2023-04-03 16:35:51.589536338 +0000 UTC
    End time       : 2023-04-03 16:35:51.589596691 +0000 UTC
    Status code    : Unset
    Status message : 
Attributes:
     -> http.method: Str(GET)
     -> http.target: Str(/books/title/page/page)
	{"kind": "exporter", "data_type": "traces", "na

Collector instrumentation on the other hand (original case) triggers another error {"level":"error","ts":1680538101.5058162,"caller":"cli/main.go:76","msg":"error while analyzing target process","error":"could not find function offsets for instrumenter","stacktrace":"main.main\n\t/home/vagrant/opentelemetry-go-instrumentation/cli/main.go:76\nruntime.main\n\t/snap/go/10029/src/runtime/proc.go:250"}
which might be related to environment differences.

from opentelemetry-go-instrumentation.

@rogercoll are you setting the OTEL_PROPAGATORS environment variable? I hit the same issue until I set that eg https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/46/files#diff-d809bd2e3528bad1b6ef0815ea0ee2d5ed9de5df6ed0acae88823157825a026aR53-R54

@pdelewski your error looks like the offsets may be missing for your Go version, have you tried running make offsets and re-building the agent? I updated the latest offsets in #46 as well so that should be merged soon

from opentelemetry-go-instrumentation.

@damemi I looked into offsets and it seems its there, however let me double check that

from opentelemetry-go-instrumentation.