Clarity PPM: How Should Logging Levels Be Set?

Document ID : KB000009555
Last Modified Date : 06/06/2018
Show Technical Document Details

The logs are important in determining the root cause and capture common errors in CA PPM.
Often times, there is too much logging which clutters or overwrites errors that matter to a particular issue. On the other hand, there is too little logging. 
How should the logging levels be set?
When should it be reset to default?



Using an administrative login,

1. Go to the CSA via URL: http://<server>:8090

   click servername > Logs > Edit Configuration

2. For each server, the following Category components should not be to INFO,DEBUG,TRACE. Instead, it should be set to resemble the following:


Note: If additional component is needed that is not listed in the 'Name' dropdown menu,
Go to the Categories section:
a. Click the button(Add Category) 
b. Add the component in the 'Other Name' column.
c. Click Save.
d. Do this for each additional component.

3. Is there a checkmark on 'Detect Log Configuration Changes Automatically'?
If checked, service(s) do not have to be restarted.
If it is not checked, service(s) have to be restarted.

Additional Information:

If the logging does not appear to be working such as the app,bg,or system logs not updating, this is corrupted logging.
The following can be performed to reset the logging mechanism:

Go to each server that has PPM installed.
-Go to the CLARITY_HOME/.setup/templates/config/
-Copy the original copy of the file: logger.xml
-Place this copy in the CLARITY_HOME/config folder.

No restart of Clarity services required.