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 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 tokens page. If you’re not an admin user for the account, consult with an account admin to get the Distributed Tracing token information.
When you’re logged into your main account, from the Settings menu, go to the Manage tokens page, open the Data shipping tokens tab, and select the Tracing option.
Find the Distributed Tracing account you want to ship to in the table, and copy the token. For information about how to manage your tracing data sources, see Manage a Distributed Tracing account.
For more details on locating the token, see Distributed Tracing shipping token.
You can find the 2-letter code for your region in the Region code column of Regions and Listener Hosts table. For US east, the region code is us.
If you need to clarify your region code, you can look it up in the General settings page, here: > Settings > General.
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 Kubernetes deployment reference topic.
<!-- removed blog link A Guide to Deploying Jaeger on Kubernetes in Production. ->