You are viewing limited content. For full access, please sign in.

Question

Question

trace logs information

Laserfiche
Updated June 29, 2016
asked on June 28, 2016

Is there any white papers or description on the LF Client trace logs?

We are currently collecting them to try to analyze them and improve performance.

Ideally we want to group the different actions or methods called in the logs.

Thank you

Gian

 

0 0

Answer

SELECTED ANSWER
replied on June 28, 2016 • Show version history

The number in brackets is the thread ID. 04572 is a background thread that acts independently from user actions ("Pinging" the idle connection to keep it alive).

The main way you would use the logs to find any performance issues in Laserfiche is to find the time between LFSession::SendRequest and the following LFSession::ProcessResponse with the same thread id. This represents how long a request takes to complete. So in this case you can see that it the UNLOCK request completed immediately (15:35:04.711 to 15:35:04.711)

1 0

Replies

replied on June 28, 2016

Those logs are not documented because they are meant to be analyzed by Laserfiche engineers. Is there a specific performance issue you are trying to resolve?

0 0
View 2 previous replies
replied on June 28, 2016

Hi Robert,

We have some performance issues in some implementations but we don't know if it is Laserfiche yet. We are just trying to collect as much data as possible.

Ideally we want to group the log entries by action.
In the LFSO92.dll log. Is the number between brackets a group of the action?

For example:

15:32:22.987 [03932] ILFObjectImpl::~ILFObjectImpl
15:32:22.987 [03932] CLFLinkType::~CLFLinkType
15:32:22.987 [03932] ILFObjectImpl::~ILFObjectImpl
15:32:22.987 [03932] CLFLinkType::~CLFLinkType
15:32:22.987 [03932] ILFObjectImpl::~ILFObjectImpl
15:32:44.003 [04572] PingConnection
15:34:44.024 [04572] PingConnection
15:35:04.711 [03932] ILFEntryImpl::Dispose
15:35:04.711 [03932]  CLFLock::Dispose
15:35:04.711 [03932]   LFSession::SendRequest (UNLOCK /+LF/entry/4497621)
15:35:04.711 [03932]    LFSession::ProcessResponse
15:35:04.711 [03932]     ProcessResponseHeaders
15:35:04.727 [03932] ILFEntryImpl::Dispose
15:35:04.727 [03932]  CLFLock::Dispose
15:35:04.727 [03932] ILFEntryImpl::Dispose

Is in this case 03932 one action and 04572 another?

 

Thank you
Gian

0 0
SELECTED ANSWER
replied on June 28, 2016 • Show version history

The number in brackets is the thread ID. 04572 is a background thread that acts independently from user actions ("Pinging" the idle connection to keep it alive).

The main way you would use the logs to find any performance issues in Laserfiche is to find the time between LFSession::SendRequest and the following LFSession::ProcessResponse with the same thread id. This represents how long a request takes to complete. So in this case you can see that it the UNLOCK request completed immediately (15:35:04.711 to 15:35:04.711)

1 0
replied on June 28, 2016

great, thats what I need.

Thank you!

0 0
replied on June 29, 2016

Another question,

Do you have a logparser tool that can be shared or any other way of processing the logs?
It will save us from creating a new one.

 

Thank you
Gian

0 0
replied on June 29, 2016

I use a perl script that reports the time taken by each request, it is attached. At the top you give it the folder containing the logs.

lfsoResponseTimes.pl.txt (2.84 KB)
Download
1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...