Commit a9afc17e authored by Russell Dickenson's avatar Russell Dickenson

Merge branch 'jeromezng-master-patch-35046' into 'master'

Move docs from event tracking to telemetry

See merge request gitlab-org/gitlab!26746
parents 86b70ec8 e6e55c81
...@@ -181,11 +181,11 @@ Complementary reads: ...@@ -181,11 +181,11 @@ Complementary reads:
- [Externalization](i18n/externalization.md) - [Externalization](i18n/externalization.md)
- [Translation](i18n/translation.md) - [Translation](i18n/translation.md)
## Event tracking guides ## Telemetry guides
- [Introduction](event_tracking/index.md) - [Introduction](../telemetry/index.md)
- [Frontend tracking guide](event_tracking/frontend.md) - [Frontend tracking guide](../telemetry/frontend.md)
- [Backend tracking guide](event_tracking/backend.md) - [Backend tracking guide](../telemetry/backend.md)
## Experiment Guide ## Experiment Guide
......
...@@ -55,7 +55,7 @@ The author then adds a comment to this piece of code and adds a link to the issu ...@@ -55,7 +55,7 @@ The author then adds a comment to this piece of code and adds a link to the issu
end end
``` ```
- Track necessary events. See the [event tracking guide](../event_tracking/index.md) for details. - Track necessary events. See the [telemetry guide](../../telemetry/index.md) for details.
- After the merge request is merged, use [`chatops`](../../ci/chatops/README.md) to enable the feature flag and start the experiment. For visibility, please run the command in the `#s_growth` channel: - After the merge request is merged, use [`chatops`](../../ci/chatops/README.md) to enable the feature flag and start the experiment. For visibility, please run the command in the `#s_growth` channel:
``` ```
......
--- ---
redirect_to: '../event_tracking/index.md' redirect_to: '../../telemetry/index.md'
--- ---
This document was moved to [another location](../event_tracking/frontend.md). This document was moved to [another location](../../telemetry/index.md).
...@@ -5,7 +5,7 @@ blocks of Ruby code. Method instrumentation is the primary form of ...@@ -5,7 +5,7 @@ blocks of Ruby code. Method instrumentation is the primary form of
instrumentation with block-based instrumentation only being used when we want to instrumentation with block-based instrumentation only being used when we want to
drill down to specific regions of code within a method. drill down to specific regions of code within a method.
Please refer to [Event tracking](event_tracking/index.md) if you are tracking product usage patterns. Please refer to [Telemetry](../telemetry/index.md) if you are tracking product usage patterns.
## Instrumenting Methods ## Instrumenting Methods
......
...@@ -44,7 +44,7 @@ From the backend, the events that are tracked will likely consist of things like ...@@ -44,7 +44,7 @@ From the backend, the events that are tracked will likely consist of things like
See [Backend tracking guide](backend.md). See [Backend tracking guide](backend.md).
Also, see [Instrumenting Ruby code](../instrumentation.md) if you are instrumenting application performance metrics for Ruby code. Also, see [Instrumenting Ruby code](../development/instrumentation.md) if you are instrumenting application performance metrics for Ruby code.
## Enabling tracking ## Enabling tracking
......
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