E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (2)
View Page History
...
The following terms are defined in Petals ESB context and must be used in all technical and functional documents. * -loggerName- |
| Trace code | A code identifying uniquely a trace type in log. For example, all service invocations are logged on the consumer side with the same code. \\ | * traceCode |
| Trace code | A code identifying uniquely a trace type in log. For example, all service invocations are logged on the consumer side with the same code. \\ | * traceCode |
| Log level | All log traces have a level indicating their severity. The logging system can be configured to filter traces to log against their severity (see [Logging in Petals]). Available severity are: \\ | |
* *ERROR*: An error occurs when the service can not be provided:
** In a Petals ESB container point of view, an error is something that stops the processing of an internal component. Consequently, the Petals ESB is stopped because it can assume its functions.
** In a component (BC/SE) point of view, an error is something that stops the processing of the SE or BC, but other components are always running correctly. Consequently, the component could be stopped.
** In a service (service-unit) point of view, an error is something that stops the processing of a service, each service invocation will fail, but other services deployed on the same component are correctly running. Consequently, the service could be stopped.
* *WARNING*: A warning occurs when the service is partially provided and is compensated by a default behavior or it could be hot-fixed without restart or re-installation.
* *INFO*: The information level highlights the provided service. Such a trace is logged parsimoniously. For example, service life cycle states are logged with this level.
* *CONFIG*: All parameter values are logged with this level.
* *MONIT*: This level is used to trace incoming and outgoing service messages to be able to monitor process executions in a business point of view.
* *DEBUG*: All traces that can help a problem analysis are logged with this level. | |
** In a Petals ESB container point of view, an error is something that stops the processing of an internal component. Consequently, the Petals ESB is stopped because it can assume its functions.
** In a component (BC/SE) point of view, an error is something that stops the processing of the SE or BC, but other components are always running correctly. Consequently, the component could be stopped.
** In a service (service-unit) point of view, an error is something that stops the processing of a service, each service invocation will fail, but other services deployed on the same component are correctly running. Consequently, the service could be stopped.
* *WARNING*: A warning occurs when the service is partially provided and is compensated by a default behavior or it could be hot-fixed without restart or re-installation.
* *INFO*: The information level highlights the provided service. Such a trace is logged parsimoniously. For example, service life cycle states are logged with this level.
* *CONFIG*: All parameter values are logged with this level.
* *MONIT*: This level is used to trace incoming and outgoing service messages to be able to monitor process executions in a business point of view.
* *DEBUG*: All traces that can help a problem analysis are logged with this level. | |
{petalslink:type=TODO Add terms}* Petals topology,
...