Damien Mathieu
Damien Mathieu
Sure. More explicit doc is always welcome.
> I would be happy to help review Feel free to do so, as that's definitely a good way forward being code owner :)
If you look at the PR merging the new instrumentation, we decided not to ship it for now. That doesn't prevent using it. You can use commit hashes as a...
This was shipped in https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrumentation/go.mongodb.org/mongo-driver/v2/mongo/otelmongo
Updating semconv is definitely not just a chore, especially since, as you mention, there are field name changes (which can cause issues with users, since they need to change their...
> What is the purpose of doing this? It seems like this will maintain the existing behavior. Yes, this would be a noop change. It would (a bit virtually) reduce...
Sure, if you think there's still too much work for this PR. Maybe document the outcome from the discussion that happened here in #6171?
Also, folks using the package will have less surprises seeing a newer version in their dependency tree rather than something older that looks like it's not being cared for.
Yes, if we can get HTTP instrumentations to use otelhttp rather than reimplement things themselves, that's definitely better.
Yes. But if/when that happens, we will make the appropriate changes to avoid breaking other instrumentations. Reusing otelhttp also makes it much easier to keep. things working the same way....