mw dev eventlogging

You probably want to have the following extensions enabled for eventlogging to function.

wfLoadExtensions( [
  'EventBus',
  'EventStreamConfig',
  'EventLogging',
  'WikimediaEvents'
  ] );

Using this will automatically configure a eventlogging server for MediaWiki.

$wgEventServices = [ '*' => [ 'url' => 'http://eventlogging:8192/v1/events' ] ];
$wgEventServiceDefault = '*';
$wgEventLoggingStreamNames = false;
$wgEventLoggingServiceUri = "http://eventlogging.local.wmftest.net:" . parse_url($wgServer)['port'] . "/v1/events";
$wgEventLoggingQueueLingerSeconds = 1;
$wgEnableEventBus = defined( "MW_PHPUNIT_TEST" ) ? "TYPE_NONE" : "TYPE_ALL";

Viewing logs

Checkout the logs of this service in order to see events coming in.

Documentation

• EventBus extension
• EventStreamConfig extension
• EventLogging extension
• WikimediaEvents extension

Commands

• mw dev eventlogging create — Create the containers
• mw dev eventlogging destroy — Destroy the containers
• mw dev eventlogging exec — Execute a command in the main container
• mw dev eventlogging image — Interact with the image used for the service
• mw dev eventlogging rebuild — Build images and recreate the containers
• mw dev eventlogging start — Start the containers
• mw dev eventlogging stop — Stop the containers

Global options

-c, --context <string>

Development context to use (overrides CONTEXT) Default: default.

--help

Help for this command

--no-interaction

Do not ask any interactive questions

-v, --verbose <count>

Increase output verbosity. Example: --verbose=2 or -vv

See also

• mw dev