| Lea_WMDE | |
| Dec 4 2017, 5:16 PM |
| F12678932: image.png | |
| Jan 20 2018, 11:13 AM |
Motivation
TwoColConflict allows you to set a base version for conflict resolution, either yours or the conflicting version. We would like to find out what people usually pick to better understand the mental model behind
Task
To the grafana board, add three number boxes
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Track which base is selected | mediawiki/extensions/TwoColConflict | master | +2 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T72163 Edit conflicts (tracking) | |||
| Resolved | None | T139601 Better solutions to edit conflicts (#1) | |||
| Resolved | Lea_WMDE | T183223 Analytics: Grafana board with insights into edit conflicts | |||
| Declined | None | T181058 Investigate when edit conflicts happen | |||
| Resolved | GoranSMilovanovic | T182009 Find out which version is used more |
Change 395722 had a related patch set uploaded (by Addshore; owner: Addshore):
[mediawiki/extensions/TwoColConflict@master] Track which base is selected
Patch will create the data, grafana board will still need an update after deployment.
Change 395722 merged by jenkins-bot:
[mediawiki/extensions/TwoColConflict@master] Track which base is selected
Data will be available in graphite under the metric names:
@Addshore The last row on the TwoColConflict dashboard has new singlestats to encompass these two indicators.
However, the queries:
summarize(MediaWiki.TwoColConflict.event.baseSelection.your, '1d', 'sum', false)
and
summarize(MediaWiki.TwoColConflict.event.baseSelection.current, '1d', 'sum', false)
both return N/A.
@Addshore Following what you did with the singlestats in the top rows of the dashboard, I've tried with:
MediaWiki.TwoColConflict.event.baseSelection.your
and
MediaWiki.TwoColConflict.event.baseSelection.current
only as queries for the new singlestats for this task. No change: both result in N/A values being shown.
@GoranSMilovanovic using the metric name suggestion (rather than entering a plain string) can help you here.
The metric come through statsd and have a collection of suffixes.
*.sum is what you want.
This is the sum of the counters in the given bucket in statsd.