Using the Live Report dashboard


The Live Report dashboard displays live data from the TrueSight Server Automation database about the status of your patch, compliance, and job activities in your environment. The dashboard is organized into the following tabs:

  • Compliance
  • Job Activity
  • Patch

You can sort the data according to your requirements. Also, you can export individual sections from the dashboard in CSV or PDF format to meet your reporting and compliance needs.

Supported browsers

Access the Live Report dashboard by using the latest version of one of the following browsers:

  • Chrome
  • Firefox 
  • Microsoft Edge

Before you begin

Make sure that you have been assigned the BLAdmins role.

To view the dashboard

  1. Enter the following URL in the browser:

    https://<AppServerHost>:<Port>/dashboards/#/liveDashboard

    Example:

    https://aus-bsa-004:9843/dashboards/#/liveDashboard

    VariableDescription
    <AppServerHost>Fully qualified name or IP address of the Application Server on which the Tomcat service has been enabled. 
    <Port>The port on the Application Server on which the Tomcat service is running. The default port is 9843.
  2. Enter the user name and password.

Compliance tab

The Compliance tab lets you monitor the security controls in your managed environment. This critical information is important for auditors and to view your current level of system security.

For example, you can use Live Report to answer the following questions:

  • How many servers are currently compliant, and how many are non-compliant? 
  • How many servers are policy compliant in a specific week? 
  • What percentage of my Red Hat servers display unacceptable policy compliance?

ComplianceTABC.png

 

Panels on the Compliance tab

The following table describes the panels on the Compliance tab:

Panel

Description
Enrolled Servers Summary

Displays the total number of servers you are managing in your environment, as well as the distribution by OS type. It 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).

Example

TSSA-ComplienceTabEnrolledRerver.png

Compliance Servers Summary

Displays the total number of servers in your environment that your compliant activities are running against. This information lets you to identify any critical gaps that must be addressed immediately to ensure your coverage is complete.

Example

TSSA-Compliance Servers Summary.png

Summary by OS

Displays the total number of compliant versus non-compliant servers, separated by their operating system.

Important: With the non-distinct server count, each server is counted once.

Use the toggle icon next to the panel name to switch between the table view and bar chart view. Hover over a bar to see the exact number of servers for an operating system. 

Example

TSSA-Summary By OS.png

Compliance Run Progress Status

Displays the current status of servers, indicating the number of policies that completed successfully, completed with warnings, running, pending, or failed.

Example

TSSA-Compliance Run Progress Status.png

Summary by Policy

Displays the top 10 policies used in the analysis, and the number of analyzed servers for each, based on the current snapshot.

Use the toggle icon next to the panel name to switch between the graph view and the table view.

Example

2025-10-08_15-11-13000004.png

Non-Compliant Servers

Displays the top 10 servers that have had the highest number of failed rules during the latest run. This information is useful to troubleshoot problems in your environment, to see which servers are the most non-compliant, in order to take the appropriate corrective measures.

Use the toggle icon next to the panel name to switch between the table view and graph view. Hover over a bar to see the exact number of rules that failed on a server. 

Example

LiveReportNonComplient.png

Compliance Historical View 

Displays the report that lets you quickly view how many servers are compliant and how many are non-compliant over a given date range (for example, day, week, month, quarter, or year). This view lets you see how a trend of compliance is progressing in your environment. 

Use the toggle icon next to the panel name to switch between the chart view and the line graph view of the report.

Hover over any of the data points in the chart to view the number of non-compliant servers on a specific day.

Example

TSSA-ComplianceTabHistoricalView.png

Cohort Analysis

Displays the percentage of policy compliance for your server groups (for example, All Windows servers or All Red Hat servers).  

Example

LiveDashboard_Cohort_254.png

Filters on the Compliance tab

Use the following filters to limit the data to be displayed on the Compliance tab:

  • Date: Select a specific range of days by using the Start and End fields.
  • Time Period: Select a time period from the list. You can choose between the last 24 hours or intervals that span up to the last 90 days (default). 
  • Policy Name: Select the required policies from the list.
  • OS: Select the required operating systems from the list. 

Job Activity tab

The Job Activities tab displays different job-related reports.

For example, the TrueSight Server Automation administrator can use the Live Reporting dashboard to answer the following questions:

  • What jobs am I running per application server? 
  • Which jobs have failed per target? 
  • Which jobs recently failed? 

JobActivityTab.png

Panels on the Job Activity tab

The following table describes the panels on the Job Activity tab:

PanelDescription
Enrolled Servers Summary

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).

Example

TSSA-JobactivitytabEnrolledSummary.png

Job Activity Servers Summary

Displays the total number of servers on which jobs were run for the given time period. It also shows the distribution of those servers by OS type.

Example

TSSA-Job Activity Servers Summary.png

Running Server Summary By Job Type

Displays the distribution of active jobs running on your servers.

Example

Running Server Summary.png

Job Activity Run Progress Status

Displays the progress and current status of ongoing job executions, showing which jobs are running, completed, or have errors. Supports real-time monitoring, troubleshooting, and export for reporting.

Example

TSSA-Job Activity Run Progress Status.png

Job Activity by Application Server

Displays job execution statistics per application server, allowing assessment of workload distribution and server-specific trends.

Example

TSSA-JobActivityApplicationSummary.png

Most Failed Jobs by Target

Displays which jobs have the highest number of failed targets in the latest run. The panel shows the number of times the job attempted to execute, and the number of failed runs. It also displays the user name that created the job, and the user who last ran the job.

Example

TSSA-Most Failed Jobs By Targets.png

Most Consecutive Recent Failure Jobs (More than 3)

Displays the recently failed jobs, including job name, target, and failure time stamp. This helps in rapid response and troubleshooting.

Example

TSSA-Most Consecutive Recent Failure Jobs (More than 3).png

Filters on the Patch tab

Use the Job Type filter to display the data for a specific type of TrueSight Server Automation job.

Patch tab

The Patch tab displays complete information about patch management. 

For example, you can can use Live Report 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?

Zoomed Patch.png

 

Panels on the Patch tab

The following table describes the panels in the Patch tab:

PanelDescription
Enrolled Servers Summary

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

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

Example

TSSA-ComplienceTabEnrolledRerver.png

Patching Servers Summary

Displays the total number of servers currently involved in a patching activity (analysis or deploy).

It also displays the distribution of those servers by OS type.

Example

Patching Servers Summary.png

Analysed Servers Summary

Displays the following information:

  • 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.

Example

Analysed Servers Summary (Non-distinct server count if multiple catalog selected).png

Deployed Servers Summary
(Commit Phase Only)

Displays the following information:

  • 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.

Example

Deployed Servers Summary (Commit Phase Only).png

Analysis Run Progress Status

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.

Use the toggle icon next to the panel name to switch between the chart version of the report, and the line graph version of the report.

Example

Analysis Run Progress Status (Non-distinct server count if multiple catalog selected).png

Deploy Run Progress Status
(Commit Phase Only)

Uses charts to show the overall progress of the patch deployment.

The panel 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

Use the toggle icon next to the panel name to switch between the chart view and table view. 

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

If you click 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.

Example

Deploy Run Progress Status (Commit Phase Only).png

Catalog Summary

Displays information about the patch catalogs associated with the patching jobs. For each patch catalog, the panel 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.

Example

Catalog Summary.png

Analysis Historical View

A line chart that displays the patch analysis job run progress over time. The chart displays 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.

Use the toggle icon next to the panel name to switch between the chart view and table view. 

Example

AnalysisHistorical.png

Deploy Historical View

A line chart that displays 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.

Use the toggle icon next to the panel name to switch between the chart view and table view. 

Example 

Deploy Historical View.png

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. 

Example

CohortPatch.png

Filters on the Patch tab

Use the following filters to limit the data to be displayed on the Patch tab:

  • Date: Select a specific range of days by using the Start and End fields.
  • Time Period: Select a time period from the list. You can choose between the last 24 hours or intervals that span up to the last 90 days (default). 

 

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

TrueSight Server Automation 25.4