Skip to content

Conversation

@P403n1x87
Copy link
Contributor

Motivation

System tests are still using the deprecated DD_EXCEPTION_DEBUGGING_ENABLED variable.

Changes

We remove any references of it and replace it with the official one where appropriate.

Workflow

  1. ⚠️ Create your PR as draft ⚠️
  2. Work on you PR until the CI passes
  3. Mark it as ready for review
    • Test logic is modified? -> Get a review from RFC owner.
    • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

  • If PR title starts with [<language>], double-check that only <language> is impacted by the change
  • No system-tests internal is modified. Otherwise, I have the approval from R&P team
  • A docker base image is modified?
    • the relevant build-XXX-image label is present
  • A scenario is added (or removed)?

@P403n1x87 P403n1x87 requested review from a team as code owners October 28, 2025 11:33
@P403n1x87 P403n1x87 requested review from ojproductions and removed request for a team October 28, 2025 11:33
@github-actions
Copy link
Contributor

CODEOWNERS have been resolved as:

utils/_context/_scenarios/__init__.py                                   @DataDog/system-tests-core
utils/telemetry/intake/static/config_norm_rules.json                    @DataDog/apm-sdk

@P403n1x87 P403n1x87 force-pushed the chore/remove-deprecated-er-var branch from b878bf5 to 8bc334d Compare October 28, 2025 11:35
Copy link
Collaborator

@cbeauchesne cbeauchesne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non blocking comment : Do the old value will be in tracer with backports ? if yes, we need to keep a mechanism that adds it for those older versions. Ping me if yes, I'll show you what is the good pattern for that.

@P403n1x87
Copy link
Contributor Author

Non blocking comment : Do the old value will be in tracer with backports ? if yes, we need to keep a mechanism that adds it for those older versions. Ping me if yes, I'll show you what is the good pattern for that.

The support for this old variable will be dropped in v4. The new variable has been around for a long time and all the versions that we still support have it, so the deprecated one is not needed as long as we're testing versions for which we still offer support.

"DD_ERROR_TRACKING_REPORT_HANDLED_ERRORS_ENABLED_MODULES": "error_tracking_report_handled_errors_enabled_modules",
"DD_ERROR_TRACKING_REPORT_HANDLED_ERRORS_LOGGER": "error_tracking_report_handled_errors_logger",
"DD_EXCEPTION_DEBUGGING_CAPTURE_FULL_CALLSTACK_ENABLED": "exception_debugging_capture_full_callstack_enabled",
"DD_EXCEPTION_DEBUGGING_ENABLED": "exception_replay_enabled",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this file is meant to be 1:1 with the dd-go/config_norm_rules.json, so we should likely leave these, especially since older tracers will continue to emit the exception debugging value.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants