• Log inStart now

Distributed tracing setup options

We recommend you review our docs on sampling types before you get started to determine if you'd like to use standard distributed tracing or Infinite Tracing. Also, if you are currently using New Relic APM agents and would like to enable distributed tracing, see our planning guide.

Ready to get started? If you don't already have one, sign up for a New Relic account. It's free, forever!

To set up distributed tracing, you'll complete three general steps:

  1. Identify services: Identify and write down the endpoints, services, languages, and systems that are used to complete this request (you'll need this information in the next step). If you have an environment diagram like the following, you could use it to create a list of services handling requests:
  1. Instrument services: Instrument each service you identify so it can send your trace data. Some tools, such as APM agents, instrument services automatically, while other tools require you to insert some code in the services. Click the icon below for instrumentation steps:

    Android mobile monitoring
    APM: C
    APM: Golang
    APM: Java
    APM: .NET
    APM: Node.js
    APM: PHP
    APM: Python
    APM: Ruby
    AWS Lambda Functions
    AWS X-Ray
    Browser monitoring
    iOS mobile monitoring
    Kamon
    OpenTelemetry
    Trace API: generic format
    Trace API: Zipkin format
  2. View traces: After you instrument the services, generate some traffic in your application, and then go to the New Relic UI to see your trace data.

Copyright © 2022 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.