The logs are important in determining the root cause and capture common errors in Clarity. There can be too much logging, which clutters or overwrites errors that matter to a particular issue. On the other hand, there can be too little logging. Here are the best practices on setting the Clarity logging levels to make sure there is enough logging in the event there is an error or exception.
Note: If an additional component is needed that is not listed in the 'Name' dropdown menu:
Replace the logger.xml file:
Important: Once you reproduce the issue and collect logs for Support, the DEBUG logging must be removed. DEBUG logging should only be used temporarily for collecting log evidence for an issue and not continuously
The exact categories have to be requested to be set by Broadcom Clarity Support