Page History
| Div | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
With the The <<Logger>> adapter also writes you can write transactional logging information via a queue asynchronously into the transaction log file of the xUML service.Use action report in this case. The logged information is usable for performance measurements or statistical evaluations (how often has the transaction been called, in which context, etc.). On the E2E BridgeRefer to MINING for more information on how to analyze this data.
- For the logger to write logs to the transaction log at all, the transaction log level of the xUML service needs to be set at least to Custom.
For more information about the transaction log levels see Transaction Log Levels of an xUML Service.
The following picture shows the usage of the <<Logger>> adapter for this case.Figure: Writing into the Transaction xUML Service Log
Figure: Logger Tag action
The Tag action of the logger adapter needs to be set to report. The following input can be provided:
| Object Name | Type | Description | Field in Transaction Log | Allowed Values / Example | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| domain | String | Specify a self-defined name of the domain of the logged entry. | Domain | Stock_Synchronization | ||||||
| state | Boolean | true or falseSpecify how to set the status field in the log entry. This will result in setting the status field in the log entry | to OK respectively ERROR. | State | true | Set the status field to OK. | ||||
| false | Set the status field to ERROR. | domain | String | self-defined name of the domain of the logged entry | Domain||||||
| parameter | String | Specify a self-defined parameter. | Parameter 2 | Item: YY-2388 | ||||||
| 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 logged instead of parameter. | e2e:type='ErrorDetail', element='YY-2388', value='Connector' | ||||||||
| description | String | Specify a description for the log entry. | Parameter 1 | Item ID could not be found. | ||||||
| timestamp | DateTime | Bridge 7.0.0-beta2 Specify a custom timestamp. This parameter is optional. If it is not given, the timestamp in the transaction log will be generated from the current timestamp.
| Date, Time | NULL | Generated timestamp in the transaction log. | |||||
| a value | Dedicated timestamp in the transaction log. | |||||||||
Example
...
Custom Error Details
| Pin | Value |
|---|---|
| domain | Stock_Synchronization |
| state | true |
| description | |
| parameter |
|
The output after running the example can be found in the xUML Service Transaction Log of the xUML service:
... OK Stock_Synchronization CUSTOM Synchronization started. e2e:type='ErrorDetail', element='YY-2388', value='Connector'
In case of an array, the output would look something like:
... e2e:type='ErrorDetail', [0].element='YY-2388', [0].value='Connector', [1].element='YZ-1222', [1].value='Adapter'
Custom Timestamp
| Pin | Value |
|---|---|
| domain | Stock_Synchronization |
| state | true |
| description | |
| parameter | Item: YY-2388 |
| timestamp | 2020-01-01T00:01:59 |
The output after running the example can be found in the xUML Service Transaction Log on the E2E Bridge. of the xUML service:
2020-01-01 00:01:59 ... OK Stock_Synchronization CUSTOM Synchronization started. Item: YY-2388'
Overview
Content Tools