rhughes Posted December 3, 2008 Posted December 3, 2008 I have found the log very useful for finding problems. However, I haven't seen a way to include Program execution in the log. It would be extremely helpful to have Program log entries added that included (along with the Program name): IF Run by Event IF Run Directly by THEN Started by IF THEN Started Directly by THEN Interrupted THEN Ended ELSE Started by IF ELSE Started Directly by ELSE Interrupted ELSE Ended Thanks. ------------------- Randy
Michel Kohanim Posted December 4, 2008 Posted December 4, 2008 Rand, Excellent idea. It shall be added to our requirements. With kind regards, Michel I have found the log very useful for finding problems. However, I haven't seen a way to include Program execution in the log. It would be extremely helpful to have Program log entries added that included (along with the Program name):IF Run by Event IF Run Directly by THEN Started by IF THEN Started Directly by THEN Interrupted THEN Ended ELSE Started by IF ELSE Started Directly by ELSE Interrupted ELSE Ended Thanks. ------------------- Randy
rhughes Posted December 4, 2008 Author Posted December 4, 2008 Another approach that might work (instead of, or in addition to, Program logging) is to add another column to the log called "Controller". Example controllers might include: - Manual (for devices) - Scene (for devices) - Device (for scenes, however it may be necessary for devices if a scene can't be resolved from a manual switch control) - ISY Program (THEN) (For devices or scenes) - ISY Program (ELSE) (For devices or scenes) - ISY External API (For devices or scenes) I guess this could be difficult if you don't always know the ultimate source of the controller (e.g. other than the PLM). --------------------- Randy
Michel Kohanim Posted December 4, 2008 Posted December 4, 2008 Hi Randy, I like it ... we actually have to revamp our logging because it's quite rudimentary now. We do know the source of each action including the IP address of a remote client. All this information should be available in the log. Thanks and with kind regards, Michel Another approach that might work (instead of, or in addition to, Program logging) is to add another column to the log called "Controller". Example controllers might include: - Manual (for devices) - Scene (for devices) - Device (for scenes, however it may be necessary for devices if a scene can't be resolved from a manual switch control) - ISY Program (THEN) (For devices or scenes) - ISY Program (ELSE) (For devices or scenes) - ISY External API (For devices or scenes) I guess this could be difficult if you don't always know the ultimate source of the controller (e.g. other than the PLM). --------------------- Randy
Recommended Posts
Archived
This topic is now archived and is closed to further replies.