Tyler Yahn

> @MrAlias @RonFed Hi, i'm still running into this issue with both versions 1.22.1 and 1.21.9. According to the README compatibility section (https://github.com/open-telemetry/opentelemetry-go-instrumentation?tab=readme-ov-file#compatibility) both 1.21 and 1.22 GO versions should...

We plan to release support for Go 1.22.3 (and 1.21.10) in a few days.

We added a graceful degradation for the HTTP instrumentation, where it will log an error if the kernel is locked down. We can do the same for gRPC as well....

There are going to be a few complex issues to address in this issue: 1. The first argument passed is a Go `error` interface 2. The method accepts a variadic...

> 1. When calling `errors.New` or `fmt.Errorf` the concrete structs contain the error message as the first field in the struct. This probably covers a significant percentage of the cases...

From SIG: Name suggestion: `otel/auto-go`

> @MrAlias Is it needed for beta? Not as far as I can see.

Seems to have been caused because the `v1.7.0` tag was checked out to a `v1.7.0` branch in the specification repository (`git checkout tags/v1.7.0 -b v1.7.0`). Ideally this wouldn't be panic.

You bring up an interesting point. In the rule you mentioned: ``` spanName: destination.workload.name | destination.service.name | "unknown" ``` `destination.service.name` becomes the default if `destination.workload.name` is undefined. From the output...

Ideally, we merge https://github.com/open-telemetry/opentelemetry-proto-go/pull/177, or something equivalent, before this is released.