Dashboard

The Dashboard tab contains the following sections:

Quick Stats

The quick stats section provides the aggregate number of resources being monitored by JMS Fleets in the chosen compartment.

Type your search text in the Search and Filter field.

You can customize the table columns by using the Manage columns icon.

You can choose a different compartment using the Compartment selector. The following tiles are available in this section:

  • Fleets: The Fleets tile displays the number of active fleets in the selected compartment.
  • Managed Instance: The Managed Instance tile displays the number of managed instances in the active fleets of the selected compartment.
  • Java Runtimes: The Java Runtimes tile displays the number of Java runtimes in the active fleets of the selected compartment.
  • Applications: The Applications tile displays the number of applications in the active fleets of the selected compartment.
Note

If you select the root compartment, the information displayed includes data for the root and all its sub-compartments. If you select any other compartment, only the data for that specific compartment is displayed.

In the Items per page field, choose 10, 20, 50, or 100 items to display. Select the header of a column to sort the list based on the title of the column.

Health

JMS resource health provides information about the health of JMS Fleet resources, including Fleets and a JMS plug-in.

JMS resource health provides a graphical representation of the number of issues, categorized as:

  • Fleets:
    • The fleets that don't have any managed instances.
    • The JMS plug-in registered to the fleet, which encountered errors while trying to push inventory data to the fleet inventory or operational logs, probably due to missing policies.

    Select Review fleet health issues to view the details and resolve the issues.

  • JMS plug-in:
    • The JMS plug-in in the instance that cannot register with JMS Fleets due to a missing policy.
    • The JMS plug-in in the instance, which encountered errors while trying to push inventory data to the fleet inventory or operational logs, probably due to missing policies.
    • The JMS plug-in in the instance that aren't associated with any fleet. This may happen if a plug-in is enabled under OCA but registration is not completed.

    Select Review JMS plug-in health issues to view the details and resolve the issues.

Note

If you select the root compartment, the information displayed includes data for the root and all its sub-compartments. If you select any other compartment, only the data for that specific compartment is displayed.

See JMS Resource Health for more information.

Announcements

The Announcements section shows all of the recent updates for Java-related products, for instance, the availability of a new update release or updates to the JMS service.