Logging

For running services, the xUML Runtime writes information to the xUML service log.

Depending on the log level of the service, this can be

• errors

• warnings

• general information

• low-level debug information

For services where transaction logging is enabled, the xUML Runtime writes information to the xUML transaction log.

Depending on the log level of the service, this can be

• custom log messages

• information about calls to service interfaces

• information about internal adapter calls

• information about external adapter calls

• Use the service log for general process information

• Log less but important resp. exceptional events e.g.

  • Scheduler started/ended

  • Order found / not found

  • File found / not found

• Use the transaction log for deeper analysis

• Log information per object/transaction:

  • Information in a transaction context, e.g. which messageID has initiated that process

  • Performance relevant information

Contents of the xUML Service Log

Contents of the xUML Transaction Log

You want to to filter for the log information.

In this case, we recommended to use the transaction log.

The transaction log is structured by tabs and can easily be pasted into an Excel sheet to use all Excel filtering facilities.

Refer to Structure of the Transaction Log on page Contents of the xUML Transaction Log.

You want the xUML Service Monitor to notify you on an error, but the service should continue to run.

Use a log operation of type "Error".

Refer to Monitoring xUML Services for more information about the xUML Service Monitor.

You want to log data for analysis in Process Mining.

Use the LogKPI asset to log the relevant data. This standard library is available in the Asset Drawer of the Designer.

You want to log service dependencies to the transaction log.

Set a transactionID.

A transaction ID allows you to trace information through the call stack of multiple service calls.