@MNeisler, @nettrom_WMF, @cchen, and @Ottomata confirmed that increasing the sampling rate of the EditAttemptStep instrument (EAS) to 100% shouldn't be a problem.
However, we can't just add
$wgDTSchemaEditAttemptStepSamplingRate = $wgWMESchemaEditAttemptStepSamplingRate = 1; // 100%
to LocalSettings.php because the VisualEditorFeatureUse instrument (VEFU) also uses those variables. In order to be able to vary the sampling rates for EAS and VEFU independently, we'll have to:
- Add new sample rate variables to VEFU
- Set EAS sample rate variables to 100%
- Remove $wgDTSchemaEditAttemptStepOversample (which is always true in production) and $wgDTSchemaEditAttemptSamplingRate (which is always 0 in production)
- This is optional but would simplify the answer to the question "How is VEFU sampled?"
We should keep $wgWMESchemaEditAttemptStepSamplingRate (set to 1 in step 2 above) as it can be used as an on/off switch for EAS. It can be removed after EAS is migrated to Metrics Platform.