E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (16)
View Page History
...
{section} h1. Petals Logging specificities
h2. Level 'MONIT'
...* FINEST (lowest value)
Moreover standard information of each log level, a MONIT level trace is accompanied by following information:
In addition to standard log information (see below), the LOG MESSAGE of a MONIT level trace gives the following informations:
* a trace code identifying the nature of the MONIT trace. See below the list of trace code.
* a flow instance identifier identifying the flow instance,
* a flow step identifier identifying the consume or the provide invoked.
* a flow instance identifier identifying the flow instance,
* a flow step identifier identifying the consume or the provide invoked.
* informations specific information to the trace code.
|| Trace code \\ || Description || Specific information \\ ||
...h2. Petals formatters
PetalsFormatter uses the following pattern:
{panel:borderStyle=solid}{+}Petals Node Name+ +YYYY/MM/DD+ +HH:MM:SS,FFF+ +LOG LEVEL+ +LOGGER NAME+ : ?\[LOG MESSAGE\]
{panel:borderStyle=solid}{+}Petals Node Name+ +YYYY/MM/DD+ +HH:MM:SS,FFF+ +LOG LEVEL+ +LOGGER NAME+ : ?\[LOG MESSAGE\]
...Petals ESB allow to split its log records into a log files hierarchy. This is done thanks to the PetalsFileHandler which can redirect log records to separate according to Petals ESB runtime properties.
In addition to standard Handler properties (level, formatter, etc..), PetalsFileHandler can be configured through the following extra properties :
* basedir : base directory where log files will be stored. Default value (if no property set) is user home directory.
In the base directory, you find petals.log file where petals container logs are recorded and a sub-directory flow-monitoring containing flowInstanceId sub-directories.
In this base directory, you'll find two things:
* a *petals.log* file which contains all petals container logs
* a *flow-monitoring* sub-directory which contains flowInstanceId sub-directories (one per flow instanciation).
* a *petals.log* file which contains all petals container logs
* a *flow-monitoring* sub-directory which contains flowInstanceId sub-directories (one per flow instanciation).
h2. Logged informations
...* Log message
We can found more informations about previous concepts in glossary [Glossary|http://doc.petalslink.com/display/glossary/Petals+ESB+specific+vocabulary]
...{warning}
h1. Appendix
...{noformat}
[^loggers.properties]
h3. Default log4j.properties
...log4j.additivity.org.ow2.petals.registry=true{noformat}
[^log4j.properties]
{column}
{column}