With the Logger adapter you can write into the log file of the service. Use the log operation in this case:
| Name | Type | Direction | Description | Allowed Values / Examples |
|---|
| level | String | in | Specify one of the error log levels described in the log level guidelines on Bridge Server Log Levels of an xUML Service. | One of Fatal, Error, Warning, Info, and Debug. |
| type | String | in | Specify a custom error domain. This usually is the application name where the error occurred. | Stock_Synchronization |
| code | String | in | Specify a custom error code. | SYNC001 |
| description | String | in | Specify a description for the log entry. | Item ID could not be found. |
| details | Any | in | Specify an object of complex type (class or array) that contains additional details. If provided, 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 | - An error detail object:
{ "element": "AF-1201", "value": "Adapter" }
- An array of objects:
[
{ "element": "AF-1201", "value": "Adapter" },
{ "element": "CD-2000", "value": "Connector" }
]
|
The output after running the example can be found in the standard xUML service log 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'