Aurora_Gaimon

CA PPM: Logs Housekeeping

Blog Post created by Aurora_Gaimon Employee on Dec 21, 2016

Finally, I've decided to talk about logs too . I don't get question so often to be honest, but I'm pretty sure many CA PPM administrators will feel curious what the best practices / recommendations are.

 

Based on my experience, see recommendations for basic worth logs:

 

 

*access-log:

.app-access-log*

.nsa-access-log*

 

Type: Log access to web application.

They are also used to create logging or performance custom reports, analysis or troubleshooting.
For auditing APP activity it's better to relay on "Audit Trail".

 

Default: Roll over daily into unique filenames containing each date.

 

How to change settings:

If your web-server is "Tomcat":

  •  Do not try to customize files under your Tomcat folder structure.
  • Those logs are used by job "Tomcat access log import/analyze". Any alteration could make the job fail.
  • It will be a not supported modification by your own risk.

If your web-server is "other J2EE server":

  • Review with your web-server administrator.

 

Housekeeping: Manually or via system script move to another location for archiving or delete logs older than "N" days. My personal experience is majority of organization don't have the need to keep them more than 90 days.

 


*sytem.log:

.app-system.log
.beacon-system.log
.bg-system.log
.nsa-system.log

 

Type: system.log files is the "console" output of the service

 

Default: It appends continuously.

 

How to change settings :TEC536205 

 

Housekeeping:

  • They don't grow too fast.  
  • Change rollover frequency as described in TEC536205.

 

 

.admin.log:

 

Type: Similar to system.log file except it represents the console activity of the prompt (install, upgrade, service stops and starts, etc.). 

 

Default: It appends continuously. 

 

How to change settings: You cannot change it.

 

Housekeeping:

  • It does not grow fast.
  • Manually purge/delete if needed. I've never seen the need to really do any housekeeping on this one. Just when troubleshooting (ie: upgrades), we may delete file to remove all previous history.

 

 

*ca.log:

.nsa-ca.log
.app-ca.log
.bg-ca.log


Type: It will log the activity for each service.

 

Default:

  • Default value for "MaxFileSize" is 5MB. 
  • Default value for "MaxBackupIndex" is 3 files.

 

snipped from "logger.xml":

[...]
<appender class="org.apache.log4j.RollingFileAppender" name="STDOUT">
<param name="File" value="../logs/ca.log"/>
<param name="Append" value="true"/>
<param name="MaxFileSize" value="5MB"/>
<param name="MaxBackupIndex" value="3"/>
<layout class="com.niku.union.log.NikuLayout">
<param name="ConversionPattern" value="%-5p %d{ISO8601} [%t] %c{2} (%u:%s:%a) %m\r\n"/>
</layout>
</appender>
[...]

 

How to change settings: TEC506120

 

Housekeeping:

  • They grow fast and quickly. 
  • My personal recommendation as a good practice is "leave default" unless you need to troubleshoot issues or other special needs. In that case:
    • MaxBackupIndex: do not increase it more then 15 MB.
    • MaxBackupIndex: do not increase it more then 10 files.

 

 

 

That’s all. Thanks for reading until here. Did you like it? Please, don’t be shy and share it.

Outcomes