Deployment

See also:

• Operator for Kubernetes
• Frontend/UI
• Windows
• CLI Flags

The main Jaeger backend components are released as Docker images on Docker Hub:

There are orchestration templates for running Jaeger with:

• Kubernetes: github.com/jaegertracing/jaeger-kubernetes,
• OpenShift: github.com/jaegertracing/jaeger-openshift.

Configuration Options

Jaeger binaries can be configured in a number of ways (in the order of decreasing priority):

• command line arguments,
• environment variables,
• configuration files in JSON, TOML, YAML, HCL, or Java properties formats.To see the complete list of options, run the binary with help command. Options that are specific to a certain storage backend are only listed if the storage type is selected. For example, to see all available options in the Collector with Cassandra storage:

$ docker run --rm \
    -e SPAN_STORAGE_TYPE=cassandra \
    jaegertracing/jaeger-collector:1.15 \
    help

In order to provide configuration parameters via environment variables, find the respective command line option and convert its name to UPPER_SNAKE_CASE, for example:

Agent

Jaeger client libraries expect jaeger-agent process to run locally on each host.The agent exposes the following ports:

It can be executed directly on the host or via Docker, as follows:

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

Discovery System Integration

The agents can connect point to point to a single collector address, which could beload balanced by another infrastructure component (e.g. DNS) across multiple collectors.The agent can also be configured with a static list of collector addresses.

On Docker, a command like the following can be used:

docker run \
  --rm \
  -p5775:5775/udp \
  -p6831:6831/udp \
  -p6832:6832/udp \
  -p5778:5778/tcp \
  jaegertracing/jaeger-agent:1.15 \
  --reporter.grpc.host-port=jaeger-collector.jaeger-infra.svc:14250

Or use —reporter.tchannel.host-port=jaeger-collector.jaeger-infra.svc:14267 to uselegacy tchannel reporter.

When using gRPC, you have several options for load balancing and name resolution:

• Single connection and no load balancing. This is the default if you specify a single host:port. (example: —reporter.grpc.host-port=jaeger-collector.jaeger-infra.svc:14250)
• Static list of hostnames and round-robin load balancing. This is what you get with a comma-separated list of addresses. (example: reporter.grpc.host-port=jaeger-collector1:14250,jaeger-collector2:14250,jaeger-collector3:14250)
• Dynamic DNS resolution and round-robin load balancing. To get this behaviour, prefix the address with dns:/// and gRPC will attempt to resolve the hostname using SRV records (for external load balancing), TXT records (for service configs), and A records. Refer to the gRPC Name Resolution docs and the dns_resolver.go implementation for more info. (example: —reporter.grpc.host-port=dns:///jaeger-collector.jaeger-infra.svc:14250)

Agent level tags

Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag —jaeger.tags=key1=value1,key2=value2,…,keyn=valuen. Tags can also be set through an environment flag like so - —jaeger.tags=key=${envFlag:defaultValue} - The tag value will be set to the value of the envFlag environment key and defaultValue if not set. This feature is not supported for the tchannel reporter, enabled using the flags —collector.host-port or —reporter.tchannel.host-port.

Collectors

The collectors are stateless and thus many instances of jaeger-collector can be run in parallel.Collectors require almost no configuration, except for the location of Cassandra cluster,via —cassandra.keyspace and —cassandra.servers options, or the location of Elasticsearch cluster, via—es.server-urls, depending on which storage is specified. To see all command line options run

go run ./cmd/collector/main.go -h

or, if you don’t have the source code

docker run -it --rm jaegertracing/jaeger-collector:1.15 -h

At default settings the collector exposes the following ports:

Storage Backends

Collectors require a persistent storage backend. Cassandra and Elasticsearch are the primary supported storage backends. Additional backends are discussed here.

The storage type can be passed via SPAN_STORAGE_TYPE environment variable. Valid values are cassandra, elasticsearch, kafka (only as a buffer), grpc-plugin, badger (only with all-in-one) and memory (only with all-in-one).

As of version 1.6.0, it’s possible to use multiple storage types at the same time by providing a comma-separated list of valid types to the SPAN_STORAGE_TYPE environment variable.It’s important to note that all listed storage types are used for writing, but only the first type in the list will be used for reading and archiving.

Memory

The in-memory storage is not intended for production workloads. It’s intended as a simple solution to get started quickly anddata will be lost once the process is gone.

By default, there’s no limit in the amount of traces stored in memory but a limit can be established by passing aninteger value via —memory.max-traces.

Badger - local storage

Experimental since Jaeger 1.9

Badger is an embedded local storage, only availablewith all-in-one distribution. By default it acts as an ephemeral storage using a temporary filesystem.This can be overridden by using the —badger.ephemeral=false option.

docker run \
  -e SPAN_STORAGE_TYPE=badger \
  -e BADGER_EPHEMERAL=false \
  -e BADGER_DIRECTORY_VALUE=/badger/data \
  -e BADGER_DIRECTORY_KEY=/badger/key \
  -v <storage_dir_on_host>:/badger \
  -p 16686:16686 \
  jaegertracing/all-in-one:1.15

Cassandra

Supported versions: 3.4+

Deploying Cassandra itself is out of scope for our documentation. One goodsource of documentation is the Apache Cassandra Docs.

Configuration

Minimal

docker run \
  -e SPAN_STORAGE_TYPE=cassandra \
  -e CASSANDRA_SERVERS=<...> \
  jaegertracing/jaeger-collector:1.15

All options

To view the full list of configuration options, you can run the following command:

docker run \
  -e SPAN_STORAGE_TYPE=cassandra  \
  jaegertracing/jaeger-collector:1.15 \
  --help

Schema script

A script is provided to initialize Cassandra keyspace and schemausing Cassandra’s interactive shell cqlsh:

MODE=test sh ./plugin/storage/cassandra/schema/create.sh | cqlsh

For production deployment, pass MODE=prod DATACENTER={datacenter} arguments to the script,where {datacenter} is the name used in the Cassandra configuration / network topology.

The script also allows overriding TTL, keyspace name, replication factor, etc.Run the script without arguments to see the full list of recognized parameters.

TLS support

Jaeger supports TLS client to node connections as long as you’ve configuredyour Cassandra cluster correctly. After verifying with e.g. cqlsh, you canconfigure the collector and query like so:

docker run \
  -e CASSANDRA_SERVERS=<...> \
  -e CASSANDRA_TLS=true \
  -e CASSANDRA_TLS_SERVER_NAME="CN-in-certificate" \
  -e CASSANDRA_TLS_KEY=<path to client key file> \
  -e CASSANDRA_TLS_CERT=<path to client cert file> \
  -e CASSANDRA_TLS_CA=<path to your CA cert file> \
  jaegertracing/jaeger-collector:1.15

The schema tool also supports TLS. You need to make a custom cqlshrc file likeso:

# Creating schema in a cassandra cluster requiring client TLS certificates.
#
# Create a volume for the schema docker container containing four files:
# cqlshrc: this file
# ca-cert: the cert authority for your keys
# client-key: the keyfile for your client
# client-cert: the cert file matching client-key
#
# if there is any sort of DNS mismatch and you want to ignore server validation
# issues, then uncomment validate = false below.
#
# When running the container, map this volume to /root/.cassandra and set the
# environment variable CQLSH_SSL=--ssl
[ssl]
certfile = ~/.cassandra/ca-cert
userkey = ~/.cassandra/client-key
usercert = ~/.cassandra/client-cert
# validate = false

Elasticsearch

Supported in Jaeger since 0.6.0Supported versions: 5.x, 6.x, 7.x

Elasticsearch version is automatically retrieved from root/ping endpoint.Based on this version Jaeger uses compatible index mappings and Elasticsearch REST API.The version can be explicitly provided via —es.version= flag.

Elasticsearch does not require initialization other thaninstalling and running Elasticsearch.Once it is running, pass the correct configuration values to the Jaeger collector and query service.

Configuration

Minimal

docker run \
  -e SPAN_STORAGE_TYPE=elasticsearch \
  -e ES_SERVER_URLS=<...> \
  jaegertracing/jaeger-collector:1.15

All options

To view the full list of configuration options, you can run the following command:

docker run \
  -e SPAN_STORAGE_TYPE=elasticsearch \
  jaegertracing/jaeger-collector:1.15 \
  --help

Shards and Replicas for Elasticsearch indices

Shards and replicas are some configuration values to take special attention to, because this is decided uponindex creation. This article goes intomore information about choosing how many shards should be chosen for optimization.

Upgrade Elasticsearch version

Elasticsearch defines wire and index compatibility versions. The index compatibility definesthe minimal version a node can read data from. For example Elasticsearch 7 can read indicescreated by Elasticsearch 6, however it cannot read indices created by Elasticsearch 5 eventhough they use the same index mappings. Therefore upgrade from Elasticsearch 6 to 7 does not require anydata migration. However, upgrade from Elasticsearch 5 to 7 has to be done through Elasticsearch 6 and waituntil indices created by ES 5.x are removed or explicitly reindexed.

Refer to the Elasticsearch documentationfor wire and index compatibility versions. Generally this information can be retrieved from root/ping REST endpoint.

Reindex

