When the limit of job log, access log, or eco-friendly log that can be kept on the machine is exceeded and new logs are generated, old logs are overwritten by new ones. If logs are not downloaded periodically, it may not be possible to record the old logs onto files.
When using Web Image Monitor to manage logs, download the logs at an interval appropriate to the conditions shown in the table.
After downloading the logs, perform a batch deletion of the logs.
If you change the [Collect]/[Do not Collect] setting for log collection, you must perform a batch deletion of the logs.
Maximum numbers of logs that can be stored in the machine
Log types |
Maximum number of logs |
---|---|
Job logs |
4000 |
Access logs |
12000 |
Eco-friendly logs |
4000 |
Estimated numbers of logs created per day
Log types |
Number of logs created per day |
---|---|
Job logs |
100 |
Access logs |
300 This number is based on 100 operations such as initialization and access operations over the Web, and 200 job entries (2 entries per job: 1 login and 1 logout). |
Eco-friendly logs |
100 |
According to these conditions, the machine can maintain logs for 40 days without overwriting. We recommend downloading logs every 20 days in case errors may occur.
The machine administrator must manage downloaded log files appropriately.
While logs are being downloaded, do not perform operations that will create log entries because as the logs that are being downloaded cannot record new entries.
Batch deletion of logs can be performed from the control panel or through Web Image Monitor.