Bump opentelemetry-instrumentation-botocore to >=0.62b0 to enable aiobotocore tracing

[saraygrjim]

Summary

aws-opentelemetry-distro==0.17.0 pins opentelemetry-instrumentation-botocore==0.61b0, which only registers BotocoreInstrumentor. As a result, applications that use aiobotocore (the async client used widely for S3, DynamoDB, SQS, Bedrock, etc.) produce no AWS spans at all when relying on the distro for auto-instrumentation.

In opentelemetry-python-contrib 1.41.0/0.62b0 the aiobotocore instrumentation was merged into opentelemetry-instrumentation-botocore and a second entry point, AiobotocoreInstrumentor, is now registered automatically when the package is installed.

References:

• Changelog: https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/CHANGELOG.md ("Version 1.41.0/0.62b0 → Add support for instrumenting aiobotocore (#4049)")
• Docs: https://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation/botocore/botocore.html

Proposed change

Bump the pinned versions in aws-opentelemetry-distro/pyproject.toml so they include opentelemetry-instrumentation-botocore >= 0.62b0 (and the rest of the contrib packages aligned to the same 0.62bx line), and cut a new release of aws-opentelemetry-distro on PyPI.

PR #725 already does this dependency bump end-to-end (currently failing CI). Could you please prioritise landing it (or an equivalent green PR) and publishing a release?

[liustve]

Hi we don't have a set timeline for a release but if this breaking AWS SDK instrumentation will sync with the team to see if we can prioritize.

[saraygrjim]

Thanks, really appreciate it.

Yes, I can confirm this is causing issues for us at the moment. With the current pinned version, the AWS SDK auto-instrumentation only covers the existing BotocoreInstrumentor, so workloads using aiobotocore are not producing AWS spans.

This is becoming a blocker for our development work, so we’d really appreciate it if the team could consider prioritising it in the short term.

Thanks again for looking into it!

[saraygrjim]

Hi, sorry to follow up again. Is there any update on this from the team’s side? Even a rough indication of whether it’s likely to make it into the next release cycle would help us plan on our end. Thanks!

[liustve]

Hi @saraygrjim we always aim to keep up to date with the latest changes in upstream OTel in every minor version bump, however, we don't yet have a planned date for this release.

[liustve]

fixed with release 0.18.0 which upgraded to 1.42.1/0.63b1