ddtrace/tracer: noDebugStack config reports to telemetry under distinct key debug_stack_enabled #2798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The
noDebugStack
tracer configuration now reports telemetry under the keydebug_stack_enabled
.Note: New
debug_stack_enabled
field added to telemetry backend here: https://github.com/DataDog/dd-go/pull/143865Motivation
Prior to this change, the
noDebugStack
config was incorrectly reporting telemetry under the keytrace_debug_enabled
.Reviewer's Checklist
Unsure? Have a question? Request a review!