diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-02 12:07:59 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-02 12:07:59 +0300 |
| commit | a325f3a104748ecc68df7c3d793940aa709a111f (patch) | |
| tree | b3bce12be64ab2d9e31627dacd059165819797a3 /doc/development/event_tracking | |
| parent | 8fb943c7df5f2b399caaeaebd6c00d0630bc763c (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/event_tracking')
| -rw-r--r-- | doc/development/event_tracking/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/event_tracking/index.md b/doc/development/event_tracking/index.md index 10e99e845d6..8c00930a781 100644 --- a/doc/development/event_tracking/index.md +++ b/doc/development/event_tracking/index.md @@ -13,7 +13,7 @@ As developers, we should attempt to add tracking and instrumentation where possi - Usage patterns. - Other metrics that can potentially be improved on. -To maintain consistency, and not adversely effect performance, we have some basic tracking functionality exposed at both the frontend and backend layers that can be utilized while building new features or updating existing features. +To maintain consistency and not adversely effect performance, we have some basic tracking functionality exposed at both the frontend and backend layers that can be utilized while building new features or updating existing features. We also encourage users to enable tracking, and we embrace full transparency with our tracking approach so it can be easily understood and trusted. By enabling tracking, users can: |