View Your Dashboards

After you have configured your monitoring, you can view your metric and alarm data in pre-defined dashboards.
uim901
After you have configured your monitoring, you can view your metric and alarm data in dashboards.
Contents
Accessing Your Dashboards
To access your dashboards, click the
Dashboards
icon (Dashboards Icon) in the left navigation of the Operator Console (OC).
  • UIM 20.3.3 has removed dependency on CA Business Intelligence (CABI) for rendering the native OC screens: Home page, Group view page, Device view page, and Monitoring Technologies (probes) view page. Custom and Out-of-the-Box dashboards and reports are still rendered by using CABI; that is, they have a dependency on CABI. However, the native OC screens are no longer dependent on CABI (Jaspersoft) and are rendered by using HTML5. For more information about the native OC screens using HTML5, see the Configuring and Viewing Monitoring Data article or the "Removing CABI Dependency (Native Operator Console)" section in the UIM 20.3.3 article.
  • To view an overview dashboard for a specific group, navigate to the group and click the
    Dashboards
    icon (Dashboards Icon)  in the upper-right corner of the screen.
In UIM 20.3.3, the main Dashboard page is displayed as follows when accessed using the Dashboard link in the left navigation view:
Additionally, in UIM 20.3.3, the dashboard pages for the monitoring technologies like processes, rsp, cdm, net_connect, and so on are rendered by using HTML5, not CABI. Therefore, when you click a tile on the main Dashboards page, the dashboard pages for such probes are rendered by using HTML5. The following screenshot shows an example of the cdm dashboard page in UIM 20.3.3:
Dashboard Time Ranges
Some dashboards allow you to select a time range for viewing metric data. If the dashboard you are viewing supports time ranges, a time range list appears in the upper-left corner of the screen.
Managing Dashboard Report Content
The following actions might be available to manage the contents of a report:
  • Click an item in a report legend to add or remove the data from a report.
  • Click a table column heading to format, filter, or sort table content.
Dashboard Basics for Monitoring
This section provides some general guidelines on how to monitor your environment effectively. The predefined dashboards are designed to help you quickly identify the source of an alarm and make your monitoring more effective and meaningful over time. When an alarm is generated, consider the following items:
  • Identify alarm information -  Alarms identify changes in your environment that require some form of intervention. The intervention might need to occur immediately or at some point in the future depending on the type or severity of the alarm. The quickest way to view all open alarms in your environment is from the Summary Dashboard.
  • Look for groups of related alarms - Alarms can occur within a related group of resources. When groups of alarms occur, identify any shared physical resources and any shared software or services that serve as supporting resources for the group. You can quickly identify groups from the Monitored Technologies report or Top Groups by Alarm report in the Summary Dashboard. Once you identify a problematic group, you can use the links in the report to view more specific information about the group resources.
  • Review metrics - Review the metrics of the highest-level resource with an alarm in the group. The metrics allow you to identify what system, instance, devices, components, or services are not performing well. It might be necessary to continue this review process until the true cause of the alarm is identified. For example, virtual machines might generate alarms if their host system runs out of memory. In this example, adding more memory to the host system should resolve the virtual machine alarms. The summary dashboards for devices, groups, probes, and services contain reports that you can use to view key performance indicator metrics.
  • Investigate how to prevent future problems – Once an issue is corrected, evaluate if more adjustments for alarms or more metrics are needed for your dashboards.