chore(di): trigger probes

[P403n1x87]

We implement trigger probes. These allows triggering the capture of debug information along a trace, ensuring all the relevant probes are also triggered.

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
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• 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 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

[github-actions]

CODEOWNERS have been resolved as:

ddtrace/debugging/_live.py                                              @DataDog/debugger-python
ddtrace/debugging/_products/live_debugger.py                            @DataDog/debugger-python
ddtrace/debugging/_session.py                                           @DataDog/debugger-python
ddtrace/debugging/_signal/trigger.py                                    @DataDog/debugger-python
ddtrace/settings/live_debugging.py                                      @DataDog/apm-core-python
tests/debugging/live/__init__.py                                        @DataDog/debugger-python
tests/debugging/live/test_live_debugger.py                              @DataDog/debugger-python
tests/debugging/test_session.py                                         @DataDog/debugger-python
ddtrace/_trace/context.py                                               @DataDog/apm-sdk-api-python
ddtrace/contrib/trace_utils.py                                          @DataDog/apm-core-python @DataDog/apm-idm-python
ddtrace/debugging/_exception/replay.py                                  @DataDog/debugger-python
ddtrace/debugging/_origin/span.py                                       @DataDog/debugger-python
ddtrace/debugging/_probe/model.py                                       @DataDog/debugger-python
ddtrace/debugging/_probe/remoteconfig.py                                @DataDog/debugger-python
ddtrace/debugging/_signal/__init__.py                                   @DataDog/debugger-python
ddtrace/debugging/_signal/model.py                                      @DataDog/debugger-python
ddtrace/debugging/_uploader.py                                          @DataDog/debugger-python
ddtrace/propagation/http.py                                             @DataDog/apm-sdk-api-python
docs/configuration.rst                                                  @DataDog/python-guild
pyproject.toml                                                          @DataDog/python-guild
tests/debugging/conftest.py                                             @DataDog/debugger-python
tests/debugging/mocking.py                                              @DataDog/debugger-python
tests/debugging/origin/test_span.py                                     @DataDog/debugger-python
tests/debugging/signal/test_collector.py                                @DataDog/debugger-python
tests/debugging/test_debugger_span_decoration.py                        @DataDog/debugger-python
tests/debugging/utils.py                                                @DataDog/debugger-python
tests/submod/traced_stuff.py                                            @DataDog/apm-core-python
tests/tracer/test_context.py                                            @DataDog/apm-sdk-api-python

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-09 11:17:08

Comparing candidate commit 2d85475 in PR branch chore/trigger-probe with baseline commit 6bfe77e in branch main.

Found 1 performance improvements and 0 performance regressions! Performance is the same for 393 metrics, 2 unstable metrics.

scenario:httppropagationextract-all_styles_all_headers

• 🟩 execution_time [-5.733µs; -5.398µs] or [-8.568%; -8.068%]

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: chore/trigger-probe
Commit report: f108c5a
Test service: dd-trace-py

✅ 0 Failed, 1468 Passed, 0 Skipped, 22m 20.08s Total duration (14m 7.33s time saved)

[shatzi]

very cool progress, thank you

[shatzi]

Thank you!

[shatzi]

I think the only thing that left is probe budget for probe with session

[shatzi]

is now happen at the end of the signal. maybe this line should go back to enter?

[P403n1x87]

ah of course 🤦

[shatzi]

I think those test could benefit with validate that parsed session are correct as well. that we decode sesion id and level as expected and we got sessions.

second, can you add a test with just session1.session2 to ensure default level works?