Controlling the size of job logs

To control the amount of data stored in job run logs, you can perform the following configurations through the blasadmin utility:

  • Restrict target-related log messages to a certain severity (or log level). You configure the log level separately for each job type or group of job types.
  • Set the maximum number of messages to store in the log. Configuration of this log limit depends on the type of messages:
    • To limit target-related log messages, you configure the log limit separately for each job type or group of job types.
    • To limit messages with job run data, you configure a single limit for all job types.
  • Set the number of errors and warnings to store in the log (in addition to the limit specified by the number of messages in the log as specified in the previous item)
    • To set the additional number of target-related errors and warnings 
    • To set the additional number of errors and warnings for job run data

The job log settings that you configure through blasadmin are saved in the TrueSight Server Automation database and are applied to all Application Servers during job execution. You do not need to restart the Application Server after performing these tasks.

Before you begin

To help you decide on the changes that you want to make, you can first display the current settings (log level and log limit) for all job types. Run the show command on the jrelog component:show jrelog all

For general help on the jrelog component, you can use the help command — either help show jrelog or help set jrelog.

To restrict target-related log messages to a certain severity

  1. Start the Application Server Administration console, as described in Starting-the-Application-Server-Administration-console.

  2. To set the log level for target-related log messages from a specific job type or group of job types, enter the following set command:
    set jrelog LogLevel <severity> <job type group>

    For the variables in this command, you can specify the following values:

    • For severity, the following values are available (in ascending order of severity):
      AllInfo, ErrorsWarnings, and Errors
      All values are case-sensitive. The default is AllInfo.

    • For job type group, the following table lists all available job groups, along with the specific job types that are included in each group.

      Job group value

      Jobs included

      GenericJobs

      Daal Plugin Distribution Job, Daal Plugin Deregistration Job, Atrium Import Job, Component Discovery Job, Application Discovery Job, Publish Product Catalog Job, and Batch Job

      PatchingJobs

      Various types of jobs involved in Patching Analysis.

      ProvisioningJobs

      Provisioning Job

      SnapshotAuditJobs

      Snapshot Job, Audit Job

      NSHScriptJobs

      NSH Script Job

      ACLPushJobs

      ACL Push Job

      ComplianceSCAPJobs

      Compliance Job and SCAP Compliance Job

      VirtualJobs

      Various types of jobs involved in virtualization.

      DeployJobs

      Agent Installer Job, Deploy Job, and File Deploy Job

      USPJobs

      USP Job

    Example

    The following command restricts the target-related messages in the log for Snapshot Jobs and Audit Jobs to include only error messages:

    set jrelog LogLevel Errors SnapshotAuditJobs

  3. Repeat step 2 for any additional job types for which you want to set the log level.
  4. To validate that you have properly configured the log level for the various job types, you can run the show command to display current log levels:
    • For all job groups : show jrelog all(This displays both log levels and log limits.)
    • For just one job group: show jrelog LogLevel <job type group>

Note

In the case of Deploy Jobs, if a different logging level was set at the user level within the job (as described in Specifying-job-options), the user-level setting takes precedence over the level set by the blasadmin command.

To set a limit for the number of messages to store in the log

  1. Start the Application Server Administration console, as described in Starting-the-Application-Server-Administration-console.

  2. To set the maximum number of target-related log entries a specific job type or group of job types, enter the following set command:
    set jrelog LogLimit <log entries> <job type group>

    For the variables in this command, note the following guidelines:

    • For number of log entries, the default value is 1000 log entries.
    • For job type group, see the list of available job groups in the previous task.
    Example

    The following command limits the number of target-related messages in the log for Snapshot Jobs and Audit Jobs:

    set jrelog LogLimit 1250 SnapshotAuditJobs

  3. Repeat step 2 for any additional job types for which you want to set the log level.
  4. To set the maximum number of job run messages in the logs of all types of jobs, enter the following blasadmin command:
    set jrelog LogLimit <log entries> JobRun
    This limit is set for all job types, including all types of jobs in the list of available job groups, as well as several other types of jobs that do not require a target (Patch Catalog Jobs, Batch Jobs, Download Jobs, and Type-2 NSH Script Jobs). The default value for job run messages is 1000000 (one million) log entries.
  5. To validate that you have properly configured the log limit for the various job types, you can run the show command to display current log limits:
    • For all job groups and job run messages: show jrelog all(This displays both log limits and log levels.)
    • For just one job group: show jrelog LogLevel <job type group>
    • For job run messages: show jrelog LogLevel JobRun

To set the maximum number of errors and warnings per target

  1. Start the Application Server Administration console, as described in Starting-the-Application-Server-Administration-console.

  2. To set the maximum number of errors and warnings per target, enter the following set command:
    set jrelog PerTargetErrorWarningBufferLimit <NumberErrorsWarnings>

    For the variables in this command, note the following guidelines:

    • This number is in addition to the limit defined for each target by the LogLimit attribute. For example, if you have set the log limit for all job types to 1000 using the LogLimit attribute, and you have set the PerTargetErrorWarningBufferLimit attribute to 50, 1000 messages will be written to the log irrespective of their type, and 50 additional errors and warnings will be written to the log.
    • Valid values are 0 (unlimited number of errors and warnings) and a positive integer.
    • The default value is 50.
  3. To validate that you have properly configured the log limit per target, you can run the show command to display current log limits:
    show jrelog PerTargetErrorWarningBufferLimit

To set the maximum number of errors and warnings for a job run

  1. Start the Application Server Administration console, as described in Starting-the-Application-Server-Administration-console.

  2. To set the maximum number of errors and warnings for a job run, enter the following set command:
    set jrelog JobRunErrorWarningBufferLimit <NumberErrorsWarnings>

    For the variables in this command, note the following guidelines:

    • This number is in addition to the limit defined for a job run by the LogLimit attribute. For example, if you have set the log limit for all job runs to 1000 using the LogLimit attribute, and you have set the JobRunErrorWarningBufferLimit attribute to 50, 1000 messages will be written to the log irrespective of their type, and 50 additional errors and warnings will be written to the log.
    • Valid values are 0 (unlimited number of errors and warnings) and a positive integer.
    • The default value is 100.
  3. To validate that you have properly configured the log limit for a job run, you can run the show command to display current log limits:
    show jrelog JobRunErrorWarningBufferLimit

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*