and the name of the user/account who ran the script
Add to that: Log script results from the Exit step.
I'm curious, in addition to the logs, where would you wan to see this info? UAC overview? Email? text message? All three?
Thanks for the input!
If possible I would love to turn on an option where I can ask the server to log the result of every single step along with the time it took to run it. And maybe even include script parameters and the exit script result as you stated here. I know this would slow things down on the client server side of things.
Maybe some options to only log errors if that is all you are interested in. But you logged all steps then you could look at the data to see what are the steps that are taking the longest to run. Or simply find the errors that are happening and track down why they are happenng.
Right now the only way we would know if users are experiencing errors is if we trap for them... and I would like to build systems that are more proactive ... I think Terry was speaking in this way today on the call.
I would love it if it were even only in the logs. But if it were in the logs see my first message on this. We have to have the columns of data split out. Otherwise ingesting it and reviewing it is almost useless.
I had also started another topic about notifications. I'll add some additional comments there ... but just real quick ... what if some event happened then this notification system could also email someone.
I am thinking that just like Web and Scripting the notifications system could be a separate process...
But not in the Windows application log... that would push out too many of the other (non FM) events if we have busy solution...
Remember Wim... I am saying it is a setting that you can turn on or off .. I konw it would slow things down but the point is that we would have a pool of really useful data to troll around in and see what is going on with the solutions that are hosted.
I hear ya, I just wanted to make sure it goes into its own separate log much like what is done for the access log and stats log.
But don't you think that even the current logs should have those extra columns - are you with me on that.
A separate Script Log could be a good idea and maybe include some information about the client wether it was FM Pro, Advanced, CWP, IWP, FM Go (iPhone, iPad, iPod Touch).