Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Dashboard tab indicates the following situations:•    Data

  • Data is not loaded to the PMDB

...

  • Agents are failing

...

  • FocalPoints are failing

...

  • License Limitation Metrics which have been exceeded

...

  • Licenses have expired or are near expiration

...

  • Licenses that are installed

...

  • Actions Items which are critical

...

  • Agents are stopped

...

  • Instances configured to experience downtime during the selected time frame

How the Dashboard tab is structured

...

In the Dashboard tab, above the Category Details area, is the view controls bar. This bar includes:•    Last

  • Last Refreshed display. This displays the date and time that the information was last refreshed.

...

  • Auto Refresh is off / Auto Refresh is on button. This button enables you to control whether the information is refreshed automatically.

...

  • Node view control. By default information is displayed for all Nodes.

...

  • To display the overview status of all Precise components in a specific node, select the node from the drop-down menu.

...

  • Application view control. By default information is displayed for all Applications.

...

  • To display the overview status of all Precise components in a specific application, select the application from the drop-down menu.

About the Category Details table

...

The Main area (right pane) will display tables based on the selection made previously on the Category Details table. The following table shows the information displayed in the Category Details table.

Table 3-1    Category 1 Category Details table

Header    Description

...

HeaderDescription
Status

Indicates the highest severity error encountered by one of the category’s components, as follows:

...

Image Added Red. Indicates that at least one of the category’s components encountered a high severity error.

...

Image Added Orange. Indicates that at least one of the category’s components encountered a medium severity error.

...

Image Added Yellow. Indicates that at least one of the category’s components encountered a low severity error.

...

Image Added Green. Indicates that none of the category’s components encountered errors.

...

Image Added Indicates components configured to experience downtime in the defined time frame. Errors for this component are ignored.

...

Image Added Indicates problematic components that have been acknowledged and are currently being handled. These components, and the errors resulting from them, are excluded from their category’s total and are grouped together in this category. For more information, see

...

...

.

Category

...

Indicates a group per technology, such as:

...

  • Agents

...

  • FocalPoints

...

  • Warehouse processes

...

  • License Limitation Metrics

...

  • Licenses

...

  • Action items
Total

...

componentsIndicates the total number of components in the selected category.

...

Errors

The color-coded stacked bar indicates the number of underlying components that have an error. Only red (high) and orange (medium) severity errors are shown.

Click on the icon on the header to switch between the following display methods:

...

  1. Show relative-sized colored toolbar according to the number of components that have problems.

...

  1. Show full-sized colored toolbar.

...

  1. Show the number of components that have problems.

About the Main area in the Dashboard tab

...

After selecting a category (Agents, FocalPoints, Warehouse processes, Licenses, Action items, or Acknowledged Items) in the Category Details table, the Detailed Description fish-eye displays text relevant to the selected category. For example: if Agents or Focalpoints are selected in the Category Details table, the Detailed Description fish-eye displays a detailed description of the current status for the selected Agents or FocalPoints. Recommendations to resolve the problem are also given.

Anchor
Problematic
Problematic
Defining problematic components as acknowledged

Handling a problematic component and solving its underlying issues might take time, and continue over into additional time frames. By default, problematic components continue to produce error reports until the underlying issue is resolved. To avoid excess error reports stemming from the same problematic component, you can acknowledge the component as problematic and currently being handled. Components can be defined as acknowledged for a defined period of time or until specified differently.

...