The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco Prime Collaboration Assurance supports the following log levels:
Debug—Helps you to debug the application.
Information—Indicates the progress of the application.
Error—Indicates that the application can still continue to run.
Fatal—Indicates critical error. This level is not listed for all modules.
You cannot disable logging. However, you can:
The log level settings can be changed from the Log Management page ( ). The log files are also included in the backup file.
Caution | You should not change the log level settings without assistance from the Cisco Technical Assistance Center (TAC) team. |
This feature provides information to resolve the network issues quickly by enabling you to download log files so that you can share the required logs.
Prerequisites - You must set the log level to Debug for the module you want to collect logs for. For more information on how to set the log level to debug, see the earlier section.
Click the Download Log button to download the logs. You are prompted to download a .tar file. The file name shows the username of the user who generated the log file, date and time-stamp (according to the Cisco Prime Collaboration server time) to indicate when the (.tar) file was generated. You need to open or untar this file to view the log file with the same name. The log file is a compressed file, which can be opened using any uncompression utility such as 7-Zip.