Diagnostic Logging Question..

I have been contemplating this and wanted to go on and ask....Is it a good idea to go on and have this logging going on even if everything seems to be working? With the need of having the logs on a failure...would it not be better to go on and have them created?

Find more posts tagged with

Comments

Dave Hooton

When 4.0b is released it will produce a crash log irrespective of logging being enabled/disabled. So I would permanently enable logging in 4.0a as problems have occurred when people thought it was running fine, and they may not be reproducible.

Rosie Perera

https://community.logos.com/discussion/comment/97850#Comment_97850

When 4.0b is released it will produce a crash log irrespective of logging being enabled/disabled. So I would permanently enable logging in 4.0a as problems have occurred when people thought it was running fine, and they may not be reproducible.

Also the log files generated by enabling logging are much more detailed than the crash log which only shows the crashing error message and the program call stack as it existed at the time of the crash. I have not noticed any performance degradation from having logging on all the time, so I'd go for it. You can always turn it off again if you find it is slowing things down for you. But you can't turn it on and collect the useful data after the fact if the program crashes. So if you had stumbled on a non-reproducible crash you wouldn't be able to help Logos track it down without having had logging enabled from the get-go.

TCBlack

https://community.logos.com/discussion/comment/97879#Comment_97879

The only downside I've noticed to having logging on all the time has started since I installed microsoft mesh on my computer. Since I have my documents syncing to the mesh; the logos logs directory is continually updating since I'm always running Logos.

I haven't figured out how to tell mesh to "sync everything but this directory" (yet).