Because "tracing" was until recently considered as a debugging option, there is no way to create disticnt trace files for every job. Although, in the notification event/script of a job you can put some generic code like
FileCopy "@V"24x7_home"\\script.log", "@V"24x7_home"\\@V"job_id".log"
which will copy script.log to [job_id].log file, this does not guarantee the correct log contents, because more multiple jobs can run simultaneously. Tracing was available from very first version of 24x7 when it didn't have a script debugger, so it was the only way to debug script job executions. The good news are that in coming soon version 3.2 it will have a built-in option to write job owned trace files, so each job can write to it's own trace file with an additional option to append or overwrite the job trace file on a new run. : I need to be able to automatically save the contents of the JAL log file
: after the execution of specific scripts. I can manually locate the
: logfile.txt file in the 24x7 program folder and rename and copy that to an
: archive location, but that seems somewhat bacdoor. Is there a better way?
: Thanks.
|
