Extension:EventLogging/Programming


 * See ../Guide for a comprehensive introduction to EventLogging, developing and deploying EventLogging schemas, and more.

How it works
When code logs an event, it must reference a schema. Here's some actual working JavaScript: In this case the schema is "GettingStarted". Schema: page on Meta. The name should use InitialCaps.


 * 1) The schema is a JSON structure that specifies the fields in the event &mdash; their names, their types (integer, string, boolean, etc.), whether required or not, allowed values, ... It is stored in the Schema: namespace of some wiki running the extension.
 * 2) PHP code in core or an extension explicitly depends on a particular revision of a particular data model, and retrieves it from the schema host (configured as $wgEventLoggingSchemaIndexUri).
 * 3) * For client-side event logging the MediaWiki ResourceLoader gets a particular revision of a schema from meta-wiki's Schema: namespace (e.g. http://meta.wikimedia.org/wiki/Schema:GettingStarted revision 4867730), caches it, and makes it available to client JavaScript such as the call to  above.
 * 4) * For server-side event logging, PHP code simply calls

How to make a data model
Then:
 * Meet a researcher and determine what you're going to log, name the fields to log, reusing well-known field names.
 * Create a JSON structure representing this data model in the Schema: namespace on meta, tweak it until it saves without errors.
 * Sample: m:Schema:OpenTask
 * Tip: http://jsonlint.com/ has better error reporting, copy and paste your JSON into it.
 * Tip: if you have a JSON file with desired fields and values, http://www.jsonschema.net/ will guess at a schema for it (but with extra info like "id" that we don't currently use) that you can start with.
 * Use the schema's talk page (sample) to link to experiments using this, discuss details, etc.
 * Always document what code in what circumstances logs the event
 * Developers write code to log events that match the data model.
 * The data model tells analysts what information is in the logs.

Versioning
If code tries to log an event that doesn't match the data model that EventLogging retrieved, EventLogging will log the event anyway but flag it as invalid. Since you always give a schema revision, you can edit the schema as much as you want without affecting existing code.

It's OK to have different kinds of events (often called actions) sharing one data model. That way the events go into one table and it may simplify querying and multi-dimensional analysis. Only add  to the fields that are applicable to all events.

Data fields

 * ''moved to ../Guide

Available data models
See m:Category:Schemas (active).

JSON schema validation
Each data model JSON file on meta-wiki is a JSON schema. This is an evolving standard to specify the format of JSON structures, in our case the logged event.
 * the JSON schema draft].
 * As of December 2012 EventLogging only validates that the schemas on meta are valid JSON.
 * When code attempts to log an event, EventLogging only pays attention to a subset of JSON schema features; as of November 2012 this includes:
 * type: boolean, integer, number, string, timestamp
 * required: true/false
 * enum values

Good starting code

 * The WikimediaEvents extension has working code to log server-side events in PHP in.
 * The GettingStarted extension has setup code to declare and require the "openTasks" schema resource and log to it in JavaScript, but it's gotten more elaborate in 2013.

Client-side logging

 * require your schema wherever you need to log events (it will pull in ext.eventLogging which implements the mw.eventLog module).
 * See for API documentation.

Tips

 * In JavaScript code, use  to set common values for fields to log that don't change, such as version, the user's name, etc.
 * ../Guide lists common field names already used in schemas and the JavaScript that fills them. Don't reinvent the wheel.

Debugging
If code attempts to log an invalid event, EventLogging detects it's invalid and flags it, but logs it anyway. Turn on ResourceLoader debug mode to see warnings in your browser's JavaScript console about invalid events. The most likely cause of an invalid events is your page doesn't load the right schema. In your browser's JavaScript console, enter mw.eventLog.schemas to see which schemas have been loaded on the current page.

Monitoring events

 * Client-side event logging works by requesting a beacon image event.gif with the log info in its query string. To see the log events you can
 * watch for this request in your browser's network console,
 * look for it in your web server's access logs,
 * run the toy web server server/bin/eventlogging-devserver in the EventLogging extension which pretty-prints the query string,
 * To monitor events after processing, you can append an  callback after a   call, for example the following temporary debugging code

Logging clicks on links
Often you want to log clicks on links. If these take the user away from the current page, there's a chance that the browser will move to the new page before the request for the beacon image makes it onto the network, and the browser will drop the request. The E3 team experimented with using deferred promises to deal with this, but that introduced known and unknown unknowns. is related to this issue.

One possible solution is implemented by the GettingStartedExtension to. In summary you add an  'click' handler to the link, and in it EventLogging itself may implement a helper function for this.
 * call  but with a timeout
 * in a jQuery  callback handler, set   to the target (href) of the link. If and when this executes it will immediately load the new page.
 * call  to prevent the default handling of the click (which would be to go to the new page).

Note in general that a click handler does not fire if the user middle-clicks to open in a new tab or chooses to visit the link from a context menu.