E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (5)
View Page History
...
{section} When you activate the log handler {{PetalsExchangeDumperFileHandler}}, any log message is saved as following:
* the log trace is logged in the log file identified by the following pattern: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/petals.log}}
* the log trace is logged in the log file identified by the following pattern: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/petals.log}}
* for log trace with level MONIT:
** the content of the message exchange dumped in a file identified as following: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/<flow step id>_<trace code>.xml}}
** the content of the message exchange dumped in a file identified as following: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/<flow step id>_<trace code>.xml}}
* for log trace with level MONIT, the content of the message exchange is dumped in a file identified as following: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/<flow step id>_<trace code>.xml}}
** the exchange content logged is composed of:
*** message exchange identifier,
*** message exchange identifier,
...*** name of operation invoked,
*** message exchange properties,
*** message exchange properties,
*** normalized messages "IN", "OUT" or "Fault" of the message exchange, with for each normalized message:
**** normalized message properties,
**** normalized message content, the XML payload,
**** normalized message content, the XML payload,
...***** attachment size if available,
***** attachment content, that will be available in a next version,
***** attachment content, that will be available in a next version,
*** fault of the message exchange if exist. Dumped as a normalized message,
*** error if exists. Dumped as an error stack trace.