(feat): Exception Replay endpoint #675
Merged
Conversation
This file contains hidden or 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
11 tasks
hghotra
approved these changes
May 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Implement the Exception Replay endpoint. This ports over the endpoint from datadog-agent: https://github.com/DataDog/datadog-agent/blob/ca681197f983c9d6b508e4b40d4526bb9a02c4ce/pkg/trace/api/endpoints.go#L140-L143
Exception Replay is a tracer feature that allows users to see local variables in the Datadog UI, kind of like a in a debugger in an IDE.
Exception replay can be enabled in the tracer with the
DD_EXCEPTION_REPLAY_ENABLED=trueenvironment variable. Currently, it's only supported in Python (in Lambda), but will be coming to Java and .NET very soon. Node will follow after.Testing
Manual testing:
Notes
https://datadoghq.atlassian.net/browse/SVLS-6837