Administration: Diagnostics module settings

You can modify the following settings:

Database connection string for the Diagnostics module

By default, the Diagnostics module persists the data in a separate database that has its own connection string.

NOTE: You can see all of the project's connection strings in Administration » Settings » Advanced » Data » Connection strings. 
By default, the Diagnostics module connection string is called SitefinityDiagnosticsModule and the project's default database connection string is calledSitefinity.

To connect the Diagnostics module to other than its default database, perform the following:

1. In the backend, click Administration » Settings » Advanced » Diagnostics » Tools » DataAccessProfiler » Parameters » Create new.
2. In Key, enter factory_connectionString
3. In Value, enter the name of the connection string to the database that you want the Diagnostics module to use. For example, if you want the Diagnostics module to persist tracing information in the project's default database, enter Sitefinity

NOTE: You can enter only connection strings that are defined in the web.config file or in the Sitefinity CMS Connections strings in Administration» Settings » Advanced » Data » Connection strings.

Log operations with no events

By default, operations that do not generate database queries are not logged.

1. In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » DataAccessProfiler » Parameters » Create new.
2. In Key, enter logOperationsWithNoEvents
3. In Value, enter true

Log queries no matter the logging settings for its root operation

By default, logging of the query depends on logging of its root operation. For example if logging of certain type of HTTP requests is currently disabled, no queries will be logged for these requests as well.

To enable logging of the query no matter of its root operation settings, perform the following:

1. In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » DataAccessProfiler » Parameters
2. Find Key with name dependsOnRootOperation
3. In Value, enter false

Log backend requests

By default, HTTP requests are logged only for frontend pages and resources. So you can change the settings to enable logging of backend requests as well.

To enable logging of backend HTTP requests, perform the following:

1. In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » HttpRequestProfiler  » Parameters
2. Find Key with value logBackend
3. In Value, enter true

Log frontend requests

1. In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » HttpRequestProfiler » Parameters 
2. Find Key with value logFrontend
3. In Value, enter false

Log backend compilations

1. In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » CompilationsProfiler » Parameters
2. Find Key with value logBackend
3. In Value, enter true

Log frontend compilations

1. In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » CompilationsProfiler  » Parameters 
2. Find Key with value logFrontend
3. In Value, enter false

Log compilations no matter the logging settings for its root operation

To enable logging of the compilation no matter of its root operation settings, perform the following:

1. In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » CompilationsProfiler » Parameters
2. Find Key with name dependsOnRootOperation
3. In Value, enter false

Log backend compilations

You can restrict logging for certain background task types, by performing the following:

1. In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » BackgroundTasksProfiler » Parameters
2. Find Key with value skipSelectedTaskTypes
3. In Value, enter background tasks types that you no longer want to log and separate them with commas.