Add aiobotocore instrumentation

[dacevedo12]

Description

Added instrumentor for aiobotocore, an async client for amazon services.

It's based on the sync botocore instrumentor, overriding the methods to patch the async codepaths

Fixes #553

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• I've been using it on production for a while with no problems.
• workflow tests should pass to be sure

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: dacevedo12 / name: David Acevedo (cd6ba57)

[dacevedo12]

CI is all green in my branch now ✔️

[nemoshlag]

LGTM but I got assigned due to docs/instrumentation ownership (which looks great). @mariojonke can you take a look? I believe you'll this is your domain 🙏

[dacevedo12]

@nemoshlag it's ok if you want to merge the other one first as this will certainly cause a conflict. I can rebase and update

[nemoshlag]

Hi @dacevedo12 thanks but it's ok. I think new instrumentations should be promoted, but I don't have any control over merging prioritization :)

[dacevedo12]

Perhaps the bot requested more reviews due to the spellcheck fix in boto3sqs. I just changed it so the CI would pass

Any chance this makes it to the 0.38 release 😄 ?

[ronlut]

@dacevedo12 thanks for your precious time and work :)
I am waiting for this as well, is it still blocked? Who should approve it?
Maybe worth releasing it as a separate instrumentor if it's not gonna happen in this repo?

[dacevedo12]

They likely won't merge it, check the (ongoing?) discussion at #1714.

I'm down to publish this on a separate repo, but won't happen immediately as I'm busy with some stuff.

Feel free to fork/copypaste in the meantime, that's what I did at work.

[dacevedo12]

Will move this to my own repo soon. Progress surely won't be made here.

Disappointing.

[idonava]

Is there any chance to merge this PR?
This library is widely used, and we were also waiting for it.

[henocdz]

@lzchen @ocelotl I see you have been working on reviewing and approving recent MRs on this repo; do you know what's required to get this much-needed change? How can we help? It'd be nice to have this available.

Thanks for your work maintaining this.