- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Exception Replay in APM Error Tracking automatically captures production variable values so you can reproduce exceptions from Error Tracking issues.
ddtrace
for Pythondd-trace-java
for Javadd-trace-dotnet
for .NETdd-trace-php
for PHPException Replay is only available in APM Error Tracking. Error Tracking for Logs and RUM is not supported.
7.44.0
or higher.ddtrace
version 1.16.0
or higher.dd-trace-java
version 1.35.0
or higher.dd-trace-dotnet
version 2.53.0
or higher.DD_EXCEPTION_DEBUGGING_ENABLED
environment variable to true
to run your service with Error Tracking Exception Replay enabled.For dd-trace-php
version 1.4.0
or higher, set the DD_EXCEPTION_REPLAY_ENABLED
environment variable to true
.
After you enable Sensitive Data Scrubbing, by default, variable data linked to specific identifiers deemed sensitive, such as password
and accessToken
, is automatically redacted. Enable Sensitive Data Scrubbing rules in Datadog. See the full list of redacted identifiers.
You can also scrub variable data for PII by:
dd_source:debugger
.To learn more about scrubbing variable data, see Dynamic Instrumentation Sensitive Data Scrubbing.
To keep the performance overhead of the feature at a minimum, error capturing is rate limited: one error per second includes variable data. If you don’t see variable values on a given trace: