How to use "Remoting Log"


What is "Remoting Log"

Remoting Log or so-called Data Transfer Log is a powerful tool that can direct us to the source of the problem when investigating performance issues.

It is used during investigations related to:

  •  slow screen forms
  •  slow loading of a drop-down list
  •  (sometimes) slow loading of a Navigator. Exec Stats is the more reliable tool when it comes to loading navigators, but the Remoting Log can still guide us if the problem is network related.
  •  a suspected network problem, which causes a general feeling of slowness when performing a particular operations


How to use it

* If you are using the Desktop Client: 

1. Go to File/Settings


2. Click Show Remoting Log – this opens the Data Transfer Log form


3. Execute ONLY the slow operation

4. Click Refresh of the Data Transfer Log


5. Click Print and Export to PDF


6. Attach the PDF to the ticket


Analyze the data

  • Always try to compare with baseline data.

This means that if there is a particular time, another location, or another definition of the same type in which the problem does not appear  - create a log for it.

Then compare both logs, the one with the problem recreation and the other which represents the normal work of the same operation.

  •  Compare the summarized values of "Total, ms", "Network, ms" and "Server, ms".

Notice whether a significantly large proportion of the total time is taken up by the total of  "Network, ms" or  "Network, ms".

This may indicate the suspected location of the delay - the network or the server.

  •  Sort ascending by "Total, ms", no grouping, and look at the top 10 times.

 Compare values of "Network, ms" and "Server, ms" again to check if one takes a significantly large proportion of the "Total, ms".

  •  Look for large "Network, ms" values.

Generally, the Desktop Client makes a lot of calls whose size (Request, B + Response, B) is between 1000 and 2000 bytes. Ideally, these should have "Network, ms" in the range of 5-50 ms.

  •  Notice whether most such requests have similar "Network, ms" times.

If the times vary a lot, like going to more than 100, there might be a network problem.

  •  Look for gaps between the request times.

Unusual gaps between the End time of the previous request and the Start time of the next one means that the client lags when making the following request. It is advisable to have the data reviewed and analyzed by our team.

  •  Look for too many repetitive operations of the same kind.

For example, if we have a document with 100 lines and you see 500 requests for a bonus program recalculation, then it is advisable to have the data reviewed and analyzed by our team.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk