Print Log¶

The Print Log provides a chronological table of all print activity across your printers, giving you a quick at-a-glance history of every print.

Overview¶

The Print Log is a dedicated view mode within the Archives page that focuses on print activity as a flat, filterable table. Unlike the standard archive views (grid, list, calendar), the Print Log shows one row per print event with key details at a glance.

Accessing the Print Log¶

1. Go to the Archives page
2. Click the Print Log button in the header toolbar (next to the grid/list/calendar view toggles)

Table Columns¶

Each row in the Print Log represents a single print event:

Status Badges¶

Filtering¶

Narrow down log entries using the filter controls at the top of the table:

Combining Filters¶

All filters can be combined. For example, show only failed prints from "Workshop X1C" in the last week by selecting the printer, status, and date range together.

Pagination¶

The Print Log supports configurable pagination for navigating large histories:

The current page range and total entry count are displayed alongside the navigation controls.

Per-row actions¶

Every row in the Print Log has two action buttons on the right:

Edit (classification)¶

Click the pencil icon to classify the print run -- set or change the failure cause and status on a single entry.

The classification you pick here is what the Failure Analysis widget groups by, so updates flow into the dashboard charts immediately.

Delete (single row)¶

Click the trash icon to remove a single entry from the log. The entry's filament, time, and cost contributions drop out of Quick Stats in the same response cycle. The matching archive (if any) is not affected -- the log row is independent of the archive.

Clearing the Log¶

The Clear button removes all log entries from the database.

How It Works¶

Automatic Logging¶

Log entries are written automatically whenever a print completes. No configuration is required -- once archiving is active, print events are recorded in the log.

Independent Storage¶

The Print Log uses its own database table (print_log_entries), separate from the archives table. This means:

• Log entries exist independently of archives
• Deleting an archive does not remove its log entry
• Clearing the log does not affect archives
• The log is lightweight and optimized for fast querying

Permissions¶

When authentication is enabled, the Print Log respects the following permissions:

API Access¶

List Log Entries¶

GET /api/v1/print-log/

Query Parameters:

Example:

curl -H "X-API-Key: your-key" \
  "http://localhost:8000/api/v1/print-log/?status=failed&limit=10"

Update a Single Entry¶

PATCH /api/v1/print-log/{entry_id}

Edit the classification (failure cause and/or status) on one entry. Requires ARCHIVES_UPDATE_OWN for entries you created, or ARCHIVES_UPDATE_ALL for any entry.

Request body:

{
  "failure_reason": "cloggedNozzle",
  "status": "failed"
}

Both fields are optional. To clear an existing classification send "failure_reason": "".

Unknown values return HTTP 400 -- the canonical vocabulary above is enforced server-side.

Example:

curl -X PATCH -H "X-API-Key: your-key" -H "Content-Type: application/json" \
  -d '{"failure_reason": "cloggedNozzle"}' \
  "http://localhost:8000/api/v1/print-log/42"

Delete a Single Entry¶

DELETE /api/v1/print-log/{entry_id}

Removes one entry from the log. The entry's filament, time, and cost contributions drop out of /api/v1/archives/stats on the same request cycle. The linked archive (if any) is untouched. Requires ARCHIVES_DELETE_OWN for entries you created, or ARCHIVES_DELETE_ALL for any entry.

Example:

curl -X DELETE -H "X-API-Key: your-key" \
  "http://localhost:8000/api/v1/print-log/42"

Clear All Log Entries¶

DELETE /api/v1/print-log/

Removes all log entries. Requires ARCHIVES_DELETE_ALL permission.

Example:

curl -X DELETE -H "X-API-Key: your-key" \
  "http://localhost:8000/api/v1/print-log/"

Tips¶