Overview

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.

Usage

Statements on this page apply to HTTP API tests, Multistep API tests, and browser tests for APM.

Prerequisites

• Your service, and the endpoint your test is running on, is traced on the APM side.
• Your service uses an HTTP server.
• Your HTTP server is using a library that supports distributed tracing.

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/*

Supported libraries

The following Datadog tracing libraries are supported:

How are traces linked to tests?

Datadog uses the distributed tracing protocol and sets up the following HTTP headers:

How long are traces retained?

These traces are retained for 15 days with the Synthetics Default retention filter, just like your classical APM traces.

Further Reading

Additional helpful documentation, links, and articles:

Introducing Datadog Synthetic MonitoringBLOG APM and Distributed TracingDOCUMENTATION Ease troubleshooting with cross product correlation.GUIDE