Estimated number of logs created per day
Job logs Access logs Eco-friendly logs
100 (per day) 300
This figure is based on 100 operations such
as initialization and access operations over
the Web and 200 access log entries (two
entries per job: one login and one logout).
100 (per day)
According to these conditions, the machine can maintain logs for 20 days without overwriting, but to be
cautious, we recommend downloading after half that time, 10 days, to leave room for error.
It is the responsibility of the machine administrator to deal downloaded log files appropriately.
• If you change the [Collect] / [Do not Collect] setting for log collection, you must perform a batch
deletion of the logs.
• After downloading the logs, perform a batch deletion of the logs.
•
During log downloads, do not perform operations that will create log entries, as logs that are in the
process of downloading cannot be updated with new entries.
• Batch deletion of logs can be performed from the control panel or through Web Image Monitor.
Notes on operation when the number of log entries reaches maximum
If the number of logs that can be stored on the machine exceeds the specified maximum value, the oldest
logs are deleted and overwritten by newer logs. Whether or not the maximum number of logs that can
be stored exceeds the maximum depends on the types of logs, which are job logs, access logs and eco-
friendly logs.
The job log and access log are downloaded as one file.
"If logs are downloaded without overwriting" below indicates that the job log and access log are mixed
after download.
"If logs are downloaded during overwriting" below indicates that part of the access log is overwritten.
In this example, part of the access log was overwritten by a downloaded log and deleted.
The eco-friendly log is downloaded as an independent file.
When logs are overwritten, it depends on the priority order and the logs with higher priority will not be
overwritten or deleted.
Managing Log Files
209
To Next Page
Loading...
Need help?
General
