AFAIKS, the only schema in the log database (m2, mariaDB, see https://meta.wikimedia.org/wiki/Research:Schemas) that has anything to do with edit conflicts is https://meta.wikimedia.org/wiki/Schema:EditConflict. This table is not fully developed (there are currently two versions on log: EditConflict_8860941 and EditConflict_8860941_15423246) and not yet fully documented.
I was not able to find anything that tracks the usage of TwoColConflict, except for I know that there must be something since we have this on Graphana: https://grafana.wikimedia.org/dashboard/db/mediawiki-twocolconflict?orgId=1
So for this we will add some tracking within the code of the TwoColConflict extension itself. This code will send data to statsd, which will then end up in the graphite instance. This will allow us to track events from the code.
Numbers like the beta feature users are already tracked in graphite and can be seen on a dashboard such as https://grafana.wikimedia.org/dashboard/db/betafeatures but this can be added to the two col conflict dashboard.
Those numbers are generated from the https://phabricator.wikimedia.org/diffusion/ADES/browse/master/src/betafeatures/counts.php script.
@Addshore Ok. I understand the route now. I have never worked with Graphite and Grafana before, but from what I've seen in their documentation - at least Grafana seems easy to do. Your call: let me know how can I help you with this and what do you think I should do to get ready if you need my help.
So, looking at this again.
loads is essentially already tracked, as the number of conflicts is tracked.
errors doesn't really apply to the twocolconflict extension, for revslider this relates to the api queries that the code makes failing causing the slider to fail. TwoColConflict doesn't make any similar api calls / have a way to fail like this.
So code changes are not needed and the panels for BF things just need to be pulled over from the revslider dashboard.
As of the errors: as @Addshore has already noted above: "errors doesn't really apply to the twocolconflict extension, for revslider this relates to the api queries that the code makes failing causing the slider to fail. TwoColConflict doesn't make any similar api calls / have a way to fail like this."
Please re-open in case any additional work needs to be done here.
@GoranSMilovanovic cool, looks great! Could you still add a short description to each panel similar to what has been done for https://grafana.wikimedia.org/dashboard/db/mediawiki-revisionslider?refresh=1m&orgId=1.
- for the total number of BF users, comment on revisionslider is: "For wikis that have the feature enabled by default, those users will not be counted here. The number of users that were using the feature as a BetaFeature before it was enabled by default will still be counted." - Q: does this apply to TwoColConflict counts too?
Descriptions are added.