Mike Dame

@MrAlias do you want to revive this PR for the beta milestone or we can start a fresh one?

From https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/738: > > The bug in this PR can happen approximately once every 50-100 client spans (since page size is 4096 bytes and we write ~40 bytes per request...

Would also add https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/639 (Remove support for Go versions below 1.17) or more clearly define our version support

Add: Go version support, kernel support, instrumentation library support documentation, libc (for binary)

From 3-Mar-24 sig meeting, at @grcevski started a thread on the Linux kernel mailing list to see about unlocking this: https://www.uwsg.indiana.edu/hypermail/linux/kernel/2403.0/03026.html It doesn't look like that thread has any replies...

From SIG call today: * We originally tried asking about this in Cillium slack, but didn't hear back * Could possibly be fixed by LSM policies (are those usable in...

Thanks @grcevski for the updates! I mentioned this on the call, but I think it's clear that we need to find an alternative approach. At this point I would consider...

https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/725#issuecomment-2032609505 for other support compatibility requirements

Also from #233: > We should have a dedicated page with all possible configuration settings. Example from .NET Automatic Instrumentation: https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/config.md > > Remember to also document config which comes...

+1 to this, or at least making it clear what go versions we support (mentioned in https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/636#issuecomment-1925365953) > Start tracking offsets from 1.17 in structs from the standard library (instead...