fix(uwsgi): add to ssi denylist [backport 2.21] #12941
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
According to our [docs](https://docs.datadoghq.com/tracing/trace_collection/library_injection_local/?tab=kubernetes#requirements) SSI does not support UWSGI. To make SSI+ddtrace-py more resilient we should add `/usr/bin/uwsgi` to the denylist. This is not a perfect solution since the uwsgi command can be stored elsewhere on a host and this could make it more challenging to add uwsgi support in the future (SSI will fail and it will be hard to know this change is why). ## Checklist - [ ] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) --------- Co-authored-by: Brett Langdon <brett.langdon@datadoghq.com> (cherry picked from commit 327a1e6)
avara1986
approved these changes
Mar 28, 2025
|
|
mabdinur
approved these changes
Mar 28, 2025
emmettbutler
approved these changes
Mar 28, 2025
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport 327a1e6 from #12891 to 2.21.
According to our docs SSI does not support UWSGI.
To make SSI+ddtrace-py more resilient we should add
/usr/bin/uwsgito the denylist. This is not a perfect solution since the uwsgi command can be stored elsewhere on a host and this could make it more challenging to add uwsgi support in the future (SSI will fail and it will be hard to know this change is why).Checklist
Reviewer Checklist