Search
Welcome to M-Files Empower – our new support experience. We'd love to hear what you think!Give feedback
Home/Support and troubleshooting/Troubleshooting/Gathering logs

Ground Link in M-Files - Enabling Trace Logging

Last updated on 28 June 2021

Admin
Ground Link
Summary

Only System administrators can enable trace logging. The Ground Link tracing settings are not visible to vault administrators. Trace logging can be enabled on both the cloud vault and the Ground Link proxy, but different information is logged on the different ends - no trace messages are sent over the Ground Link connection. Customers can therefore only enable tracing on their proxies, not in their cloud vault.

Enabling tracing in cloud

In cloud environment go to the corresponding vault > Advanced Vault Settings > External Repositories > Ground Link. In Configuration tab, there is Tracing section. Select Enabled = Yes.

Trace Level

Defines the severity level of the trace messages that are logged. All messages with a level less than or equal to the selected level will be logged. For example, selecting "3. Information" results in recording entries for the levels "3. Information", "2. Warning", and "1. Error".
  1. Error
  2. Warning
  3. Information
  4. Verbose
Note, that verbose tracing should be enabled only temporarily as it can result in very large log files and performance issues.

Categories

Specifies the categories of the trace messages that are logged in addition to the default category.
Remote Calls - Information about remote calls made over Ground Link is traced. The information includes remote method names, call duration, and timeouts.
gRPC - Information about gRPC connections managed by Ground Link is traced.
Remote Message Size - Information about the size and message splitting of remote messages sent over Ground Link is traced.
image.png

Enabling tracing in on-premises (usually Proxy)

In on-premises the location is the same.
image.png
 

Trace location

Ground Link uses the same temporary file location received from MFServer that connector trace logging has used.
Typically, the base path is something like the following:
C:\Program Files\M-Files\Server Vaults\<VaultName>\FileData\Temp_<GUID>\<n>
The Ground Link proxy log has the path (relative to the base path): <AppGuid>\GroundLinkProxyTrace.log
The cloud vault Ground Link log has the following path (relative to the base path). Note that the GUID is fixed. It is the application GUID.
{225cc467-c7e3-4dd1-b06b-b62f84048c8b}\GroundLinkTrace.log
An example of the full path:
C:\Resources\Directory\4ea3e28fd6474ea4b21630dc322ad35b.MFilesServerAzure.Metadata\a14468d1-6d18-43de-8706-1882aeb5d4f7\FileData\Temp\1\{225cc467-c7e3-4dd1-b06b-b62f84048c8b}

 

Still need help?