Skip to content

Logs

The task logs provide detailed information about each task's execution, including any errors or issues encountered. This feature is crucial for troubleshooting and ensuring that data generation processes run smoothly.

Task Logs
Task Logs

Accessing Task Logs

Task logs can be accessed from the task execution list by clicking on the log icon. This view displays the logs for the selected task, providing insights into the task's execution process.

Log Actions

At the top of the log view, the toolbar provides the following controls:

Log Actions
Log Actions
  1. Auto refresh (5s): Toggles automatic reloading of the log content every 5 seconds.
  2. Scroll to head / Scroll to end: Jumps to the beginning or end of the log.
  3. Refresh: Reloads the log content to display the most recent information.
  4. Download log: Allows you to download the log file for offline analysis or record-keeping.

This functionality ensures that users can keep track of task executions and handle any issues promptly, maintaining the integrity and reliability of their data generation processes.

Run Summary Lines

Many generation and database-scan tasks now include a short Run summary line in the logs.
These entries are optimized for quick human review in downloaded log files and include key execution metrics such as:

  • scanned tables/columns
  • action distribution (for example, generator/script/converter counts)
  • PII candidate/key counts
  • top generator usage
  • release label used at runtime

Example:

1
2
3
4
5
6
7
Run summary (DB scan):
- Release: 3.2.0; analysis: 1.0.0; registry: 7ae50afda1bc6c51
- Scope: full (system_policy=default)
- Schemas: discovered=4, eligible=4, selected=4, reflected=4
- Data: tables=609, columns=8,073, columns_with_actions=8,073, entity_recommendations=362, pii_candidates=323
- Actions: generator (7,711), script (362)
- Top generators: StringGenerator (2,711), IntegerGenerator (2,469), DateTimeGenerator (1,697), IncrementGenerator (714), FloatGenerator (95)

Note

If your deployment does not set RELEASE_VERSION, logs show release not configured for traceability.

Error Codes

DATAMIMIC uses standardized error codes for consistent troubleshooting. When errors occur, they appear in the logs with:

  • Issue Code: Unique identifier (e.g., I322)
  • Message: Description of the problem
  • Location: File and line number
  • Guidance: How to resolve the issue

Example log entry:

1
2
3
[ERROR] I322: Dynamic targetEntity is only supported for routing-capable exporters (TemplateSingle, JSONSingle, XMLSingle, mem). Unsupported targets: {targets}
  Location: models/export.xml:45
  Guidance: Use TemplateSingle/JSONSingle/XMLSingle/mem or remove dynamic targetEntity values.

See the Error Codes Reference for a complete list of error codes and their resolutions.

Note

Logs are available for every task execution, whether it was initiated by a manual generation, advanced generation settings, or triggered by a CRON schedule. This ensures complete traceability and accountability for all operations within DATAMIMIC.