Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 29 Agent and Processing Unit Configuration : Understanding and Configuring Log Configurations

Understanding and Configuring Log Configurations
Each processing unit references a log configuration. The log configurations are defined in the Collections tab. See Configuring Collections of Rules, Rule Functions, and Destinations for related procedures. This section explains more about log configurations and how to configure them.
You can also replace the default line layout implementation with your own.
Log File Settings
For a reference to the settings, see the Files Section in Table 54, CDD Collections Tab Log Configurations Settings (Sheet 1 of 3).
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.
Understanding 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:
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.
Configuring Log Configurations
See Understanding and Configuring Log Configurations for an explanation of the logging levels, modules, and syntax details
To Add a Log Configuration
1.
2.
3.
4.
5.
To Specify a Custom Line Layout Class
1.
2.
3.
4.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved