Get set and get ready: This section describes what you have to do to get set up - before you can use Distributed Tracing in Logz.io.

If you already have Jaeger installed locally, learn how to go about Making the easy switch from your local Jaeger installation to Logz.io Distributed Tracing.

To set up Distributed Tracing:

Set up instrumentation

Determine the best instrumentation strategy for your system: Manual or automatic instrumentation. Read more about setting up instrumentation.

Look up your Distributed Tracing Token and Region information in Logz.io
  • You must have admin permissions for the Logz.io account to view the Manage accounts page. If you’re not an admin user for the account, consult with an account admin to get the Distributed Tracing token information.

    From your main account, go to the Manage accounts page of your Operations workspace.
    It can be reached by selecting > Settings > Manage accounts.

    Distributed Tracing token location

    Scroll to the Distributed Tracing account section and click the account you want to ship to.

    The account’s token and other settings are displayed when you click the relevant tracing account name at the bottom of the section. Reveal Distributed Tracing Token

  • You can find the Listener host URL for your region in the Regions and Listener Hosts table.
    If you need to clarify your region code, you can look it up in the General settings page, here: > Settings > General. Navigate to general settings

Deploy tracing components

Decide on your tracing source, make deployment decisions, and decide whether or not to use an agent to send tracing data to Logz.io. Read more about deploying tracing components.

If you’re deploying distributed tracing on Kubernetes, we recommend the following blog post: A Guide to Deploying Jaeger on Kubernetes in Production.