Question

Web Access Event Log Folder Size

Web Client How To Administration

Updated July 8

asked on July 8

Hi Laserfiche,

One of our customers has reported that the web access log folder located at C:\ProgramData\Laserfiche\WebAccess\EventLog is now more than 27GB in size and they'd like to know if this can simply be cleaned up periodically, and if so will this have any impact on system functionality/usability?

Cheers!

Chris Douglas

0 0

Answer

SELECTED ANSWER

replied on July 8

From the docs (link is redirected to the admin guide home page for some reason right now but shouldn't hard to find in the table of contents):

https://doc.laserfiche.com/laserfiche.documentation/11/administration/en-us/Default.htm#../Subsystems/WAConfiguration/Content/Diagnostics.htm

Diagnostics

The Diagnostics page allows you to select a log level for the web client, as well as to turn tracing on and off in order to locate a specific problem.

The following log levels are available:

Critical: Only very important errors will be logged. This is the default setting.

Important: All errors will be logged.

Informational: Both errors and non-error informational messages will be logged.

Debug: All errors and non-error informational messages, plus additional information about activity in the web client, will be logged. This setting is only recommended when troubleshooting a specific issue, as it can result in very large log files and performance impacts.

You can also choose to enable tracing for the web client, Repository Access, and WinHTTP. In general, tracing should only be performed to troubleshoot specific issues, usually at the request of your support contact.

It's quite likely the Log Level was set to "Debug". The others should still follow the ETW log config behavior, which by default caps log size at 1 or 10 MB with rollover.

0 0

Replies

replied on July 8

Chris, it sounds like the logging setting in the Web Client Configuration was changed at some point. Log into the Web Client Configuration page on the web server and go to the Diagnostics tab on the left. Make sure that the "Log Level" is set to "Critical" (default value). If it's different than Critical it could have been changed during troubleshooting an issue and never set back or someone just didn't understand what it should be set to.

For the files that are already in there, yes, they can be deleted.

3 0

replied on July 8

Good call, I'll check

0 0

SELECTED ANSWER

replied on July 8

From the docs (link is redirected to the admin guide home page for some reason right now but shouldn't hard to find in the table of contents):

https://doc.laserfiche.com/laserfiche.documentation/11/administration/en-us/Default.htm#../Subsystems/WAConfiguration/Content/Diagnostics.htm

Diagnostics

The Diagnostics page allows you to select a log level for the web client, as well as to turn tracing on and off in order to locate a specific problem.

The following log levels are available:

Critical: Only very important errors will be logged. This is the default setting.

Important: All errors will be logged.

Informational: Both errors and non-error informational messages will be logged.

Debug: All errors and non-error informational messages, plus additional information about activity in the web client, will be logged. This setting is only recommended when troubleshooting a specific issue, as it can result in very large log files and performance impacts.

You can also choose to enable tracing for the web client, Repository Access, and WinHTTP. In general, tracing should only be performed to troubleshoot specific issues, usually at the request of your support contact.

It's quite likely the Log Level was set to "Debug". The others should still follow the ETW log config behavior, which by default caps log size at 1 or 10 MB with rollover.

0 0

You are not allowed to follow up in this post.

Question

Question

Web Access Event Log Folder Size

Answer

Replies

Sign in to reply to this post.