Manual reindexing can be used when upgrading from Elasticsearch 5 to 7 (through Elasticsearch 6)without waiting until indices created by Elasticsearch 5 are removed.

• Reindex all span indices to new indices with suffix -1:

curl -ivX POST -H "Content-Type: application/json" http://localhost:9200/_reindex -d @reindex.json
{
  "source": {
    "index": "jaeger-span-*"
  },
  "dest": {
    "index": "jaeger-span"
  },
  "script": {
    "lang": "painless",
    "source": "ctx._index = 'jaeger-span-' + (ctx._index.substring('jaeger-span-'.length(), ctx._index.length())) + '-1'"
  }
}

• Delete indices with old mapping:

curl -ivX DELETE -H "Content-Type: application/json" http://localhost:9200/jaeger-span-\*,-\*-1

• Create indices without -1 suffix:

curl -ivX POST -H "Content-Type: application/json" http://localhost:9200/_reindex -d @reindex.json
{
  "source": {
    "index": "jaeger-span-*"
  },
  "dest": {
    "index": "jaeger-span"
  },
  "script": {
    "lang": "painless",
    "source": "ctx._index = 'jaeger-span-' + (ctx._index.substring('jaeger-span-'.length(), ctx._index.length() - 2))"
  }
}

• Remove suffixed indices:

curl -ivX DELETE -H "Content-Type: application/json" http://localhost:9200/jaeger-span-\*-1

Run the commands analogically for other Jaeger indices.

There might exist more effective migration procedure. Please share with the community any findings.

Kafka

Supported in Jaeger since 1.6.0Supported Kafka versions: 0.9+

Kafka can be used as an intermediary buffer between collector and an actual storage.The collector is configured with SPAN_STORAGE_TYPE=kafka that makes it write all received spansinto a Kafka topic. A new component Ingester, added in version 1.7.0, is used to read fromKafka and store spans in another storage backend (Elasticsearch or Cassandra).

Writing to Kafka is particularly useful for building post-processing data pipelines.

Configuration

Minimal

docker run \
  -e SPAN_STORAGE_TYPE=kafka \
  -e KAFKA_BROKERS=<...> \
  -e KAFKA_TOPIC=<...> \
  jaegertracing/jaeger-collector:1.15

All options

To view the full list of configuration options, you can run the following command:

docker run \
  -e SPAN_STORAGE_TYPE=kafka \
  jaegertracing/jaeger-collector:1.15 \
  --help

Topic & partitions

Unless your Kafka cluster is configured to automatically create topics, you will need to create it ahead of time. You can refer to the Kafka quickstart documentation to learn how.

You can find more information about topics and partitions in general in the official documentation. This article provide more details about how to choose the number of partitions.

Storage plugin

Jaeger supports gRPC based storage plugins. For more information refer to jaeger/plugin/storage/grpc

Available plugins:

• InfluxDB

docker run \
  -e SPAN_STORAGE_TYPE=grpc-plugin \
  -e GRPC_STORAGE_PLUGIN_BINARY=<...> \
  -e GRPC_STORAGE_PLUGIN_CONFIGURATION_FINE=<...> \
  jaegertracing/all-in-one:1.15

Ingester

jaeger-ingester is a service which reads span data from Kafka topic and writes it to another storage backend (Elasticsearch or Cassandra).

To view all exposed configuration options run the following command:

docker run \
  -e SPAN_STORAGE_TYPE=cassandra \
  jaegertracing/jaeger-ingester:1.15
  --help

Query Service & UI

jaeger-query serves the API endpoints and a React/Javascript UI.The service is stateless and is typically run behind a load balancer, such as NGINX.

At default settings the query service exposes the following port(s):

Minimal deployment example (Elasticsearch backend):

docker run -d --rm \
  -p 16686:16686 \
  -p 16687:16687 \
  -e SPAN_STORAGE_TYPE=elasticsearch \
  -e ES_SERVER_URLS=http://<ES_SERVER_IP>:<ES_SERVER_PORT> \
  jaegertracing/jaeger-query:1.15

UI Base Path

The base path for all jaeger-query HTTP routes can be set to a non-root value, e.g. /jaeger would cause all UI URLs to start with /jaeger. This can be useful when running jaeger-query behind a reverse proxy.

The base path can be configured via the —query.base-path command line parameter or the QUERY_BASE_PATH environment variable.

UI Customization and Embedding

Please refer to the dedicated Frontend/UI page.

Aggregation Jobs for Service Dependencies

Production deployments need an external process which aggregates data and creates dependency links between services. Project spark-dependencies is a Spark job which derives dependency links and stores them directly to the storage.

Configuration

All binaries accepts command line properties and environmental variables, power by viper and cobra libraries. Please refer to the CLI Flags page for more information.