Skip to main content

How to define a rotation strategy for logs in Talend Identity and Access Management

Logs produced by Talend Identity and Access Management could grow huge in size and amount. You may define a log rotation strategy to automatically archive or delete useless logs.
Different types of logs are stored in the $IAM_HOME/apache-tomcat/logs folder.
  • catalina.out: this is the global log, recording global events on the Tomcat server.
  • Tomcat server logs:
    • catalina.<date>.log
    • localhost.<date>.log
    • manager.<date>.log
    • host-manager.<date>.log
    According to the configuration file of these logs, $IAM_HOME/apache-tomcat/conf/logging.properties, only the logs of the last 90 days are kept.
  • Access logs: localhost_access_log.txt
  • Spring Boot applications:
    • idp.log
    • oidc.log
    • scim.log
    • sts.log
    • audit.log
    • sts-tac.log
    • audit-tac.log
  • Syncope:
    • core-connid.log
    • core.log
    • core-persistence.log
    • core-rest.log
    • console.log
    • enduser.log

The catalina.out log, the Tomcat server logs and the access logs are all standard Tomcat logs, independent of the Talend products. If you need to define a rotation strategy for these logs, see the third-party documentation about these logs, for example, logrotate for the catalina.out log or the access logs.

The following sections explain how to define a log rotation strategy for the Spring Boot logs and the Syncope logs.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!