Several performance-related settings for Reporting Dashboards are available in the Configuration module. See Changing Reporting Dashboards Settings.
Error messages for Reporting Dashboards are logged to the Error tab of the Diagnostics Console. Troubleshooting information is logged to the Diagnostics Console when the following settings are enabled:
-
General logging is enabled with the reportServiceTraceLevel setting or the hylandTracing setting in the Web.config file of the Application Server.
-
Session-based logging is enabled with the reportServiceSessionTraceLevel setting in the Unity Client configuration file.
The following element must be added to the appSettings element of the Web.config file for the Application Server:
-
<add key="reportServiceTraceLevel" value="0"/>
Elements for the Unity Client configuration file must be added under the appSettings element:
-
<add key="reportServiceSessionTraceLevel" value="0"/>
The possible values for the reportServiceTraceLevel, reportServiceSessionTraceLevel, and hylandTracing settings are:
|
Value |
Tracing Type |
Description |
|---|---|---|
|
0 |
Trace |
Most verbose logs. May contain sensitive application data and should never be used in a production environment. |
|
1 |
Debug |
Logs that are used for interactive investigation during development. |
|
2 |
Information |
Logs that track the general flow of the application. |
|
3 |
Warning |
Logs that highlight an abnormal or unexpected event in the application flow. |
|
4 |
Error |
Logs that highlight when the current flow of execution is stopped due to a failure. |
|
5 |
Critical |
Logs that describe an unrecoverable application or system crash, or a catastrophic failure that requires immediate attention. |
|
6 |
None |
Use this setting to limit logs as much as possible. |
If the reportServiceTraceLevel and reportServiceSessionTraceLevel values are not supplied, the settings for logging routes in the App Server Web.config are used.
For details on enabling these settings, see the corresponding module reference guides or contact your first line of support. For details on using the Diagnostics Console, see the Diagnostics Service and Diagnostics Console module reference guide.