Purpose of DEBUG, TRACE, or VERBOSE Logging
When trying to troubleshoot a problem, it can often be helpful to increase the logging level of the affected component. This should be done with great care, because the amount of information logged is substantially larger. Logging should be returned to a normal level after troubleshooting. Do not leave DEBUG, TRACE, or VERBOSE logging enabled, because that will result in Riva creating a lot of large log files and reduce sync performance.
DEBUG, TRACE, or VERBOSE logging is enabled by creating or updating a .config file for the service executable or application that you want to enable that kind of logging for:
To modify the logging level, add the following app.setting to the applicable .config file in the Riva\Application\Base or Riva\Application\<version number> folder (see How to create an App.Setting file to enable advanced options):
<add key="LoggingLevel" value="LEVEL" /> where "LEVEL" indicates the logging level, for example "DEBUG":
<add key="LoggingLevel" value="DEBUG" /> (To enable DEBUG logging mode.)
Example that can be copied and pasted into a blank file:
<?xml version="1.0" encoding="utf-8"?>
<add key="LoggingLevel" value="DEBUG" />
Based on the above component that you want to modify, create a text file in which the advanced configurations are entered. This file needs to be saved to the latest Riva application folder:
For an overview of the logging levels, see Logging levels in the article How to manage Riva On-Premise logging.
IMPORTANT! Save the file, and restart the component. To restart the component, do any of the following:
To return logging levels to a normal level:
Riva upgrades preserve .CONFIG files
The Riva upgrade process copies the .CONFIG files to the latest version folder.
Riva 2.4.42 or higher.
Note: The following procedure applies only to the 32-bit Riva sync service, the standard installed service. It does not apply the option for the Riva Manager application or for the 64-bit service, which requires the manual procedure - Config File.
To enable the logging level in the Riva Manager application: