Page History
| Div | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
The With the <<Logger>> adapter writes via a queue asynchronously you can write into the log file of the service. Use action log in this case.
The input consists of error level, code, type, and description. The log levels are: Fatal, Error, Warning, Info, and Debug as following picture shows the usage of the <<Logger>> adapter:
Tag action of the logger adapter needs to be set to log. The following input can be provided:
| Object Name | Type | Description | Allowed Values / Example | |
|---|---|---|---|---|
| level | String | Specify one of the error log levels described in the log level guidelines on Log Levels of an xUML Service. | ||
...
The following picture shows the usage of the <<Logger>> adapter.
Figure: Writing into the Standard xUML Service Log
Example
...
| One of Fatal, Error, Warning, Info, and Debug. | ||||
| type | String | Specify a custom error domain. | Stock_Synchronization | |
| code | String | Specify a custom error code. | | |
| description | String | Specify a description for the log entry. | Item ID could not be found. | |
| details | Any | Runtime 2020.6 Builder 7.8.0 Specify an object of complex type (class or array) that contains additional details. The contents of this object will be flattened and appended to the description. | an error detail object | |
Example
| Pin | Value |
|---|---|
| level | Error |
| type | Stock_Synchronization |
| code | SYNC001 |
| description | Item ID could not be found. |
| details |
|
The output after running the example can be found in the standard xUML service log on the E2E Bridge. of the xUML service:
...[Error][Internal][Stock_Synchronization][Item ID could not be found. Detail: e2e:type='ErrorDetail', element='AF-1201', value='Adapter']
In case of an array, the output would look something like:
... Detail: e2e:type='ErrorDetail', [0].element='AF-1201', [0].value='Adapter', [1].element='CD-2000', [1].value='Connector'
Overview
Content Tools