Log Configurations
Each processing unit references a log configuration. The log configurations are defined in the Collections tab.
You can also 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 Files Section in CDD Collections Tab Log Configurations Settings.
- 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 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.
module1:level module2:level ...
*:info
This syntax means that logging for all modules is at the info logging level.
*:info driver.tibrv:debug
This syntax means that all modules use logging level info, except the module driver.tibrv which uses debug level.