Monitor data exchange

In Data modeling studio, for monitoring purposes, executed actions are logged.

The main activities for which logging is done are:

• Deploy: All actions that are executed when you deploy a data model are logged. Each time you deploy a data model, an execution ID is created to which all executed deploy actions are related
• Data export: All actions that are executed when you export data are logged.
• Metadata updates: Metadata updates are only logged if on the Data modeling studio parameters, Log metadata updates is 'Yes'.

Note: On deploy or data export, executed SQL statements are only logged if on the Data modeling studio parameters Log executed SQL statements is 'Yes'.

Logging is done on three levels:

• Summary: Each deploy or data export results in a record in the summary. Each record is identified by the context (data model) and the execution ID.
• Log: The actions that are executed by the deploy, data export, or metadata update.
• Processing: The export statistics for each exported business entity (data set or data entity) as defined for the deployed or exported data model.

Data modeling studio has several options to troubleshoot data exports.

The deploy and export history is logged. Over time, the number of logged records grows. To limit the number of logged records in the database, you can refresh the history. If you refresh the history, the retention settings of these Data modeling studio parameters are applied:

• Log record retention (days): On refresh, only the log records are kept that are within the number of defined retention days.
• Processing record retention (days): On refresh, only the processing records are kept that are within the number of defined retention days.

Example: Number of retention days is 7. Today you Refresh. As a result, all logged records are deleted that are older than a week.