• 로그인무료 계정

Distributed tracing setup options

We recommend you do an initial setup of distributed tracing and consider the advanced Infinite Tracing feature if you are not getting the data you need. 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:

Diagram showing the three steps to set up distributed tracing
  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:
A sample environment diagram showing how you might identify services.
  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:

    New Relic Android Mobile
    Android mobile monitoring
    C
    APM: C
    Golang
    APM: Golang
    Java
    APM: Java
    .NET
    APM: .NET
    Node.js
    APM: Node.js
    PHP
    APM: PHP
    Python
    APM: Python
    Ruby
    APM: Ruby
    AWS Lambda Functions
    AWS Lambda Functions
    AWS X-Ray
    AWS X-Ray
    New Relic Browser
    Browser monitoring
    New Relic iOS Mobile
    iOS mobile monitoring
    Kamon
    Kamon
    OpenTelemetry
    OpenTelemetry
    New Relic format: use your own integration
    Trace API: generic format
    Zipkin format custom integration
    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.