Synthetic transaction traces connect your synthetic results to APM transaction traces. While synthetic results capture browser-side details from each synthetic check, transaction traces capture the activity on your app server. When you connect synthetic monitors to APM, you can view both sides of every synthetic's run.
Synthetic monitoring and APM must be on the same account for transaction traces to make these connections.
Synthetic transaction traces are enabled by default in the following APM agent versions:
- Java: 3.14.0 or higher
- .NET: 188.8.131.52 or higher
- Node.js: 1.16.1 or higher
- PHP: 184.108.40.206 or higher
- Python: 220.127.116.11 or higher
- Ruby: 3.9.7 or higher
To view synthetic transaction traces, create a monitor that checks a website for which you have enabled synthetic transaction traces. Then, from the Summary page in the Synthetics UI, click a dot in a location chart to open the result details. Hover over any of the timeline charts to get links to transaction traces.
With the new Summary view enabled, you can click any data point in location charts to access the waterfall result details.
New Relic collects up to 20 synthetic transaction traces per application each minute. If your app receives more than 20 synthetic checks per minute, not every synthetic result will include a synthetic trace.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.