Configuring Business Log Levels

You monitor and analyze business events of BPM (Business Process Management) using the business log. BPM raises events to signal changes in the lifecycle of its entities such as business processes. You can configure a log level for the business log to be able to control the amount of data written to the business log. Every log entry that should be written in the database is checked against this log level and after that is either stored or ignored.

You can use lower log level if, for example, you expect high load scenarios and you want to improve performance and minimize database growth. Higher log levels are to be used when rich analyzing capabilities are needed.

The business log level you configure applies to all processes deployed on the particular application server.

You can configure one of the following business log levels:

• None

  It stores no business log entries, except for changes of business log level.

• Failure

  It stores only error and failure business log events.

• Standard

  This is the default log level, which stores enough information to reproduce the process flow but still reduces the amount of data stored significantly. At least this level is required to fully support all datasources needed for reporting activities.

• Detailed

  It stores everything except high-volume events, such as update of data objects, for example.

• Full

  It stores all business log entries.

Every log level includes the amount of log entries that are stored by the previous lower log level.