Important

   

Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Live Reporting dashboard Patch reports

This topic describes the reports that available when you click the Patch tab on the Live Reporting dashboard. The topic includes the following sections:

Overview

The Patch tab displays complete information about patch management in three distinct views: the current state of the environment, a historical view, and a cohort analysis.

For example, the BladeLogic administrator can use Live Reporting to answer the following questions:

  • How many servers are enrolled, patched, or deployed? 
  • How many patch jobs failed on a given day? 
  • How many Windows servers are patch-compliant during a given week? 
  • What type of operating systems are running on the enrolled servers?
  • When was the last time a particular catalog updated successfully?
  • How many individual servers have been patched?
  • How many individual servers have been analyzed?
  • What are the common reasons for failure in patch analysis?
  • What are the errors for remediation jobs not executed successfully?

Reviewing a summary of enrolled, patched, and deployed servers

The high-level reports allow the patch administrator to view at a glance the current state of the managed environment, relative to compliance status.

The following table provides a description for each of the items in the view.

If you hover above the report, the share and edit icons are displayed in the upper-right corner of the view. (The options are described in Troubleshooting the Live Reporting dashboard.)

ReportDescriptionExample screen
Enrolled servers summary

This report displays the total number of servers you are managing in your environment, as well as the distribution by OS type.

The report also lists the number of servers that are currently not accessible (for example, the agent on the server is down, or is in a maintenance window).

Patching servers summary

This report shows the total number of servers currently involved in a patching activity (analysis or deploy). It also shows the distribution of those servers by OS type.

Analyzed servers summary

(Non-distinct server count if multiple catalogs selected)

This report identifies:

  • The total number of servers targeted for analysis. Note that each server is counted once, even if it was analyzed against multiple patch catalogs.
  • The number of servers that were not analyzed (for example, if the server was inaccessible for any reason)
  • The number of compliant servers (zero missing patches)
  • The number of non-compliant servers (one or more missing patches)
  • The Others column refers to the number of servers that were paused, due to a maintenance window being in effect; in this case there are patches that still need to be deployed

Note: With the Non-distinct server count, each server is counted once, even if it you selected multiple patch catalogs in the filter options.

Deployed servers summary (Commit phase only)

This report identifies:

  • The number of servers targeted for remediation
  • The number of servers for which remediation failed
  • The number of servers that were successfully patched
  • The number of servers that were skipped because the maintenance window was not available, or there was an exclusion window in effect
  • The Others column refers to the number of servers that were paused, due to a maintenance window being in effect; in this case there are patches that still need to be deployed

Note: This report is only for the Commit phase of the Patching Job, which is the final phase of the deployment.

Analysis run progress status

(Non-distinct server count if multiple catalogs selected)

This report displays, in chart form, the overall progress of the analysis (indicating how many failed, completed, or completed with warnings). This report is useful if you encounter a large number of analysis failures.

Note: With the Non-distinct server count, each server is counted once, even if it you selected multiple patch catalogs in the filter options.

If you hover above the report, the view toggle icon is displayed (along with the standard share and edit icons) in the upper-right corner of the view. The toggle icon enables you to switch between the chart version of the report, and the line graph version of the report. (The options are described in Troubleshooting the Live Reporting dashboard.)

If you click on any of the individual bars in the chart, you can open the drill down reports which contain additional information, as shown in the first figure on the right.

 

Clicking on the individual bar representing failed runs displays the Analysis Failure reasons Summary Report and the Analysis Details report.

The first figure shows a section of the Analysis Failure Reasons Summary Report, which provides the error codes for the failed runs, and descriptions of the errors, when available.

Clicking on an error code displays the Analysis Failure Reasons Details Report, which provides further details on the error as well as possible remediation steps.

Deploy run progress status (Commit phase only)

This report also uses charts to show the overall progress of the patch deployment.

The report displays four status states:

  • The number of runs that failed, where there was an issue with the server or the patch was not installed
  • The number of runs that completed, where the missing patch or patches were installed successfully
  • The number of runs that were paused, because a maintenance window or an exclusion in effect; in this case there are patches that still need to be deployed
  • The number of runs that were skipped because the maintenance window was not available, or there was an exclusion window in effect

If you hover above the report, the view toggle icon is displayed (along with the standard share and edit icons) in the upper-right corner of the view. The toggle icon enables you to switch between the chart version of the report, and the line graph version of the report. (The options are described in Troubleshooting the Live Reporting dashboard.)

Note: This report is only for the Commit phase of the Patching Job (final phase of the deploy process).

 

If you click over either of the bars in the chart, you are linked to a pop-up report with more information. The first image to the right shows a detail report for a deploy run that completed successfully.

Clicking on the server name displays the Deploy Itemwise Details report, which provides a list of the patches that were deployed to the server, along with other information.

Note: The Itemwise Details report is displayed only if the Agent version is version 8.8 or later.

Catalog Summary

This table shows information about the patch catalogs associated with the patching jobs. For each patch catalog, the table shows the number of jobs associated with the catalog, the date and time of the latest catalog update, and the date and time of the last successful update.

Note that the catalog summary does not show catalogs in the following scenarios:

  • Patch catalogs that have not been used in any patching job.
  • Patch catalogs that have been updated without running their associated Patch analysis jobs after the update.

Analyzing the history of the patching jobs run on servers

 To display a high-level view of the patch analysis and deploy process trends over time, select the Historical View option.

You can change the duration of the view by selecting the options at the top of the chart: day, week, month, quarter, or year.

To refine the scope, you can filter the data presented on the dashboard using the filter options, as described in Changing the scope of the data.

ReportDescription

Analysis historical view

(Non-distinct server count if multiple catalogs selected)

This report  is a line chart that shows the patch analysis job run progress over time. The chart shows how many jobs were running, pending, completed, failed, or completed with warnings, at any given point in time.

Note: With the Non-distinct server count, each server is counted once, even if it you selected multiple patch catalogs in the filter options.

If you hover over the view, the share, view toggle, and edit icons are displayed in the upper-right corner of the view. (The options are described in Troubleshooting the Live Reporting dashboard.)

Deploy historical view (Commit phase only)

This report is a line chart that shows the patch deployment job run progress over time. The chart shows how many jobs were running, pending, completed, failed, or completed with warnings, or skipped, at any given point in time.

Note: This report is only for the Commit phase of the Patching Job.

If you hover over the view, the share, view toggle, and edit icons are displayed in the upper-right corner of the view. (The options are described in Troubleshooting the Live Reporting dashboard.)

Reviewing a cohort analysis of patching jobs on your servers

To see the trends for how your patching activity has been progressing or, in some cases, regressing, select the Cohort Analysis option.


The cohort analysis groups the critical business function units based on your server groups (for example, All Windows servers), and indicates the percentage of servers that are compliant in that group. As an administrator or a manager, you can quickly learn how the patching activity is proceeding in your environment. 

Clicking on a percentile cell in the chart displays the Cohort Analysis Details report, as shown below.

This report provides details for a specific server group, by server.

You can filter the data in the cohort analysis reports using the filters in the Common group. See Changing the scope of the data.

Changing the scope of the data

For both the current view and the historical view, you can change the scope of the data displayed in the report by changing the filter options on the right side of the report. The filter options are displayed in two categories: Current/Historical View and Common filters, as shown below.

To refine the scope, you can filter the data presented on the dashboard using the following options:

Current/Historical View filters

  • Time period - Select a time period from the drop-down list. You can choose between the last 24 hours or intervals that span up to the last 90 days. The default is 24 hours.
  • Time range - Select a specific range of days by using the calendar icons next to the From and To fields.

Common filters

  • Server group - Click Select to choose a specific server group for which you want to see patching data. All static and smart groups are listed.  You can select up to 10 server groups.

    Note

    For more information about keeping this list of server groups up-to-date, see How do I refresh the list of server groups on the Live Reporting dashboard?
    For information about controlling the length of the list, see How can I shorten the list of server groups for filtering?

  • Catalog name - (Patch reports only) Choose a patch catalog for which you want to see patching data.

  • Template name - (Compliance reports only) Select a Template Name. You can use this filter to view all templates, no templates, or select one or two templates to restrict the compliance data displayed.
  • Job Type - Use this filter to limit the display to a specific type of BMC Server Automation job.
  • Customer - Out-of-the-box property that you can select to filter the data by customer.
  • Location - Out-of-the-box property that you can select to filter the data by location.
  • Role - This option is available only if you have launched the dashboard from a browser, and if the BMC Server Automation user that is logged on is assigned multiple roles.

For the cohort analysis report, the Common filters apply, but not the Current/Historical View filters.

Where to go from here

Troubleshooting the Live Reporting dashboard

Was this page helpful? Yes No Submitting... Thank you

Comments