Logging

PaperCut NG/MF has two types of logging within the Administration pages; Application and Audit logging. Both log views are accessible via the Logs tab for users with sufficient administrative rights to view these. In both cases, there are some minor configuration changes an administrator might want to tune.

Application Logs

The Application Log retains a complete history of system events (errors, notifications, alerts, etc), unless configured otherwise.

Application Log Configuration Keys

Audit Logs

The Audit Log retains a complete history of administration changes to a user, unless configured otherwise.

You can disable this if a customer does not want to retain this information via Options > Advanced > Diagnostics > Enable audit logging

Additional config options exist in the Config Editor :

Application Log Configuration Keys

Job Logs

The Job Log is a separate log type that records all print, copy, and scan activity on the network. Each entry captures the:

• user who printed
• time of the print event
• number of pages and document attributes (color, duplex, paper size, etc.)
• source workstation name or IP address
• document name and type
• cost of the job, if a cost model is assigned.

To access the job, in the Admin interface, go to Logs > Job Log.

You can export the job log as a PDF, HTML, or CSV file in the Reports section.

How long are job logs retained for?

You can keep data indefinitely in the Job Log — unless you configure otherwise — because by default, PaperCut has no hard limit on the size of the Job Log; it can’t be filled. That means PaperCut Hive and Pocket are designed so that large databases with historical log data do not slow down day-to-day use.

Where is job log data stored?

Job log data is stored in the tbl_printer_usage_log database table.

How to clear job log entries

For instructions on how to manage job log retention and clear the job log data, see Partially Clearing Logs.