Added instructions on enabling user counts to error tracking
What does this MR do and why?
Related issue: gitlab-org/opstrace/opstrace#2345 (comment 1860314084)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Merge request reports
Activity
requested review from @phillipwells
assigned to @sguyon
mentioned in issue gitlab-org/opstrace/opstrace#2345 (closed)
changed milestone to %17.0
added sectionanalytics label
1 Warning 
7714c29f: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines. 1 Message 
This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/operations/error_tracking.md(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.mdfiles that you've changed. The first few lines of each*.mdfile identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-reviewjob that generated this comment.Generated by
Edited by Ghost User-
added docs-only label
- Resolved by Phillip Wells
@sguyon A few suggestions from me
- Last reply by Phillip Wells
removed review request for @phillipwells
changed milestone to %16.11
