| title | metaDescription | redirects | freshnessValidatedDate | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Distributed tracing setup options |
Here are links to help you get started with distributed tracing |
|
never |
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 agents and would like to enable distributed tracing, see our planning guide.
To set up distributed tracing, you'll complete three general steps:
-
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:
-
Instrument services: Instrument each service you identify so it can send your trace data. Some tools, such as agents, instrument services automatically, while other tools require you to insert some code in the services. Click the icon below for instrumentation steps:
} /><TechTile name="APM: C" to="/docs/apm/agents/c-sdk/instrumentation/distributed-tracing-c-sdk" icon={
}
/><TechTile name="APM: Golang" to="/docs/apm/agents/go-agent/configuration/distributed-tracing-go-agent" icon={
}
/><TechTile name="APM: Java" to="/docs/apm/agents/java-agent/configuration/distributed-tracing-java-agent" icon={
}
/><TechTile name="APM: .NET" to="/docs/apm/agents/net-agent/configuration/distributed-tracing-net-agent" icon={
}
/><TechTile name="APM: Node.js" to="/docs/apm/agents/nodejs-agent/installation-configuration/distributed-tracing-nodejs-agent" icon={
}
/><TechTile name="APM: PHP" to="/docs/apm/agents/php-agent/configuration/distributed-tracing-php-agent" icon={
}
/><TechTile name="APM: Python" to="/docs/apm/agents/python-agent/configuration/distributed-tracing-python-agent" icon={
}
/><TechTile name="APM: Ruby" to="/docs/apm/agents/ruby-agent/configuration/distributed-tracing-ruby-agent" icon={
}
/><TechTile name="AWS Lambda Functions" to="/docs/serverless-function-monitoring/aws-lambda-monitoring/enable-lambda-monitoring/configure-serverless-monitoring-aws-lambda" icon={
}
/><TechTile name="AWS X-Ray" to="/docs/integrations/amazon-integrations/aws-integrations-list/aws-x-ray-monitoring-integration" icon={
}
/><TechTile name="Browser monitoring" to="/docs/browser/new-relic-browser/browser-pro-features/browser-data-distributed-tracing" icon={
}
/><TechTile name="iOS mobile monitoring" to="/docs/mobile-monitoring/new-relic-mobile-ios/get-started/new-relic-ios-and-dt" icon={
}
/><TechTile name="Kamon" to="/docs/integrations/open-source-telemetry-integrations/kamon/kamon-reporter" icon={
}
/><TechTile name="OpenTelemetry" to="/docs/integrations/open-source-telemetry-integrations/opentelemetry/opentelemetry-quick-start" icon={
}
/><TechTile name="Trace API: generic format" to="/docs/understand-dependencies/distributed-tracing/trace-api/report-new-relic-format-traces-trace-api" icon={
}
/><TechTile name="Trace API: Zipkin format" to="/docs/understand-dependencies/distributed-tracing/trace-api/report-zipkin-format-traces-trace-api" icon={
}
/>
-
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.
