Hide menu Last updated: Dec 13 2016
Area: Episerver DXC Service Applies to versions: Not applicable


This topic describes general service monitoring, and how to enable debugging, logging and detailed error messages for troubleshooting solutions based on the Episerver Digital Experience Cloud Service

In this topic

Note: Debugging of code and functionality should always be done in the Integration environment. Debugging in the Preproduction/Production environments should only be done when absolutely needed. Contact Episerver to register a support ticket for remote debugging.

Checking service status

Visit the Microsoft Azure Status dashboard for general service operation information. See the Episerver service dashboard for Episerver-specific operational status.


Accessing Azure Portal

Contact Episerver to get access to your DXC Service-specific resources in the Azure portal, so that you can monitor and troubleshoot your solutions. When logged in, the Azure portal will display information as in the example below.

Enabling debugging

You need to enable debugging in both the Azure Portal and Visual Studio. Following the steps below, you first allow remote debugging in the Azure portal, and then attach to the correct process in Visual Studio.

1. In the Azure portal: 

  1. Select App Services for the Integration environment.
  2. Go to Application settings and set Remote debugging to On.

2. In Visual Studio: 

  1. Go to Tools and select Attach to process.
  2. Under Available Processes, select the correct process, which can be found under the publishUrl in the publish profile settings file. Example format: epvscms3p60ginte.azurewebsites.net.  Use the credentials provided in the publish profile settings file when prompted for access.
  3. After selecting the process, click Attach.
  4. Debug your solution as you normally would in Visual Studio.

Activating logging

Episerver supports writing to the diagnostics log using BLOB storage. See Logging into .Net Diagnostics Trace for more details on how this works.

Follow these steps to activate the logging.

  1. Select App Services for the integration environment, and go to Diagnostics log. 
  2. Set the Application Logging (Blob) to On, select desired Level of verbosity, and select a storage account and container under Storage Settings.
  3. Click Save when done.

Note: The Web App will restart when activating the logging.

Accessing log information

Access the website log files in the integration environment using any of the methods described below.

Download log files

Use the download/FTP options available in Azure Portal under Diagnostics logs for the environment.

Kudu services tool

The Kudu services tool is available with your access to the Azure Portal and Digital Experience Cloud.

  • Add "scm" to the environment URL, for example https://epvscms3p60ginte.scm.azurewebsites.net/, to display information in Episerver logs available under site/wwwroot/appdata and logfiles/eventlog.

Detailed error messages

You might find it useful to turn on detailed ASP.NET error messages in web.config for your solution in the Integration environment, as an additional tool when debugging.