Using the Live Reporting dashboard
This topic provides an overview of how to use the Live Reporting dashboard, which displays complete live data in your database about the status of your patch, compliance, and job activities in your environment.
This topic includes the following sections:
Video: Using the Live Reporting dashboard
The following video provides basic information and helpful tips on how to use the Live Reporting dashboard.
Before you begin
Before using the Live Reporting dashboard, make sure you have completed the following:
- Ensure that you have completed all of the installation and setup tasks described in Installing and configuring Yellowfin to enable Live reporting.
Ensure that the user (or role) you are using to access the Live Reporting dashboard has the report.writer permission. Otherwise, the Live Reporting launch option will be disabled.
- There is auto-sync between users in BMC Server Automation and Yellowfin, provided the access roles are present appropriately. If you create any new user in BMC Server Automation, then you must map the required roles to access the yellowfin. If any user does not have Yellowfin access role, then these roles are not available on Yellowfin side.
- If you used the dashboard that was introduced in version 8.8, and had previously installed and configured Yellowfin, you must perform the upgrade steps outlined in Upgrading Yellowfin for Live Reporting. This is not applicable for BMC Server Automation 8.9.01 and later.
Launching the Live Reporting dashboard
You can launch the Live Reporting dashboard from the BMC Server Automation console or from an external browser. Perform either of the following steps depending on how you want to launch the Live Reporting dashboard:
Perform the following steps:
- Log on to the BMC Server Automation console with the user that is assigned the required role and authorization (as described in Step 7 of Installing and configuring Yellowfin to enable Live reporting).
- From the console, select the Configuration menu.
- Click Live Reporting to launch the Live Reporting dashboard.
You will not be warned about using non-trusted certificates if you:
- started your browser on the same host where you installed the trial CA certificate.
- purchased the CA certificate.
Perform the following steps:
Enter the following URL in your external browser:
Host name of the server hosting the Yellowfin server
Port number that the Yellowfin server listens on. The default port number is 8443.
- Log on to Yellowfin by entering the BMC Server Automation user ID who has been assigned with the required role (as described in Installing and configuring Yellowfin to enable Live reporting). The default password for this user ID is test (unless it had been changed during installation).
The initial display of the dashboard defaults to the Patch tab.
Overview of the Live Reporting dashboard
To Live Reporting dashboard includes three tabs:
- Patch tab – current, historical, and cohort analysis views of patch-related data
- Compliance tab – current, historical, and cohort analysis views of server compliance
- Job Activity tab – successful and failed jobs run on your servers
Each of these tabs includes multiple reports which provide high-level information. The Compliance tab is shown as an example below:
To see the details, you can "drill down" on these reports to see additional data (for example, which patches were installed for a given job, or how many servers are actually compliant per a given policy, as shown below).
You can easily export reports, for example in PDF format, for closer examination or sharing with management.
All views display only those servers for which the logged in user has access.
Types of reports available
The Job Activity tab provides reports related to the most recent job activity for each available Application Server.
The Patch tab and the Compliance tab both include multiple ways to view the data. The following table provides descriptions of each of these views.
The current view displays several reports, high-level and more detailed, that are built off the most recent data from the database. The following example shows the current view for the Compliance tab.
The Historical view enables you to compare, over a period of time, the status of your patch management process and the compliance of your servers with corporate policies or industry standards.
The cohort analysis enables you to compare the the status of your patch management process and the compliance of your servers based on a specific property (Server Group, Location, or Customer Property). As an administrator or a manager, you can quickly learn how the patching activity or policy compliance is proceeding in your environment.
The Cohort Analysis view also enables you to identify the patch management or policy compliance ratio (as a percentage) for specific server groups.
The following example shows the cohort analysis for the Compliance tab.
Cohort charts are snapshots in time of the servers that were active at that time.
Reviewing the reports on the dashboard tabs
The following topics provide information about the various reports that are available on each of the dashboard tabs:
|Patch||Live Reporting dashboard Patch reports||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.|
|Compliance||Live Reporting dashboard Compliance reports||The Compliance tab lets you monitor the security controls in your managed environment. This tab also provides three distinct views of the data: the current state of the environment, a historical view, and a cohort analysis.|
|Job Aactivity||Live Reporting dashboard Job Activity reports||The Job Activity tab displays different job-related reports offered in Live Reporting, for example, to view the trending of the number of Windows versus Linux patch jobs in your environment.|
To keep the data in the dashboard as current as possible, it is important to periodically How do I refresh the list of server groups on the Live Reporting dashboard?, particularly if you have updated your server list or smart groups. See