- Using Correlation IDs to investigate distributed requests
- Enabling distributed tracing
- Using Jaeger in the GitLab Development Kit
- Using Jaeger without the GitLab Developer Kit
GitLab is instrumented for distributed tracing. Distributed Tracing in GitLab is currently considered experimental, as it has not yet been tested at scale on GitLab.com.
According to Open Tracing:
Distributed tracing, also called distributed request tracing, is a method used to profile and monitor applications, especially those built using a microservices architecture. Distributed tracing helps to pinpoint where failures occur and what causes poor performance.
Distributed tracing is especially helpful in understanding the life cycle of a request as it passes through the different components of the GitLab application. At present, Workhorse, Rails, Sidekiq, and Gitaly support tracing instrumentation.
Distributed tracing adds minimal overhead when disabled, but imposes only small overhead when enabled and is therefore capable in any environment, including production. For this reason, it can be useful in diagnosing production issues, particularly performance problems.
The GitLab application passes correlation IDs between the various components in a request. A correlation ID is a token, unique to a single request, used to correlate a single request between different GitLab subsystems (for example, Rails, Workhorse). Since correlation IDs are included in log output, Engineers can use the correlation ID to correlate logs from different subsystems and better understand the end-to-end path of a request through the system. When a request traverses process boundaries, the correlation ID is injected into the outgoing request. This enables the propagation of the correlation ID to each downstream subsystem.
Correlation IDs are normally generated in the Rails application in response to certain web requests. Some user facing systems don’t generate correlation IDs in response to user requests (for example, Git pushes over SSH).
When integrating tracing into a new system, developers should avoid making certain assumptions about correlation IDs. The following guidelines apply to all subsystems at GitLab:
- Correlation IDs are always optional.
- Never have non-tracing features depend on the existence of a correlation ID from an upstream system.
- Correlation IDs are always free text.
- Correlation IDs should never be used to pass context (for example, a username or an IP address).
- Correlation IDs should never be parsed, or manipulated in other ways (for example, split).
The LabKit library provides a standardized interface for working with GitLab correlation IDs in the Go programming language. LabKit can be used as a reference implementation for developers working with tracing and correlation IDs on non-Go GitLab subsystems.
GitLab uses the
GITLAB_TRACING environment variable to configure distributed tracing. The same
configuration is used for all components (e.g., Workhorse, Rails, etc).
GITLAB_TRACING is not set, the application isn’t instrumented, meaning that there is
no overhead at all.
GITLAB_TRACING, a valid “configuration-string” value should be set, with a URL-like
In this example, we have the following hypothetical values:
driver: the driver. GitLab supports
jaeger. In future, other tracing implementations may also be supported.
param_value: these are driver specific configuration values. Configuration parameters for Jaeger are documented further on in this document they should be URL encoded. Multiple values should be separated by
&characters like a URL.
The first tracing implementation that GitLab supports is Jaeger, and the GitLab Development Kit supports distributed tracing with Jaeger out-of-the-box.
The easiest way to access tracing from a GDK environment is through the
performance-bar. This can be shown
b in the browser window.
Once the performance bar is enabled, click on the Trace link in the performance bar to go to the Jaeger UI.
The Jaeger search UI returns a query for the
Correlation-ID of the current request. Normally,
this search should return a single trace result. Clicking this result shows the detail of the
trace in a hierarchical time-line.
Distributed Tracing can be enabled in non-GDK development environments as well as production or staging environments, for troubleshooting. Please note that at this time, this functionality is experimental, and not supported in production environments at present. In this first release, it is intended to be used for debugging in development environments only.
Jaeger tracing can be enabled through a three-step process:
- Start Jaeger.
- Start the GitLab application.
- Go to the Jaeger Search UI in your browser.
Jaeger has many configuration options, but is very easy to start in an “all-in-one” mode which uses memory for trace storage (and is therefore non-persistent). The main advantage of “all-in-one” mode being ease of use.
For more detailed configuration options, refer to the Jaeger documentation.
If you have Docker available, the easier approach to running the Jaeger all-in-one is through Docker, using the following command:
$ docker run \ --rm \ -e COLLECTOR_ZIPKIN_HTTP_PORT=9411 \ -p 5775:5775/udp \ -p 6831:6831/udp \ -p 6832:6832/udp \ -p 5778:5778 \ -p 16686:16686 \ -p 14268:14268 \ -p 9411:9411 \ jaegertracing/all-in-one:latest
Without Docker, the all-in-one process is still easy to setup.
- Download the latest Jaeger release for your platform.
- Extract the archive and run the
This should start the process with the default listening ports.
Once you have Jaeger running, configure the
GITLAB_TRACING variable with the
appropriate configuration string.
TL;DR: If you are running everything on the same host, use the following value:
This configuration string uses the Jaeger driver
opentracing://jaeger with the following options:
|Configures Jaeger to send trace information to the HTTP endpoint running on |
|Configures Jaeger to use the constant sampler (either on or off).|
|Configures the |
Other parameter values are also possible:
|This is the default. Configures Jaeger to send trace information to the UDP listener on port |
|Configures Jaeger to use a probabilistic random sampler. The rate of samples is configured by the |
|Use a ratio of |
|Override the service name used by the Jaeger backend. This parameter takes precedence over the application-supplied value.|
GITLAB_TRACINGvalue should to be configured in the environment variables for all GitLab processes, including Workhorse, Gitaly, Rails, and Sidekiq.
GITLAB_TRACING environment variable is exported to all GitLab services, start the
GITLAB_TRACING is configured properly, the application logs this on startup:
13:41:53 gitlab-workhorse.1 | 2019/02/12 13:41:53 Tracing enabled ... 13:41:54 gitaly.1 | 2019/02/12 13:41:54 Tracing enabled ...
GITLAB_TRACING is not configured correctly, this issue is logged:
13:43:45 gitaly.1 | 2019/02/12 13:43:45 skipping tracing configuration step: tracer: unable to load driver mytracer
By default, GitLab ships with the Jaeger tracer, but other tracers can be included at compile time. Details of how this can be done are included in the LabKit tracing documentation.
If no log messages about tracing are emitted, the
GITLAB_TRACING environment variable is likely
By default, the Jaeger search UI is available at http://localhost:16686/search.