Log Configurations

Each processing unit references a log configuration. The log configurations are defined on the Collections tab.

You can replace the default line layout implementation with your own. You can also override the default logging mechanism in TIBCO BusinessEvents to use the log4j mode. See Overriding the Default Logging Mode for more details. For some custom log4j configuration examples, see Custom Log4j Configuration Examples.

For more information about log4j, see Apache wiki page.

Log File Settings

For a reference to the settings, see the CDD Collections Tab Log Configurations Settings Reference in CDD Collections Tab Log Configurations Settings Reference.

  • Log File Name and Location

    Set the name and location of the log file for a log configuration using the Name and Directory settings. If you do not enter a leading slash, the files are stored relative to the working directory (the directory in which you start the be-engine.exe executable). If you do not specify a name, the engine name is used. If no engine name is specified the name defaults to <hostname>.log or cep-engine.log.

  • Number and Size of Log files

    You can also set the size of a single log file, the number of files to keep, and whether a log file is flushed when an engine starts, or whether entries are appended. Log Configuration Levels and Syntax

Log Configuration Levels and Syntax
In a log configuration that uses the provided line layout implementation, you select a level of logging for each module in the TIBCO BusinessEvents runtime.
Levels
A level corresponds to how much logging is filtered out. They are ordered where all is lowest and off is highest:
Level Description
Off Highest possible rank. Filters out all logging messages (turns logging off for the specified module).
Fatal Logs only severe runtime errors that cause the application to stop running.
Error Also logs runtime errors that might not cause the application to stop running.
Warn Also logs potentially harmful runtime events or situations.
Info Also logs runtime informational events of general interest.
Debug Also logs detailed runtime informational events, for use in identifying issues.
Trace Also logs even more detailed runtime information.
All Lowest possible rank. Turns on all logging including any custom logging levels.
Syntax
Enabling a lower level automatically enables the higher levels. For example, enabling info automatically enables fatal, error, and warning.

Assign each module to a level using a space-delimited list. The levels are not case sensitive. The syntax is as follows: 

module1:level module2:level ...

To assign a certain level of logging to all modules, use an asterisk: 

*:info

This syntax means that logging for all modules is at the info logging level.

You can use the asterisk syntax and also specify exceptions that use a different logging level. For example: 

*:info  driver.tibrv:debug

This syntax means that all modules use logging level info, except the module driver.tibrv which uses debug level.

The Apache Ignite log also follows the CDD log configurations. To use a different logging level than the one configured in the CDD for Apache Ignite logs, set the module org.apache.ignite to the desired logging level. for example:

*:info org.apache.ignite:debug

This syntax means that all modules use logging level info, whereas Apache Ignite uses logging level debug.