Event log for programs

[johnnyt]

Would like to see an event log for programs with the ability to turn logging on/off by individual program with a global all on / all off override. In my mind it would have entries something like this:

 

timestamp, program name, action (evaluated/activated/waiting/finished), initiated by (auto, manual, program name, startup), condition (true/false), state (running then/running else/not running), next scheduled

 

e.g.

2012-01-05, 20:00:00.00, Program X, evaluated, auto, true, running then, 2012-01-05 21:00:00.00

2012-01-05, 20:00:01.23, Program X, waiting, auto, true, running then, 2012-01-05 21:00:00.00

2012-01-05, 20:00:02.34, Program X, finished, auto, false, not running, 2012-01-05 21:00:00.00

 

2012-01-05, 20:01:03.45, Program Y, activated, Program A, false, running else, n/a (called by "Run Else")

2012-01-05, 20:01:03.56, Program Y, waiting, Program A, false, n/a

2012-01-05, 20:01:05.12, Program Y, evaluated, auto, true, running then, n/a (condition changed while running)

2012-01-05, 20:01:05.23, Program Y, waiting, auto, false, n/a

2012-01-05, 20:01:05.45, Program Y, finished, Program B, true, not running, n/a (stopped by Program

 

2012-01-05, 20:02:34.56, Program Z, evaluated, auto, true, not running, n/a (program used as a flag)

 

I know there would be redundancy in most cases when tracking both "true" and "running then", or tracking "finished" and "not running" but I'm suspecting that isn't always the case and could be useful to know. I tried to show an example of when there isn't redundancy with the last line (Program Z), but maybe this just isn't something that would happen. Obviously this would require some experimentation.

 

IMO, this type of log would be helpful not just to help troubleshoot programming problems more quickly during initial development and as needed after, but also to leave on in some cases to keep a history.

 

Apologies if this has been asked before. I tried a search for "event log for programs" (all terms) but it ignored the words "log for programs"

[Michel Kohanim]

Hi johnnyt,

 

I think this is a great idea but, at the same time - and based on your previous post - I think had you had this feature turned on, your system would've come to a grinding halt.

 

All this said, yes, we should have some lower level debugging (not as elaborate as you have listed) to help with loops and programming issues.

 

With kind regards,

Michel

[isy99user]

I've just been debugging a problem when some more information in the log (the one you can download to excel) would have been helpful.

 

But not sure I would go as far as johnnyt.

 

Right now the log has "user" column which just says "system" or "program". It would be very helpful if there could be a little more information.

 

For example rather than just have "program" have "program + the name of the program"...

For example rather than just "system" have "system + internal" (for an event generated by the ISY) or "system + external" (for an event received by the ISY).

 

This would make the log considerably more comprehendible and usable for debugging.

 

Thanks

[Michel Kohanim]

Hello isy99user,

 

Thanks so very much for the feedback.

 

I do agree ... having names of the programs in the logs is very important.

 

With kind regards,

Michel