Estimated number of logs created per day
Job logs Access logs
100 (100 logs 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).
If the daily estimates are not exceeded, the machine can store logs for 20 days without having to overwrite
older logs. However, we recommend that you download the logs every 10 days. This will prevent unwanted
overwriting and ensure all logs are preserved, even if the daily estimate is exceeded.
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.
• Logs can be batch deleted via Web Image Monitor.
Notes on operation when the number of log entries reaches maximum
The machine reads the number of access and job logs and begins overwriting the oldest log entries to make
space for the new logs as they arrive.
Downloaded log files include both access and job logs, with some log entries incomplete.
The following illustration shows an example in which logs are downloaded during access log overwriting.
In this example, some of the access log entries are incomplete.
Logs are overwritten in reverse priority order, meaning logs of lowest priority are overwritten first and logs
of highest priority are overwritten last. This way, if the overwrite is canceled, there is a chance that logs of
higher priority will still be available.
6. Managing Access to the Machine
128
To Next Page
Loading...
