Anton Pirker

Hey @czyber ! We are really not the fastest at looking at contributions right now. (didnt know you also did some graphene contributions) Is this the change you want to...

We have a bash script that does this: https://github.com/getsentry/sentry-python/blob/master/scripts/aws-cleanup.sh So maybe we can just invoke this in an AWS Lambda function (or somewhere else)

One idea to tackle the "classes imported before `sentry_sdk.init` will left uninstrumented": What `opentelementry-instrumentation` does is setting the `PYTHONPATH` env variable to `'.../lib/python3.10/site-packages/opentelemetry/instrumentation/auto_instrumentation:/home/anton/my_project'` In `.../lib/python3.10/site-packages/opentelemetry/instrumentation/auto_instrumentation` there is a file called...

Hey @mlockett42 That's a really good suggestion. We need to make the SDK support more async processing, to fully support all the async Python projects out there. I put this...

@stryker-sk can you please add information on what version of Django and Zappa you use? And if you have any special settings for Django and/or Zappa?

Hey @stryker-sk, I created a [demo application](https://github.com/getsentry/test-awslambda-zappa-django) to reproduce this error. It is a Django application using Zappa to run in AWS Lambda. The demo application first reads the contents...

So you managed to exclude the boto3 library itself but keep the sentry boto integration and everything works now as expected?

Ok, sorry for the misunderstanding. Then I can not reproduce your issue. Here is the .zip of my Zappa project that works as excepted. It sends errors and performance data...

I just used `zappa deploy dev` and `zappa update dev` to deploy/update. My Zappa settings you can see here: https://github.com/getsentry/test-awslambda-zappa-django

Thanks for creating the issue @IevgeniiB !