Previous Topic: Log Files Controlled by Each Log4j.xml FileNext Topic: Configure Rollover Settings for Selected Log Files

Maintenance › How to Maintain Log Files › Set the Log Level of a Service

Set the Log Level of a Service

You can change the log level of a CA Service Catalog service for various reasons. For example, you can set the log level to a higher level to investigate a problem or question. After you are finished investigating, you can reduce the log level for efficiency reasons.

Follow these steps:

  1. Open the log4j.xml file of the CA Service Catalog service whose logging level you want to set.
  2. Find the following section: 
    <root>

        <priority value="log-level" />
    <appender-ref ref="accounting" />
    <!-- appender-ref ref="console" /-->

    </root>
  3. Specify one of the following for the log-level:
    Fatal

    Logs only errors that shut down a CA Service Catalog component. This log level typically provides the least detail. It also requires the least amount of disk space for rolled-over log files and therefore the least maintenance.

    Error

    Logs all of the messages from the previous level, plus failed actions. For example, a user submitted a request, but the system did not present the request for approval.

    Warn

    Logs all of the messages from the previous levels, plus warning messages; for example, a user creates a service with a nonunique name.

    Informational

    Logs all of the messages from the previous levels, plus messages that are informational only. An example is the total number of open database connections.

    Debug

    Logs all of the messages from the previous levels, plus more detailed messages intended to help troubleshoot a problem. For example, debug messages can include every step of a multiple-step process.

    Trace

    Logs every action and displays the final XML. This level includes all of the messages from the previous levels, plus many more.

    This log level typically provides the most detail. It also requires the most amount of disk space for rolled-over log files and therefore the most maintenance.

  4. Save and close the log4j.xml file.
  5. Recycle the CA Service Catalog service whose logging level you updated.

Important! Do not make any other changes to any log4j file, unless instruction to do so by CA Technical Support!