Support Logs
optimus check writes one privacy-safe support log for every non-dry-run unless logging is disabled.
Dry-run mode never creates a support log.
Default Log Locations
| Mode | Default log folder |
|---|---|
| Single-file mode | <input-file-directory>/logs |
| Folder mode | <folder>/logs |
| Missing path or early config error | ./logs |
Override the folder:
optimus check customers.csv --map mapping.yml --standard --log-dir ./logs
Disable the support log:
optimus check customers.csv --map mapping.yml --standard --no-log
File Name
Log files are named like:
optimus-check-20260512T140000Z-a1b2c3d4.log
Each run also has a short run ID.
What Logs Include
Support logs can include:
- Run ID.
- Start time.
- CLI version.
- OS and .NET framework information.
- Working directory.
- Input path.
- Mapping path.
- Output path.
- API target without query string or credentials.
- Check type.
- Flags such as quiet, verbose, PDF, signing, notification, and force-new.
- Validation operation ID.
- Idempotency key.
- API statuses.
- Result path.
- PDF path.
- Exit code.
- General errors and stack traces for CLI errors.
What Logs Do Not Include
Support logs do not include:
- Tokens.
- Request bodies.
- Response bodies.
- CSV row values.
- VAT IDs.
- Company names.
- Addresses.
- Custom column values.
If you contact support, include the support log path or the log file unless your internal policy says otherwise.