Skip to main content
Skip table of contents

Enable Debug Logging

This page shows you how to enable and disable debug logging. This is useful for troubleshooting issues as it will provide detailed information on what is happening behind the scenes.

It is recommended to set back to "Information" when the debugging is completed as "Debug" will create larger log files and more load on the server. 

Steps to enable debugging

  1. Navigate to the EzeScan WebApps home page using a supported browser.

  2. Login as an Admin user.

  3. In the top right click the Admin link to open the Admin Panel.

  4. On the left menu click the Logs link.

  5. Change the Logging Level to Information.


  6. In the top right confirm you see a success notification.

Steps to disable debugging

  1. Navigate to the EzeScan WebApps home page using a supported browser.

  2. Login as an Admin user.

  3. In the top right click the Admin link to open the Admin Panel.

  4. On the left menu click the Logs link.

  5. Change the Logging Level to Information.


  6. In the top right confirm you see a success notification.

Steps to enable debug logging when unable to access the admin panel

  1. In the appsettings.json file find the section that says

    JS
     "_Serilog":{
          "MinimumLevel":"Information"
       },
  2. Remove the underscore at the start and then change the value of Information to Debug.

    JS
     "Serilog":{
          "MinimumLevel":"Debug"
       },
  3. Save the appsettings.json file.

  4. Stop and start the IIS Application Pool.

Steps to enable verbose logging

  1. In the appsettings.json file find the section that says:

    JS
     "_Serilog":{
          "MinimumLevel":"Information"
       },
  2. Remove the underscore at the start and then change the value of Information to Verbose.

    JS
     "Serilog":{
          "MinimumLevel":"Verbose"
       },
  3. Save the appsettings.json file.

  4. Stop and start the IIS Application Pool.



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.