Help Contents

 

Updating the logging.config File

updated by Catch Admin (Apr 21, 2015)

In some instances it may be necessary to change the level of Enterprise Testers logging.  When troubleshooting issues, it may be necessary to to change the configuration settings of your log file. 

The following section provide instructions on how to make basic changes to the Enterprise Tester logging Config files. 

Log File Location

Log files by default are written to the Web\App_Data folder, in the installation folder – which can normally be found in C:\Program files\Catch Limited\Enterprise Tester\Web\App_data\ - the current days logs will be written to a file called “log.txt” and previous log files will be stored as “log.txtYYYY.MM.DD” where YYYY.MM.DD is the date at which the log was recorded.

Changing Error Logging from WARN to DEBUG

Enterprise Tester is configured to log only WARN (warning) messages by default to maximize system performance.  However, when troubleshooting an error, you may be asked by our support team to provide a more detailed log file.  To do this, you will need to change the logging status in your instance of Enterprise Tester, from WARN to DEBUG.

Open the logging.config file (normally found in Program Files\Catch Limited\Enterprise Tester\Web folder) using notepad or other text editor.

Scroll to the bottom and change the “Priority Value” from WARN to DEBUG as shown below:

<root>
    <priority value="DEBUG" />

Save and close the file. For the changes to the logging.config file to take effect you will need to Restart IIS or ’Recycle’ the Application Pool in IIS that Enterprise Tester is using.

As mentioned above, setting the logging level to ‘DEBUG’ will impact on the performance of Enterprise Tester – once you have captured the diagnostic information requested by Catch Limited you should always restore this value back to ’WARN’ to keep Enterprise Tester running at full speed (and avoid filling up your server with log files).