debian-mirror-gitlab/doc/operations/tracing.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

52 lines
2.5 KiB
Markdown
Raw Normal View History

2020-07-28 23:09:34 +05:30
---
stage: Monitor
2022-04-04 11:22:00 +05:30
group: Respond
2021-02-22 17:27:13 +05:30
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-28 23:09:34 +05:30
---
2022-07-16 23:28:13 +05:30
# Tracing (DEPRECATED) **(FREE SELF)**
2020-07-28 23:09:34 +05:30
2021-11-18 22:05:49 +05:30
> - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/42645) from GitLab Ultimate to GitLab Free in 13.5.
2022-03-02 08:16:31 +05:30
> - [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346540) in GitLab 14.7.
2022-07-16 23:28:13 +05:30
> - [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-03-02 08:16:31 +05:30
WARNING:
This feature is in its end-of-life process. It is [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/346540)
2022-07-16 23:28:13 +05:30
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-28 23:09:34 +05:30
2021-04-29 21:17:54 +05:30
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-28 23:09:34 +05:30
2021-04-29 21:17:54 +05:30
## Install Jaeger
2020-07-28 23:09:34 +05:30
2021-04-29 21:17:54 +05:30
[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-28 23:09:34 +05:30
2021-04-29 21:17:54 +05:30
See also:
2020-07-28 23:09:34 +05:30
2021-04-29 21:17:54 +05:30
- 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-28 23:09:34 +05:30
2021-04-29 21:17:54 +05:30
## Link to Jaeger
2020-07-28 23:09:34 +05:30
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-09-04 01:27:46 +05:30
1. Navigate to your project's **Settings > Monitor** and provide the Jaeger URL.
2020-07-28 23:09:34 +05:30
1. Click **Save changes** for the changes to take effect.
2021-09-04 01:27:46 +05:30
1. You can now visit **Monitor > Tracing** in your project's sidebar and GitLab redirects you to
2021-04-29 21:17:54 +05:30
the configured Jaeger URL.