Distributed tracing allows you to see the entire journey of your requests throughout a distributed system. For the Ruby agent, we offer two types of distributed tracing (for more details, see How span sampling works):
Standard (head-based sampling): Before any traces arrive, we determine a set percentage of traces to accept and analyze. This gives you a solid starting point to see how tracing can help you. It is turned on by default in Ruby agents 8.0.0 and higher.
Infinite Tracing (tail-based sampling): Our cloud-based service accepts all your traces and then sorts through them to find the most important. After you set up standard tracing, we recommend you add this option because it analyzes all of your traces and gives you configuration options to sample the traces that matter most to you.
All the steps you need to get started with distributed tracing are right here:
- New Ruby agents: Steps for head- and tail-based sampling for new agent installations
- Older Ruby agents: Tracing options if you have older Ruby agents
- Manual instrumentation: Tips if automatic instrumentation doesn't work
Whether you just want to try out standard distributed tracing (head-based sampling) or also want to set up Infinite Tracing (tail-based sampling), you need to start by setting up standard tracing. We'll get you through the APM agent installation to get head-based sampling going. After that, you can set up Infinite Tracing, which is optional but recommended.
This is the best approach to set up standard distributed tracing if you haven't installed any APM agents for your services yet, or if you want to instrument additional services.
If you already have some services instrumented with this APM agent, and you want to include them in distributed tracing, you'll need to manually enable distributed tracing for each service. See Options for older Ruby agents.
You'll need a New Relic account to set up distributed tracing. If you don't already have one, you can quickly create a free account.
Figure out which services you want to instrument so they each send trace data to New Relic.
You'll repeat the agent installation routine for each service involved in your transactions. If some of your services use other languages, simply repeat the installation steps for those languages.
To start the installation routine, click the tile below. When you are finished installing each agent, return here to see tips for viewing your traces.
After you instrument each of your services with APM agents, generate some traffic in your application so we can capture some traces. Here are two ways to view your traces in the UI:
For more help finding your traces in the UI:
Standard distributed tracing for APM agents (above) captures up to 10% of your traces, but if you want us to analyze all your data and find the most relevant traces, you can set up Infinite Tracing.
To learn more about this feature, see Infinite Tracing.
Before beginning, first ensure you meet the requirements.
The Infinite Tracing setup builds on the instrumentation step from the new agent installation for standard distributed tracing. After you finish installing the agents, continue with the trace observer setup.
The trace observer is a New Relic AWS-based service that collects and analyzes all your traces. Follow the instructions in Set up trace observer. When you're done, return here with your trace observer information and continue with the next step to configure the agent.
Infinite Tracing configuration settings include the standard distributed tracing plus information about the trace observer. Note that server-side configuration is not available for Infinite Tracing.
If you need help with proxy configuration, see Proxy support.
After you add the agent configuration settings, you should start seeing data in the New Relic UI. After you spend some time analyzing your data, you may want to adjust some of the features of Infinite Tracing:
- Configure trace observer monitoring
- Configure span attribute trace filter
- Configure random trace filter
If you have older Ruby agents, confirm the distributed tracing features you want are supported before enabling it.
After reviewing the compatibility information below, see Configure your older Ruby agents.
See the settings below to enable distributed tracing.
If you've been using an older agent without distributed tracing, before turning on distributed tracing, check out Impacts to APM.
Recommendation: Before performing any custom instrumentation, read:
If a service is not passing the trace header to other services, you can use the distributed tracing payload APIs to instrument the calling service and the called service. The calling service uses an API call to generate a payload, which is accepted by the called service.