[ekicholong]

Hi Ray,

Thank you very much for the feedback. Any solution is very much appreciated.

To answer your questions;

I have a configuration file which contains MaxParts, MaxSize, FileName, FilePath amongst other properties for configuring logFileDestination. Only a developer, a support-team and a test-team member should be able to edit this file and change the values of these properties.  The file is being used by an application generating quite a large number of logs using codesite.

The idea of later changing values of especially MaxParts and MaxValue via a configuration file came about as I am yet to determine the optimal values to use for the end-users. And so during the testing phase I want to experiment with different values until i get an optimal one, which means that there could be an instance where it might be necessary to for example increase or reduce the value of MaxParts (and or MaxSize) depending on the size of logs generated – without having to recompile the application. Perhaps it is worth to note that the application testing is done by a separate test-team who only get the compiled binaries and one of my test request would be to observe the size and the number of logfiles generated. In addition, during a support session for an end-user (customer), a support-team member might realise that there is need to increase or decrease the value of MaxParts (and or MaxSize) depending on the number of logs generated which vary between users. In both cases you want to ensure that tester’s or user’s computer is not littered with uneeded log files.

 

[ekicholong]

Thank you for your reply.

For issue 1, yes it is correct to assume that there were 6 log files in a folder before i changed MaxParts from 6 to 3 and started a new logging session.  And also for issue 2, there were 12 log files before changing MaxParts from 12 to 8. I can confirm that i changed the value of MaxParts property only.

By “new log files are also generated on top of the existing ones.” I meant that after the last file part is full, new log file parts are generated on top of the existing ones using the name numbering pattern. If for example sample_6.csl was the last file part, first its filled up and once full new files are created as follows: sample_7.csl, sample_8.csl etc.  In the case of issue 1, new log file parts are created up to sample_10.cls and then all new logs are saved only in this one file until i stop the logging session. And in the case of issue 2 where MaxParts > 10, new log file parts are continously created until i stop the logging session.

My comment “no file should exceed the size limit set by the MaxSize whatsoever” was only in reference to issue 1 where by sample_10.csl continously grows in size waaay above the set MaxSize value. But I agree with you and I am aware of what you are saying, that the last file part can slightly outgrow the value of MaxSize in order to accomodate the last message. That is ok as long as all other new messages are not saved in the same file therefore increasing it’s size as is the case with sample_10.csl.

I do hope am a bit clear now and am willing to offer more information if required to.

Cheers

[Author]

Posts