Commit 6c797123 authored by Mike Jang's avatar Mike Jang

Merge branch...

Merge branch '287785-adjust-docs-for-using-feature-flags-for-tracking-using-redis-hll' into 'master'

Adjust docs for using feature flags for tracking using Redis HLL

See merge request gitlab-org/gitlab!48457
parents 2aca100b 48cfb186
...@@ -467,13 +467,17 @@ Next, get the unique events for the current week. ...@@ -467,13 +467,17 @@ Next, get the unique events for the current week.
start_date: Date.current.beginning_of_week, end_date: Date.current.end_of_week) start_date: Date.current.beginning_of_week, end_date: Date.current.end_of_week)
``` ```
Recommendations: ##### Recommendations
- Key should expire in 29 days for daily and 42 days for weekly. We have the following recommendations for [Adding new events](#adding-new-events):
- If possible, data granularity should be a week. For example a key could be composed from the
metric's name and week of the year, `2020-33-{metric_name}`. - Event aggregation: weekly.
- Use a [feature flag](../../operations/feature_flags.md) to have a control over the impact when - Key expiry time:
adding new metrics. - Daily: 29 days.
- Weekly: 42 days.
- When adding new metrics, use a [feature flag](../../operations/feature_flags.md) to control the impact.
- For feature flags triggered by another service, set `default_enabled: false`,
- Events can be triggered using the `UsageData` API, which helps when there are > 10 events per change
##### Enable/Disable Redis HLL tracking ##### Enable/Disable Redis HLL 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