PB Web Media Audit Bundle for Symfony

Installs: 5 832

Dependents: 0

Suggesters: 0

Security: 0

Stars: 2

Watchers: 3

Forks: 0

Open Issues: 0


1.2.3 2019-10-28 14:26 UTC

This package is auto-updated.

Last update: 2020-10-03 07:31:15 UTC


Provides an easily extendible Symfony Bundle to create an audit log.


Install the audit-bundle using composer:

composer require pbweb/audit-bundle

then, add the bundle to your AppKernel:

class AppKernel extends Kernel
    public function registerBundles()
        $bundles = array(
            // ...
            new Pbweb\AuditBundle\PbwebAuditBundle(),


To insert an entry in the audit logger, create an AuditEvent and give it to the AuditLog

$event = new \Pbweb\AuditBundle\Event\AuditEvent('test');
$log = $container->get('pbweb_audit.audit_log');

You can also create your own events (which we recommend), as long as they implement the AuditEventInterface.


Events enter the audit logger which will then trigger the following events (in order) with the provided AuditEventInterface event as an argument:

  1. pbweb_audit.append_event
  2. The return value of $event->getName()
  3. pbweb_audit.log_event

That way you can hook into generic flow moments or only respond to specific events.

The Audit Bundle uses the Symfony event system so all the normal shenanigans (like listener priorities, stopping propagation, etc) work when handling these events.

Event Appenders

Events aren't usually complete by themselves, you probably want to append some data related to the event like the user that triggered it or the ip of the client.

To do this listen to the pbweb_audit.append_event event (either through a listener or subscriber). It will receive all AuditEventInterface events that go into the audit log.

Default event appenders

The Audit Bundle comes packaged with a few event appenders that will be loaded by default, see the configuration section below on how to disable that.

If you use these appenders, you need to add symfony/security to your project.


Eventually the audit log entries need to go somewhere, either the database, a PSR logger or whatever you can think of.

The Audit Bundle comes packaged with a PSR logger and Doctrine logger (see below).

You can also implement your own logger by listening to the pbweb_audit.log_event event. It will receive all AuditEventInterface events that go into the audit log.

PSR Logger

By default the Audit Bundle loads the PsrLogger, which will use the @logger service to log events to your default log. Look at the configuration section below on how to disable this behaviour.

Doctrine Logger

For small(ish) audit logs you could use the database as a data store. The Audit Bundle comes with an AbstractDoctrineLogger. The only thing you need to do is create a service that implements the convertToEntity method and give it the tag kernel.event_subscriber.


You can optionally configure the audit bundle in your app/config.yml file

    load_default_event_loggers: true    # loads the loggers defined in Pbweb/AuditBundle/Resources/config/default/loggers.yml
    load_default_event_appenders: true  # loads the event appenders in Pbweb/AuditBundle/Resources/config/default/appenders.yml 


© PB Web Media