Before we run the demo application, let's make sure we can run the Jaeger backend to collect the traces, as otherwise we might get a lot of error logs. A production installation of the Jaeger backend would consist of many different components, including some highly scalable databases like Cassandra or Elasticsearch. For our experiments, we do not need that complexity or even the persistence layer. Fortunately, the Jaeger distribution includes a special component called all-in-one just for this purpose. It runs a single process that embeds all other components of a normal Jaeger installation, including the web user interface. Instead of a persistent storage, it keeps all traces in memory.
If you are using Docker, you can run Jaeger all-in-one with the following command:
$ docker run -d --name jaeger \ -p 6831:6831/udp \ -p 16686:16686 \ -p 14268:14268 \ jaegertracing/all-in-one:1.6
The -d
flag makes the process run in the background, detached from the terminal...