Engine log update

[GoogleCodeExporter]

Instead of writing engine log in the same file botssys/logging/engine.log and 
logrotate all others (numbers depend on log_file_number param in bots.ini),

write engine log file in a new engine log folder "botssys/logging/engine/"  
named with his own report idta. maybe split log by filereport ?

It's to provide quick way to view it for check if something is bad in this log.

In the same time add a new field in route table :
  - Conservation log : to specified when keep or not log file.
    (Never, When error(s) occur(s), Always)

Maybe another field to specified the delay of log conservation.

Original issue reported on code.google.com by [email protected] on 18 Apr 2014 at 9:53

[GoogleCodeExporter]

> Instead of writing engine log in the same file botssys/logging/engine.log and 
logrotate all others (numbers depend on log_file_number param in bots.ini),
> write engine log file in a new engine log folder "botssys/logging/engine/"  
named with his own report idta. maybe split log by filereport ?
yes, that is possible (doing a rename of engine.log after a run)
can display the idta of run in GUI easily.

>
> It's to provide quick way to view it for check if something is bad in this 
log.
>
> In the same time add a new field in route table :
>   - Conservation log : to specified when keep or not log file.
>     (Never, When error(s) occur(s), Always)
that might be a very good idea!
>
> Maybe another field to specified the delay of log conservation.
>
now there is the number of logs (default=10).
If logs with errors are kept longer that could be a new parameter in bots.ini 
(eg numberofdayserrorlogsarekept)

Original comment by [email protected] on 20 Apr 2014 at 12:12

• Added labels: Bots-engine, version3.2

[GoogleCodeExporter]

> yes, that is possible (doing a rename of engine.log after a run)
> can display the idta of run in GUI easily.

Great and very useful to make a engine log view !

> now there is the number of logs (default=10).
> If logs with errors are kept longer that could be a new parameter in bots.ini 
(eg numberofdayserrorlogsarekept)

Yes, it could be maxdaysenginelog ?

Original comment by [email protected] on 21 Apr 2014 at 7:48

[GoogleCodeExporter]

I manage this with botsengine exit points script. After each run, the log is 
read looking for warnings or other messages of interest. These are saved in 
separate logs that persist for 7 days or longer. All the previous day's 
warnings are added to a daily housekeeping email report in postcleanup.

Original comment by mjg1964 on 28 Apr 2014 at 10:35

[GoogleCodeExporter]

another option here is to check if run has errors;
that is a relatively easy check.

Original comment by [email protected] on 1 May 2014 at 1:05

[GoogleCodeExporter]

Yes, and maybe check if there is no input/output file in the run, add a 
conservation option for this case :
 - empty run log  : - don't keep
                    - delete in the maintenance 

Corresponding to hoursrunwithoutresultiskept ?

Original comment by [email protected] on 1 May 2014 at 4:27