Skip to content

AWS-Xray is not getting disable in Python #241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hassanahmed95 opened this issue Sep 1, 2020 · 4 comments
Open

AWS-Xray is not getting disable in Python #241

hassanahmed95 opened this issue Sep 1, 2020 · 4 comments
Labels

Comments

@hassanahmed95
Copy link

hassanahmed95 commented Sep 1, 2020

I have a XRAY_RECORDER dict in the setting.py file of Django. Where I have different settings for AWS Xrays like Daemon address, tracing name etc. In the same dict I also mentioned 'AWS_XRAY_SDK_ENABLED': False. In short, I want to disable AWS Xray SDK for my application. But it still sends traces in spite of setting it to False. Although I can turn it off using global_sdk_config.set_sdk_enabled(False) but due to requirements constraint, I have to enable or disable it via environment variables. But it still send traces in spite of setting to False.

@RafeyIqbalRahman
Copy link

#172 @chanchiem

@hassanahmed95
Copy link
Author

#172 does not address my issue. In #172 the approach via global SDK config has been mentioned. While I am address it via environment variable approach.

@srprash
Copy link
Contributor

srprash commented Sep 14, 2020

Hi @hassanahmed95
Apologies for late response. I have been investigating this issue and discovered that AWS_XRAY_SDK_ENABLED setting is not supported in the django instrumentation of the SDK. Currently, for configuring the X-Ray recorder for a Django application, only these environment variables are supported within the settings.py file. You can set the environment variable AWS_XRAY_SDK_ENABLED as False outside the application on your host if possible, to disable the SDK.
Let me know if that works out for you.

@stale
Copy link

stale bot commented Jan 8, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in next 7 days. Thank you for your contributions.

@stale stale bot added the stale label Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants