System Logs gives administrators direct access to OptimiDoc's internal server logs for troubleshooting, performance monitoring, and support diagnostics. The viewer offers parsed and raw display modes, date navigation, severity and thread-ID filtering, full-text search with context lines, and log-file downloads.
Screenshot: System Logs view
Overview
The System Logs page is the primary tool for investigating what the server actually did. Logs record detailed information about every operation — print-job processing, scan workflows, device communication, authentication, and errors. Two log types are available:
-
Web Logs — generated by the OptimiDoc web application (IIS-hosted): API requests, authentication, job processing, and web-interface operations.
-
Service Logs — generated by the OptimiDoc Windows service: background tasks, device communication, scheduled operations, and service-level events.
Where the Audit Log shows structured business events, System Logs expose the underlying application log files line by line — the right tool when you need low-level detail or a file to send to support.
Accessing System Logs
-
Log in to the OptimiDoc web interface as an administrator.
-
Navigate to Diagnostics > System Logs in the left sidebar.
Log Viewer
The viewer is organised into three tabs: Web Logs, Service Logs, and Download.
Viewing logs
-
Select the Web Logs or Service Logs tab.
-
Choose a date with the date picker. Only dates that have log data are selectable.
-
Set the severity filter to control which messages appear. The filter is inclusive — each level also shows everything more severe than it. The default is Warning.
|
Level |
Description |
|---|---|
|
Errors |
Errors and the most severe (fatal) entries that require immediate attention. |
|
Warnings |
Potential issues, plus all errors. |
|
Info |
General informational messages, plus warnings and errors. |
|
Debug |
Detailed technical messages for in-depth troubleshooting. |
|
Trace |
The most verbose level, showing every internal operation. |
You can also sort entries newest-first or oldest-first, and filter by Thread ID to follow a single request or worker thread through the file.
View modes
-
Parsed — shows entries in a structured format with colour-coded level indicators, timestamps, and messages. Recommended for general use.
-
Raw — shows the raw log file text without formatting. Useful for copying data to share with support.
Searching logs
Use the search box to filter the loaded day's entries by keyword. Matches are highlighted and non-matching lines are hidden. The context lines control sets how many surrounding lines are shown around each match:
|
Setting |
Effect |
|---|---|
|
0 |
Only matching lines are shown. |
|
2 / 5 / 10 |
Two, five, or ten lines of context before and after each match. |
Downloading Logs
Single day
From the Web Logs or Service Logs tab, click Download Log to download the log file for the currently selected date as a plain text file.
Date range
Switch to the Download tab for bulk downloads:
-
Choose the log type (All, Web, or Service).
-
Set the From and To dates.
-
Click Download.
The matching daily log files are packaged into a single ZIP archive named logs_<from>_<to>.zip and downloaded to your browser.
Tips
-
Start at the Warning level when investigating an issue; drop to Info or Debug if you need more detail.
-
Search for an error code or device name to jump straight to the relevant lines, then widen the context lines to read around them.
-
Use the Thread ID filter to isolate a single operation when many run concurrently.
-
When contacting support, use the Download tab to export the relevant range and attach the ZIP to your request.
-
Each cluster node writes its own logs. For an intermittent issue, check the logs on every node.
Related articles