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} Definitions of traceCode:
*consumeFlowStepBegin*: détermine la réception d'une requête extérieur sur un consume.
* *consumeFlowStepBegin*: record the fact that an external event is received by a consumer. Such a record can only occur on the consume side of binding-components,
* *consumeFlowStepEnd*: record the succeeded end of the external event processing,
* *consumeFlowStepFailure*: record the failure of the external event processing,
* *provideFlowStepBegin*: record of the fact that a provide service receives a call/request from a service consumer. Such a record occurs on service-engine or on the provider side of binding-components,
* *provideFlowStepEnd*: record of the fact that a service provider sends its answer or acknowledgment,
* *provideFlowStepExtBegin*: record of the fact that a service provider calls another service (external call). Such a record can only occur on the provider side of binding-components,
* *provideFlowStepExtEnd*: record of the fact that a service provider receives the answer or acknowledgement to its external call,
* *consumeFlowStepExtFailure*: record that a service provider receives an error from its external call,
* *provideFlowStepFailure*: record the failure of the service provider processing.
* *consumeFlowStepEnd*: record the succeeded end of the external event processing,
* *consumeFlowStepFailure*: record the failure of the external event processing,
* *provideFlowStepBegin*: record of the fact that a provide service receives a call/request from a service consumer. Such a record occurs on service-engine or on the provider side of binding-components,
* *provideFlowStepEnd*: record of the fact that a service provider sends its answer or acknowledgment,
* *provideFlowStepExtBegin*: record of the fact that a service provider calls another service (external call). Such a record can only occur on the provider side of binding-components,
* *provideFlowStepExtEnd*: record of the fact that a service provider receives the answer or acknowledgement to its external call,
* *consumeFlowStepExtFailure*: record that a service provider receives an error from its external call,
* *provideFlowStepFailure*: record the failure of the service provider processing.
*consumeFlowStepEnd*: end message sent to consumer (out message, or Acknowledgement - ACK-).
*consumeFlowStepFailure*: defines if a problem occured during step execution (a fault or a technical error).
*provideFlowStepBegin*: record of the fact that a provide service receives a call/request from a consume.
*provideFlowStepEnd*: record of the fact that provide service send the answer (out message or request ACK).
*provideFlowStepExtBegin*: record of the fact that provide service calls another service (external call).
*provideFlowStepExtEnd*: record of the fact that a provide service receives the answer to its external call (FIXME soit la réponse réelle, soit l'accusé réception s'il est possible envoyé par le service extérieur, sinon elle ne sera pas présente) .
*provideFlowStepFailure*: defines if a problem occured during step execution (a fault or a technical error).
*consumeFlowStepFailure*: defines if a problem occured during step execution (a fault or a technical error).
*provideFlowStepBegin*: record of the fact that a provide service receives a call/request from a consume.
*provideFlowStepEnd*: record of the fact that provide service send the answer (out message or request ACK).
*provideFlowStepExtBegin*: record of the fact that provide service calls another service (external call).
*provideFlowStepExtEnd*: record of the fact that a provide service receives the answer to its external call (FIXME soit la réponse réelle, soit l'accusé réception s'il est possible envoyé par le service extérieur, sinon elle ne sera pas présente) .
*provideFlowStepFailure*: defines if a problem occured during step execution (a fault or a technical error).
h1. Dumping content of message payload
When you activate the log handler {{PetalsPayloadDumperFileHandler}}, the logger saves the messages running through the bus, in corresponding flowInstanceId folder. Each message is named according to the following model: {{flowStepId_traceCode.xml}}.
Once the dump is done, a MONIT level log trace is recorded in the {{flow.log}} file, with the following informations: traceCode, flowInstanceId and flowStepId (which are the same as the ones recorded by {{PetalsFileHandler}}) and dumpPath (which tells where the message is actually recorded).
Once the dump is done, a MONIT level log trace is recorded in the {{flow.log}} file, with the following informations: traceCode, flowInstanceId and flowStepId (which are the same as the ones recorded by {{PetalsFileHandler}}) and dumpPath (which tells where the message is actually recorded).
When you activate the log handler {{PetalsPayloadDumperFileHandler}}, 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}}
* for log trace with level MONIT:
** the content of service request and reply is dumped in a file identified as following: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/<flow step id>_<trace code>.xml}}
** the file name of the dumped message is added as a new attribute {{payloadContentDumpFile}} of the MONIT log trace.
* 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 service request and reply is dumped in a file identified as following: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/<flow step id>_<trace code>.xml}}
** the file name of the dumped message is added as a new attribute {{payloadContentDumpFile}} of the MONIT log trace.