Any problems with leaving verbose logging on?

[pjr]

Hi,

It's becoming quite a problem for us having to reboot 3CX servers for clients when we have enable verbose logging to get to the bottom of issues (expecially trying to co ordinate reboots during the day when multiple offices share a single server).

Is there any downside in leaving verbose mode permanently enabled, do the logs overwrite themselves or will they eventually eat up all available disk space?

Thanks

Paul

 

[KerryG]

I leave verbose on with the systems that I tend to work on the most, I leave it lower on systems that I never need to touch.

 

[pjr]

Thanks Kerry - I presume leaving Verbose on has not caused you any issues?

Paul

 

[KerryG]

Not yet

 

[Vali_3CX]

I guess, this is a personal choice, depending by what everybody expects from a tracelog file. Personally, on any program providing tracelog/debugging options, I enable this feature only when it behaves... not normally, and if I'm able to understand something useful from these files, or to send them to technical support. Otherwise, I disable this feature, because a tracelog involves disk space, additional CPU time, additional memory, additional resources.

 

[LeonidasG_3CX]

There will be NO problems at all with leaving Verbose logs on.
Absolutely nothing.

I to answer the next flying question before it's even asked:

Q: Why aren't Verbose logs enabled by Default in the installation?
A: At the moment Normal Logs provide sufficient info for a Normal user to understand the basic operations of the system.
E.g:
Normal Logs: 100 Calling 101 > 101 Accepted > Call Connected
Verbose Logs: Leg:C:1 Connected > Contact 101 rpid;js09fjdjjvjvjs9jvxcl0apkpszx; SDP bladabladabla > Requires Proxy Auth Xyz omgbbq

And dont even ask what Low Logging mode does That's something i just realized i've propably never used...

 

[pjr]

There will be NO problems at all with leaving Verbose logs on.
Absolutely nothing.

Exactly the answer I was hoping for - thanks Leonidas!

Paul