Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(celery): close celery.apply spans using task_protocol 1 [backport…
… 2.14] (#10874) Backport 6346fcb from #10848 to 2.14. This PR fixes an issue where Celery's closing signals got triggered but dd-trace-py skipped closing the `celery.apply` span due to not finding the task id. In celery's `task_protocol: 1`, the id is in the message of the body: https://docs.celeryq.dev/en/main/internals/protocol.html#message-body . The issue with the previous logic is that if the headers does have information (even if the headers were unrelated to the id), it would skip the check of the id in the body: before: ``` if headers: ``` after (this PR): ``` if headers and 'id' in headers: ``` By doing this, we check the headers for the id, then check the body for the id. If it fails to find the task id in the body or header, then it still hits the debug log, `unable to extract the Task and the task_id. This version of Celery may not be supported.` . This PR relates to the goal of #10676 , to close celery spans. If for some reason the logic in this PR fails to close an open `celery.apply` span, #10676 will act as a fail safe and close it. Special Thanks: @timmc-edx for helping us track this down! ## Checklist - [x] 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: wantsui <[email protected]>
- Loading branch information