**==== Background**
Existing metrics are supposed to include usage of the 2010 vs 2017 editorsuse the legacy EventLogging system. The existingThere was a [[ https://grafana-rw.wikimedia.org/d/uXX3yj1Mz/codemirror?forceLogin&orgId=1 | Grafana dashboard ]] no longer functionsbut it is now marked for cleanup. This task is about instrumentation for CodeMirror 6, starting from a clean slate. This data will help us evaluate which features are the most popular, and influence what is decided as the default set of features in the longer-term goal of having CodeMirror on by default for interest projects (i.e. This task is about reviving it along with any additional metrics we want for CodeMirror 6T288161).
**Acceptance criteria**As part of this task, we should retire the existing legacy instrumentation.
* Revive all existing panels at https://grafana-rw.wikimedia.org/d/uXX3yj1Mz/codemirror==== Data questions
New things we want to track:
* Use of* How many people are using CodeMirror without the 2017 or 2010 editors (i.e. `wikitext-2003`).rror?
* Following {T359498}* Which editors are being used with CodeMirror (2017 editor, WikiEditor, we'll want to track usage of each individual feature.or standalone CodeMirror)?
** Template folding* Which [[ https://www.mediawiki.org/wiki/Help:Extension:CodeMirror#Features | CodeMirror features ]] are being used?
** Bracket matching
** Template folding
** Autocompletion
** Line numbering
** Highlighting the active line
** Highlight special characters** Line wrapping
** …and eventually other features as they are added, like autocompletion
This data will help us evaluate which features are the most popular, and influence what is decided as the default set of features in the longer-term goal of having CodeMirror on by default for interest projects (i.e.Highlighting special characters
** Bidi isolation
* What is the relationship of editor experience and the various features? T288161).(edit count bucketing)