-
Notifications
You must be signed in to change notification settings - Fork 417
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(debugging): ensure dynamic instrumentation enabled
With the introduction of exception debugging, the new enablement logic caused the dynamic instrumentation to not register with the remoteconfig client when the programmatic API was used, unless DD_DYNAMIC_INSTRUMENTATION_ENABLED is also set. Since this is not the documented behaviour, we make this fix to align with the expected behaviour of the programmatic API.
- Loading branch information
Showing
3 changed files
with
20 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 6 additions & 0 deletions
6
releasenotes/notes/fix-di-enable-programmatic-api-2dd583ac87af5451.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
--- | ||
fixes: | ||
- | | ||
dynamic instrumentation: Fixed the programmatic API to ensure that the | ||
dynamic instrumentation service is fully enabled when | ||
``Dynamic Instrumentation.enable()`` is called. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters