Compliance results

The results of Compliance Jobs show how components satisfy or fail to satisfy the compliance rules established in a component template. Compliance Job results also show the outcome of any auto-remediation.

After running a Compliance Job, you can display job results in a tab in the content editor. The tab contains a hierarchical tree that shows results for each run of the job. The following nodes under each job run present different views of the results:

  • Remediation View — Shows the result of the remediation job launched automatically by this Compliance Job run.
  • Rules View – Organizes information according to the compliance rules defined for each component template.
  • Server View — Organizes information according to the components found on each server.

Selecting nodes below the Rules View or Server View nodes displays additional details about a portion of the hierarchical tree.

The possible compliance statuses of compliance rules are described in Compliance-statuses-of-compliance-rules. To view Compliance Job results, any of the following procedures are possible:

To use Compliance Job results, any of the following procedures are possible:

After you display Compliance Job results, you can export some or all of the results of the Compliance Job (see Exporting-compliance-results).

Note

  • The Application Server can be configured to set a maximum number of results that are displayed for any failed condition in a compliance rule. If you are running a Compliance Job that examines large numbers of component parts that fail a compliance rule, you can potentially tax your system resources, particularly disk space. If results for a Compliance Job exceed the limits defined for the Application Server, the job run icon shows a warning and the job log includes a message saying that job results are truncated.
    By default the maximum number of results for a failed condition is set to 100. To change this maximum number, use the Application Server Administration console (that is, the blasadmin utility) to set another value for the ComplianceResultMaxNumberOfAssets option. For more information, see Managing-the-Application-Server. 
  • For any target servers that were included in an exclusion window when the job was run, job run results are impacted in the following ways:
    • The job run fails and the job log contains an error message that notifies you that the server was configured to be in an exclusion window. In addition, the start time of the job run cannot be obtained and is not displayed.
    • If the Run auto-discovery option was selected in the General panel of the job, automatic component discovery is also blocked. If no components are available (from a previous discovery) for the server, the server does not appear in job results. A warning message in the job log notifies you that the server was configured to be in an exclusion window.
  • A compliance job that is run without any targets assigned fails with the following warning message:
    "Didn't find any target servers for <jobname>."
    The auto-discovery setting changes does not affect this behavior. You can change this behavior by using the ComplianceJobRunsWithNoTargets blasadmin command. For more information, see Enabling compliance or snapshot jobs to run without targets.

 

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