Commit 6e7bf037 authored by alinamihaila's avatar alinamihaila

Update feature flag docs for events tracking

parent 1a391b4c
...@@ -133,7 +133,7 @@ Any such changes lead to inconsistent reports from multiple GitLab instances. ...@@ -133,7 +133,7 @@ Any such changes lead to inconsistent reports from multiple GitLab instances.
If there is a problem with an existing metric, it's best to deprecate the existing metric, If there is a problem with an existing metric, it's best to deprecate the existing metric,
and use it, side by side, with the desired new metric. and use it, side by side, with the desired new metric.
Example: Example:
Consider following change. Before GitLab 12.6, the `example_metric` was implemented as: Consider following change. Before GitLab 12.6, the `example_metric` was implemented as:
```ruby ```ruby
...@@ -495,7 +495,7 @@ Implemented using Redis methods [PFADD](https://redis.io/commands/pfadd) and [PF ...@@ -495,7 +495,7 @@ Implemented using Redis methods [PFADD](https://redis.io/commands/pfadd) and [PF
aggregation. aggregation.
- `aggregation`: may be set to a `:daily` or `:weekly` key. Defines how counting data is stored in Redis. - `aggregation`: may be set to a `:daily` or `:weekly` key. Defines how counting data is stored in Redis.
Aggregation on a `daily` basis does not pull more fine grained data. Aggregation on a `daily` basis does not pull more fine grained data.
- `feature_flag`: optional. For details, see our [GitLab internal Feature flags](feature_flags/) documentation. - `feature_flag`: optional. For details, see our [GitLab internal Feature flags](feature_flags/) documentation. The feature flags are owned by the group adding the event tracking.
Use one of the following methods to track events: Use one of the following methods to track events:
......
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