Skip to content

fix(internal): fix inconsistencies with tracer flare implementation #13417

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

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

brettlangdon
Copy link
Member

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

Copy link
Contributor

CODEOWNERS have been resolved as:

ddtrace/internal/flare/flare.py                                         @DataDog/apm-core-python
ddtrace/internal/flare/handler.py                                       @DataDog/apm-core-python
ddtrace/internal/remoteconfig/products/client.py                        @DataDog/remote-config @DataDog/apm-core-python

Copy link
Contributor

github-actions bot commented May 14, 2025

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 231 ± 2 ms.

The average import time from base is: 233 ± 2 ms.

The import time difference between this PR and base is: -2.02 ± 0.08 ms.

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.976 ms (0.86%)
ddtrace.bootstrap.sitecustomize 1.303 ms (0.56%)
ddtrace.bootstrap.preload 1.303 ms (0.56%)
ddtrace.internal.remoteconfig.client 0.647 ms (0.28%)
ddtrace 0.673 ms (0.29%)

@pr-commenter
Copy link

pr-commenter bot commented May 14, 2025

Benchmarks

Benchmark execution time: 2025-05-15 09:26:55

Comparing candidate commit a8ed143 in PR branch brettlangdon/fix.flares with baseline commit ecc84b1 in branch main.

Found 0 performance improvements and 4 performance regressions! Performance is the same for 519 metrics, 5 unstable metrics.

scenario:iast_aspects-format_map_aspect

  • 🟥 execution_time [+447.548ns; +574.960ns] or [+14.018%; +18.009%]

scenario:iast_aspects-ljust_aspect

  • 🟥 execution_time [+1.336µs; +1.451µs] or [+10.371%; +11.258%]

scenario:iast_aspects-swapcase_aspect

  • 🟥 execution_time [+193.530ns; +229.166ns] or [+7.827%; +9.269%]

scenario:iast_aspects-upper_aspect

  • 🟥 execution_time [+228.311ns; +275.896ns] or [+10.081%; +12.182%]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants