Commit 43e72d41 authored by Craig Norris's avatar Craig Norris Committed by Achilleas Pipinellis

Remove outdated version reference

parent e381df33
...@@ -2,13 +2,12 @@ ...@@ -2,13 +2,12 @@
stage: Enablement stage: Enablement
group: Distribution group: Distribution
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 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
type: reference
--- ---
# Finding relevant log entries with a correlation ID **(FREE SELF)** # Finding relevant log entries with a correlation ID **(FREE SELF)**
In GitLab 11.6 and later, a unique request tracking ID, known as the "correlation ID" has been GitLab instances log a unique request tracking ID (known as the
logged by the GitLab instance for most requests. Each individual request to GitLab gets "correlation ID") for most requests. Each individual request to GitLab gets
its own correlation ID, which then gets logged in each GitLab component's logs for that its own correlation ID, which then gets logged in each GitLab component's logs for that
request. This makes it easier to trace behavior in a request. This makes it easier to trace behavior in a
distributed system. Without this ID it can be difficult or distributed system. Without this ID it can be difficult or
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment