Administration: Diagnostics module settings
To modify the default settings of the Diagnostics module, in Sitefinity backend, click Administration » Settings » Advanced » Diagnostics » Tools » DataAccessProfiler.
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 called Sitefinity.
To connect the Diagnostics module to a different that its default database, perform the following:
- In the backend, click Administration » Settings » Advanced » Diagnostics » Tools » DataAccessProfiler » Parameters » Create new.
- In Key, enter factory_connectionString
- 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 Connections strings in Administration » Settings » Advanced » Data » Connection strings.
Enable backend profiling
By default, only frontend operations are logged.
To enable the backend logging, perform the following:
- In the backend, click Administration » Settings » Advanced » Diagnostics » Tools » DataAccessProfiler » Parameters » Create new.
- In Key, enter enableBackendProfiling
- In Value, enter true
Log operations with no events
By default, operations that do not generate database queries are not logged.
To enable logging of operations with no queries, perform the following:
- In the backend, clickAdministration » Settings » Advanced » Diagnostics » Tools » DataAccessProfiler » Parameters » Create new.
- In Key, enter logOperationsWithNoEvents
- In Value, enter true