chore(crashtracker): add profiler_config tag if profiler enabled

[taegyunkim]

The previous attempt set the tag after crashtracker has started, and tags didn't show up in the logs.

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

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 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[bot]]

CODEOWNERS have been resolved as:

ddtrace/internal/core/crashtracking.py                                  @DataDog/apm-core-python
ddtrace/profiling/profiler.py                                           @DataDog/profiling-python
ddtrace/settings/profiling.py                                           @DataDog/profiling-python
tests/internal/crashtracker/test_crashtracker.py                        @DataDog/apm-core-python

[datadog-dd-trace-py-rkomorn[bot]]

Datadog Report

Branch report: taegyunkim/crashtracker-profiler-config Commit report: bc549ae Test service: dd-trace-py

:white_check_mark: 0 Failed, 1468 Passed, 0 Skipped, 26m 10.08s Total duration (12m 0.77s time saved)

[pr-commenter[bot]]

Benchmarks

Benchmark execution time: 2024-11-21 19:13:09

Comparing candidate commit a5a04a7c1aebb058399497feeda4bd624e387e28 in PR branch taegyunkim/crashtracker-profiler-config with baseline commit d792c3dc3c7452ed64524ea38d0b9c9116330a73 in branch main.

Found 2 performance improvements and 4 performance regressions! Performance is the same for 382 metrics, 2 unstable metrics.

scenario:iast_aspects-ljust_aspect

• 🟥 execution_time [+1.451µs; +1.556µs] or [+10.461%; +11.220%]

scenario:iast_aspects-ospathbasename_aspect

• 🟥 execution_time [+555.407ns; +599.398ns] or [+16.702%; +18.025%]

scenario:iast_aspects-ospathjoin_aspect

• 🟥 execution_time [+463.758ns; +526.577ns] or [+9.095%; +10.327%]

scenario:iast_aspects-rsplit_aspect

• 🟩 execution_time [-196.418ns; -165.813ns] or [-10.206%; -8.616%]

scenario:iast_aspects-split_aspect

• 🟩 execution_time [-215.894ns; -186.554ns] or [-11.519%; -9.953%]

scenario:iast_aspects-upper_aspect

• 🟥 execution_time [+219.238ns; +251.825ns] or [+7.946%; +9.127%]