2020-07-09 23:08:53 -04:00
---
stage: Monitor
2022-01-27 13:14:37 -05:00
group: Respond
2020-11-26 01:09:20 -05:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-07-09 23:08:53 -04:00
---
2022-05-13 17:08:46 -04:00
# Tracing (DEPRECATED) **(FREE SELF)**
2020-07-09 23:08:53 -04:00
2022-01-10 19:13:53 -05:00
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42645) from GitLab Ultimate to GitLab Free in 13.5.
> - [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346540) in GitLab 14.7.
2022-05-13 17:08:46 -04:00
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/359904) behind a [feature flag](../administration/feature_flags.md) named `monitor_tracing` in GitLab 15.0. Disabled by default.
2022-01-10 19:13:53 -05:00
WARNING:
This feature is in its end-of-life process. It is [deprecated ](https://gitlab.com/gitlab-org/gitlab/-/issues/346540 )
2022-05-13 17:08:46 -04:00
in GitLab 14.7.
It will be removed completely in GitLab 15.2.
FLAG:
On self-managed GitLab, by default this feature is not available. To make it available, ask an administrator to [enable the feature flag ](../administration/feature_flags.md ) named `monitor_tracing` .
On GitLab.com, this feature is not available.
This feature is not recommended for production use.
2020-07-09 23:08:53 -04:00
2021-03-23 05:09:17 -04:00
Tracing provides insight into the performance and health of a deployed application, tracking each
function or microservice that handles a given request. Tracing makes it easy to understand the
end-to-end flow of a request, regardless of whether you are using a monolithic or distributed
system.
2020-07-09 23:08:53 -04:00
2021-03-23 05:09:17 -04:00
## Install Jaeger
2020-07-09 23:08:53 -04:00
2021-03-23 05:09:17 -04:00
[Jaeger ](https://www.jaegertracing.io/ ) is an open source, end-to-end distributed tracing system
used for monitoring and troubleshooting microservices-based distributed systems. To learn more about
installing Jaeger, read the official
[Getting Started documentation ](https://www.jaegertracing.io/docs/latest/getting-started/ ).
2020-07-09 23:08:53 -04:00
2021-03-23 05:09:17 -04:00
See also:
2020-07-09 23:08:53 -04:00
2021-03-23 05:09:17 -04:00
- An [all-in-one Docker image ](https://www.jaegertracing.io/docs/latest/getting-started/#all-in-one ).
- Deployment options for:
- [Kubernetes ](https://github.com/jaegertracing/jaeger-kubernetes ).
- [OpenShift ](https://github.com/jaegertracing/jaeger-openshift ).
2020-07-09 23:08:53 -04:00
2021-03-23 05:09:17 -04:00
## Link to Jaeger
2020-07-09 23:08:53 -04:00
GitLab provides an easy way to open the Jaeger UI from within your project:
1. [Set up Jaeger ](https://www.jaegertracing.io ) and configure your application using one of the
[client libraries ](https://www.jaegertracing.io/docs/latest/client-libraries/ ).
2021-06-15 14:09:57 -04:00
1. Navigate to your project's **Settings > Monitor** and provide the Jaeger URL.
2020-07-09 23:08:53 -04:00
1. Click **Save changes** for the changes to take effect.
2021-06-15 14:09:57 -04:00
1. You can now visit **Monitor > Tracing** in your project's sidebar and GitLab redirects you to
2021-03-23 05:09:17 -04:00
the configured Jaeger URL.
