Mike Dame

Does https://github.com/open-telemetry/opentelemetry-go-instrumentation/issues/1176 help?

Hi, can you please share the logs from the auto-instrumentation agent?

@shravanv1 do you have the full logs from the agent from when it starts up? Not just the logs around the spans. I'm looking for a message that would indicate...

@ingvagabund can you put the vendor changes into their own commit for review?

@bwplotka we can close this now right?

We have PodLifetime, which considers pending pods, but only if they have already been scheduled (see https://github.com/kubernetes-sigs/descheduler/issues/858 and https://github.com/kubernetes-sigs/descheduler/pull/846#discussion_r899217024). I think there have been other similar request to evict non-scheduled...

@arasuse sorry but I don't quite understand your question, could you please explain more where the url is missing? It would also help to see what config you are running...

@NhatVuDuy ah, I understand now. We do support `{method} {target}` where there is a low-cardinality `{target}` value available. Starting in https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/740, this is automatically parsed from templated path names in...

@RonFed cool, we can look into it. @NhatVuDuy unfortunately right now we're prioritizing work for our [beta release](https://github.com/orgs/open-telemetry/projects/50) which is more focused on stability than features, so this won't be...

@NhatVuDuy are you using [routing patterns](https://go.dev/blog/routing-enhancements) in your code? That is what auto-instrumentation relies on to know it's a low-cardinality route. That feature became available in go 1.22