- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
The APM integration with Synthetic Monitoring allows you to go from a test run that potentially failed to the root cause of the issue by looking at the trace generated by that test run.
Having network-related specifics (thanks to your test) as well as backend, infrastructure, and log information (thanks to your trace) allows you to access a new level of details about the way your application is behaving, as experienced by your user.
Statements on this page apply to HTTP API tests, Multistep API tests, and browser tests for APM.
Create a test that hits your traced HTTP server, and Datadog automatically links the trace generated by your server to the corresponding test result.
To link browser test results, allow the URLs you want the APM integration headers added to. You can do this in Synthetic Settings. Use *
for wildcards:
https://*.datadoghq.com/*
The following Datadog tracing libraries are supported:
Datadog uses the distributed tracing protocol and sets up the following HTTP headers:
x-datadog-trace-id
x-datadog-parent-id: 0
x-datadog-origin: synthetics
ingestion_reason:synthetics
.x-datadog-origin: synthetics-browser
ingestion_reason:synthetics-browser
.x-datadog-sampling-priority: 1
traceparent: [version]-[trace id]-[parent id]-[trace flags]
version
: The specification assumes version is set to 00
.trace id
: 128 bits trace ID, hexadecimal on 32 characters. The source trace ID is 64 bits to maintain compatibility with APM.parent id
: 64 bits span ID, hexadecimal on 16 characters.trace flags
: Sampled (01
) or not sampled (00
)traceparent: 00-00000000000000008448eb211c80319c-b7ad6b7169203331s-01
These traces are retained for 15 days with the Synthetics Default
retention filter, just like your classical APM traces.
Additional helpful documentation, links, and articles: