This documentation is for a version that is out of support.

You may want to view the same page for the latest version, or for any of the versions available in the drop-down menu in the top-right corner.

Work execution audit

Sometimes it is useful to understand what is currently happening in the platform, in particular for work execution, see Work service mechanism.

This can be achieved using a specific logger called Work execution audit

What can be tracked

Abnormal work execution

The logger produce a Warning each time a work takes too much time to be executed or it was rescheduled too much times.

For theses cases, it also produces an Info log when the work was finally executed.

A reschedule happens when a work can’t be executed right now because some other work already locked the same process instance.

Activate and configure the work execution audit

The audit is activated by default, it can be deactivated or reactivated here:

In bonita-tenant-community-custom.properties set flag bonita.tenant.work.audit.activated to true or false

Some properties can be configured, these can be found in the default configuration file bonita-tenant-community.properties under the Work execution audit section

There is a dedicated logger called BONITA_WORK_AUDIT.EXECUTION, its level can be changed to DEBUG for more information, in file logging.properties.