-
Notifications
You must be signed in to change notification settings - Fork 443
feat(co): add in-product enablement support #13633
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
base: main
Are you sure you want to change the base?
Conversation
We add support for in-product enablement to code origin for spans.
|
Bootstrap import analysisComparison of import times between this PR and base. SummaryThe average import time from this PR is: 277 ± 2 ms. The average import time from base is: 277 ± 2 ms. The import time difference between this PR and base is: -0.8 ± 0.1 ms. Import time breakdownThe following import paths have grown:
|
BenchmarksBenchmark execution time: 2025-06-10 11:08:05 Comparing candidate commit 714aeb9 in PR branch Found 0 performance improvements and 4 performance regressions! Performance is the same for 549 metrics, 3 unstable metrics. scenario:iastaspects-format_map_aspect
scenario:iastaspectsospath-ospathbasename_aspect
scenario:iastaspectsospath-ospathnormcase_aspect
scenario:iastaspectsospath-ospathsplitdrive_aspect
|
I think in-product enablement should only enable entry spans so this might be blocked by #13593. |
def _start(): | ||
from ddtrace.debugging._origin.span import SpanCodeOriginProcessor | ||
|
||
SpanCodeOriginProcessor.enable() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When you rebase this, we should either remove or separate exit spans into a separate path per agent sync discussion
We add support for in-product enablement to code origin for spans.
Checklist
Reviewer Checklist