Hi,
I like an extra column in the server log (log_server{yyyyMMdd}.txt) of visualcron.
Now we have:
date time logType message
The Extra column is like a job category. It could be the jobname like this:
date time logType jobName message
At this time it is hard to see which message belong to which job. I use the logging for debugging, but sometime I need to debug the logging 🤦
An other approach is that you give the jobs an Id in the log and refer every task to that Id.
date time logType increasingHexId message
So you get this kind of logging:
11/27/2008 10:00:00 PM Info 0000001 Job started: Test jobA
11/27/2008 10:00:01 PM Info 0000001 Task started: Task1
11/27/2008 10:00:02 PM Info 0000001 Task completed: Task1
11/27/2008 10:00:03 PM Info 0000001 Job completed: Test jobA
11/27/2008 10:00:04 PM Info 0000002 Job started: Test jobB
11/27/2008 10:00:05 PM Info 0000002 Task started: Task1
11/27/2008 10:00:06 PM Info 0000002 Task completed: Task1
11/27/2008 10:00:07 PM Info 0000002 Job completed: Test jobB
11/27/2008 11:00:00 PM Info 00000AC Job started: Test jobA
11/27/2008 11:00:01 PM Info 00000AD Job started: Test jobB
11/27/2008 11:00:02 PM Info 00000AC Task started: Task1
11/27/2008 11:00:02 PM Debug Saving Jobs
11/27/2008 11:00:03 PM Info 00000AC Task completed: Task1
11/27/2008 11:00:04 PM Info 00000AD Task started: Task1
11/27/2008 11:00:05 PM Info 00000AD Task completed: Task1
11/27/2008 11:00:05 PM Debug 00000AD Running File Notification: 'bla bla'
11/27/2008 11:00:06 PM Info 00000AC Job completed: Test jobA
11/27/2008 11:00:07 PM Info 00000AD Job completed: Test jobB
Every day you start at 0 and you can use hex numbers to have a lot of id's.
Visualcron tasks (not job related) don't have a jobId.
What do you think of this?
Regards
Erik
Uses Visualcron since 2006.