Not a bad idea! However, consider that now you can control the size of the current file by limiting the maximum number of entries in the 24x7 system options. Also, you should not allow frequent jobs that run every few minutes or even seconds to write to the log file, so in most situations you should have only a few tens records a day.
For the sake of our discussion, let's assume you have 50 daily jobs and 10 monthly jobs that create in average about 100 log records a day. Having 3000 record limit we should have about 30 days of history with 1-day rotation every day. The size of such file should be somewhere between 10K and 30K, which for today browsers and computers is a piece of cake. If you would like to keep a longer history you may want to create a job that runs let's say once a week and archives all HTM files to some directory on your network server or even ZIP them down. : What do you think about a change in the structure of the HTML Log file in the
: following way: Each day creates an own HTML file for the right frame.
: The left frame contains links to the "daily" HTML files.
: Using this, 24x7 would not have to handle with one huge HTML file, and the
: overall performance would be raised ...
|
