Last update on: 2014-09-monthly
- We have enabled SSL by default for all users.
- We have added timeseries support and are busy implementing it for all metrics
- Metrics can now have timestamp as start / end point instead of a date
- We implemented the survival metric
The Threshold metric was implemented, and numerous bugs were fixed.
We concluded Phase 1 of Wikimetrics, by implementing asynchronous cohort validation, editor survivor and threshold metrics.
The team added a small but important feature to Wikimetrics in December: the ability to authenticate against MediaWiki OAuth. This allows users to sign up for Wikimetrics without relying on a third party for authentication and is an early adoption of MediaWiki OAuth.
We are adding features to Wikimetrics to support scheduled jobs and data access via evergreen URLs. This will support dashboarding and other services that are will be built on top of the service. In addition, we are preparing a Wikimetrics-Vagrant image to help getting started with Wikimetrics development.
Work progresses on enhancing Wikimetrics into a more flexible general tool. This month we completed work on a Vagrant deployment environment which will make it easier for the community to work on Wikimetrics. We've also made progress on the scheduler, reporting enhancements and a deployment issue.
We did some significant architectural work on WikiMetrics this month to prepare it for its role as our recurrent report scheduling and generation system. The first use case for this system will be the Editor Engagement Vital Signs project, which will provide daily updates on key metrics around participation.
New features have been deployed on Wikimetrics: Scheduled Reports & Public Reports.
The focus for this month was on extending Wikimetrics to support the Editor Engagement Vital Signs (EEVS) project. The team also fixed several bugs around Unicode support (particularly non-Latin character sets) and implemented delete cohort functionality.
To support Editor Engagement Vital Signs, the team has implemented a new metric: Newly Registered User. There is also a new backup system to preserve user's reports on cohorts as well as the ability to tag cohorts. A number of bugs have been fixed, including fixing the first run of a recurrent report and preventing the creation of reports with invalid cohorts.
Wikimetrics can now generate vital sign metrics for every project daily. Rolling Monthly Active Editor metric has been implemented; the reports are in JSON format, in a logical path hosted on a file server and downloadable. The team also worked on backfilling data for the daily reports on Newly Registered and Rolling Active Editor, and numerous optimizations to backfill the data quickly.
Following the prototype built for Wikimania, the team identified many performance issues in Wikimetrics for backfilling Editor Engagement Vital Signs (EEVS) data. The team spent a sprint implementing some performance enhancements as well as properly managing sessions with the databases. Wikimetrics is better at running recurring reports concurrently and managing replication lag in the slave DBs.
Work was done on the following metrics:
- Rolling New Active Editor - Implemented
- Rolling Surviving New Active Editor - Implemented
- Pages Created and Edits - Updated to include reporting configuration to include changes to deleted pages (this is a default).
- Metrics with ‘Namespaces’ as a parameter let you specify “All Namespaces.” Leave the input field blank to do so.
- Rolling recurring old active editor is implemented, but does not perform sufficiently rapidly for us to enable it on the production servers.
- The status of the implementation of Standardized Metrics defined by the Research Team is here: https://meta.wikimedia.org/wiki/Research:Metrics_standardization/Implementation