Logging Templates

You can use templates for defining the logged items and their logging levels. You can use templates as such, or edit the settings in the later steps of the wizard.

In the Example and Templates folder that is delivered with the installation packages, there are the following templates. You can also make your own ones using them as models only.

Note:

If the Hide Sensitive Information is not in use (DebugSecure has the value 0), sensitive data, such as user names or phone numbers, may be available in log files. In each troubleshooting template where this setting is turned off, there is a note in the description about the issue. Always turn Hide Sensitive Information on (use value 1 for DebugSecure) after troubleshooting.

To see the exact logging settings, view the files, or select the template in Logging Wizard, and see the results in step 4.

Table 1. Default Logging Templates
File	Template	Usage
LoggingTemplate_Defaults.xml	Back to Defaults	Return to the normal recommended logging level where sensitive data is hidden and logging levels are set to Warning.
LoggingTemplate_Troubleshooting.xml	Audio and RTP	Issues with audio streams, sound quality, recording and signaling destinations
	Authentication	Issues when opening user interfaces, such as CDT or Online Monitoring.
	Contact Routing	Issues in contact allocation and routing. NOTE: Sensitive data may be available in log files.
	ECF	Issues in Embedded Communication Framework (ECF) chats and tasks. Additionally, Tomcat logs may be required, see ECF Developer Guide. NOTE: Sensitive data may be available in log files.
	Import and Export	Issues in import and export functions.
	Integration Interfaces	Issues in integrated systems. For optimal performance, you may deselect interfaces which are not affected in step 2 Select Items.
	Network	Issues with network connections or performance. May produce huge log files, monitor CPU load and available hard disk space. NOTE: Sensitive data may be available in log files.
	Outbound Campaign	Issues in Outbound campaign. Additionally, client-side log (such as CDT) is needed with the log level 5. NOTE: Sensitive data may be available in log files.
	Restful Interfaces	Issues in Restful Configuration Interface (RCI), Restful Monitoring Interface (RMI), Task Managing Interface (TMI), License Reporting Interface (LRI), or SAP Service Cloud (C4C)Interface.
	Tracing Agent Actions	Issues related to user session, contact, and profile related issues. Additionally, client-side log (such as CDT) is needed with log level 5. NOTE: Sensitive data may be available in log files.