You’ll need to install and deploy the following components for distributed tracing:

Client libraries (required) - These are language-specific implementations. An instrumented service creates spans when receiving new requests and attaches context meta-data to outgoing requests (Trace ID, Span ID, and so on). We support the Jaeger, Zipkin, OpenTracing, and OpenTelemetry instrumentation libraries.

Agent (optional) - The Agent component acts as a “buffer” between the tracer and the collector. Because it sits so close to the instrumentation, we use UDP to enhance performance and reduce round trips.

Collector (required) - The collector receives spans and runs them through a processing pipeline. It can receive spans from the agents or directly from the instrumentation, depending on the implementation. The collector is also responsible for batching spans and sending them to Distributed tracing architecture

Component overview

Because embraces open source, we opted for Jaeger. Except for the collector integration, everything you need to deploy is created and maintained by the open source community, which means that the support team can focus more effectively on the issues that the community can’t resolve. Jaeger Collector captures end-to-end distributed transactions from your applications and infrastructure with trace spans sent directly to via the Jaeger Collector which you install inside your environment.

The integration builds on the Jaeger Collector base image and uses the gRPC plugin framework, to enable communication between the collector and

Configure the extension with shell variables or environment variables. The required ports are described here.

 --network=net-logzio \
 --name=jaeger-logzio-collector \
 -p 14268:14268 \
 -p 9411:9411 \
 -p 14267:14267 \
 -p 14269:14269 \
 -p 14250:14250 \

The complete list of collector parameters is presented below. In addition to these parameters, you can also use Jaeger’s collector parameters.

Collector Parameter Description
ACCOUNT_TOKEN (Required) - The account token is required when you use the collector to send traces to
- Replace <SHIPPING-TOKEN> with the token of the account you want to send data to
How do I look up my account token?
REGION - Optional two-letter region code that determines the suggested listener URL (where you will be sending trace data to)
- Find your region code in the Regions and URLs table
- This parameter is left blank for US East (Northern Virginia)
How do I look up my region?
GRPC_STORAGE_PLUGIN_LOG_LEVEL - The lowest log level to send
- Default: warn
- From lowest to highest, log levels are: trace, debug, info, warn, error
- Controls logging only for the Jaeger Collector
- Does not affect Jaeger components
COLLECTOR_ZIPKIN_HTTP_PORT If you’re using a Zipkin implementation to create traces, set this optional environment variable to the HTTP port for the Zipkin collector service


You can deploy an agent as a sidecar container or as a Host Daemon. Although deploying an agent is not absolutely required for the instrumentation libraries which support sending spans directly to the collector, an agent can help with load balancing and enriching spans with additional tags that are not available at the collector level.

When deciding the best approach for your environment, consider the following factors:

  1. Do you need to lower the number of open connections? Sending a high number of spans to the collector can create many open connections. The agent can help with load balancing and lowering the number of connections from your application itself.
  2. Is there benefit in enriching the spans? The agent can enrich spans by adding tags that are not available at the collector level, such as region or pod name, which are often exposed at lower levels.

To deploy a Jaeger agent in a Docker environment

docker run \  ## make sure to expose only the ports you use in your deployment scenario!
  --rm \
 -p6831:6831/udp \
 -p6832:6832/udp \
 -p5778:5778/tcp \
 -p5775:5775/udp \
 jaegertracing/jaeger-agent:1.20  ## Use the relevant agent version

Refer to the Jaeger documentation for the agent version.

Kubernetes deployment reference

If you’re working with Kubernetes, use this yaml file as a reference to deploy the collector/agent, and use the output of kubectl explain deployment as your apiVersion value.