Monitoring Project Server Health

To keep track of the Maestro performance and problems, log files are created during Maestro runtime.

These log files can be used for system administration, security, and debugging purposes. By default, logs are rolled by date.

  • project-server.log - This file contains all start-up information and activity logs of Maestro Project Server.
  • maestro.log - This file logs all the activities of Maestro Project Server from the moment it started until the moment it was stopped.

To view the Maestro log files navigate to [maestro_home]/projectserver/logs. You may use a text editor to view the log files.

Logging Rolled By Date

To roll maestro.log by date, edit the file [maestro_home]/projectserver/conf/wrapper.conf and set the following properties:

  • wrapper.logfile=%PROJECTSERVER_BASE%/logs/maestro.YYYYMMDD.log
  • wrapper.logfile.rollmode=DATE

To roll project-server.log by date, edit the file [maestro_home]/projectserver/apps/root/WEB-INF/classes/log4j.xml

  • Set the appender's class to org.apache.log4j.DailyRollingFileAppender
  • Set the appender's datePattern property - The DatePattern takes a string in the same format as expected by SimpleDateFormat. This options determines the rollover schedule.
  • Sample configuration of log4j.xml that is rolled by date
    <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
  <appender name="rolling" class="org.apache.log4j.DailyRollingFileAppender">
    <param name="file" value="${appserver.base}/logs/project-server.log" />
    <param name="append" value="true" />
    <param name="datePattern" value="'.'yyyy-MM-dd" />
    <layout class="org.apache.log4j.PatternLayout">
      <param name="ConversionPattern" value="%d [%t] %-5p %c %x - %m%n" />
    </layout>
  </appender>
</log4j:configuration>

Logging Rolled By Size

To roll maestro.log by size, edit the file [maestro_home]/projectserver/conf/wrapper.conf and set the following properties:

  • wrapper.logfile=%PROJECTSERVER_BASE%/logs/maestro.log
  • wrapper.logfile.rollmode=SIZE
  • wrapper.logfile.maxsize=5mb

To roll project-server.log by size, edit the file [maestro_home]/projectserver/apps/root/WEB-INF/classes/log4j.xml

  • Set the appender's class to org.apache.log4j.RollingFileAppender
  • Set the appender's maxFileSize - The maximum size that the output file is allowed to reach before being rolled over to backup files. You can specify the value with the suffixes "KB", "MB" or "GB" so that the integer is interpreted being expressed respectively in kilobytes, megabytes or gigabytes.
  • Set the appender's maxBackupSize - This determines how many backup files are kept before the oldest is erased. This takes a positive integer value. If set to 0, then there will be no backup files and the log file will be truncated when it reaches MaxFileSize.
  • Sample configuration of log4j.xml that is rolled by size
    <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
  <appender name="rolling" class="org.apache.log4j.RollingFileAppender">
    <param name="file" value="${appserver.base}/logs/project-server.log" />
    <param name="append" value="true" />
    <param name="maxFileSize" value="5MB" />
    <param name="maxBackupIndex" value="5" />
    <layout class="org.apache.slf4j.PatternLayout">
      <param name="ConversionPattern" value="%d [%t] %-5p %c %x - %m%n" />
    </layout>
</log4j:configuration>