Analyzer detail view Global search

Ops Center Analyzer Detail View User Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99ANA007-06
ft:lastEdition
2026-03-16

The Global search helps you to locate and filter a resource in the resource tree. It is available at the top of the left pane.

You can locate and filter the resources using the following methods:
  • Type the complete or partial resource name in the Search text box and then press Enter. The resource is displayed with its path in resource tree. If a resource is available at different nodes, the path for each node is displayed.

    For example:

  • If the resources count is large, it is recommended to use the search refinement option as follows:
    1. Type the @ character in the search text box after the search string.
      For example, to search the port CL1-A, type as follows:
      CL1-A@

      The refinement menu appears.

    2. Select the required probe type, resource type, and attribute name (optional).

      The resources that match the search are shown as a part of a filtered tree.

    3. The search result is shown in the left pane. You can perform the following operations with the search result:
      • Click the search result to expand the node level.
      • Click the node or any intervening level to open the corresponding resource reports in the Reports pane.
        Note: If the search query does not match any result, then the following message appears:

        No results matched for “search-string”.

      • To exit the search, click the button. This resets the tree view and search box, but retains the reports in the Reports pane.
  • When you search (without search refinement option), the global search feature by default searches the following list of metrics:
    • Name
    • IP Address or IP
    • Serial Number
    • WWN
    • Node WWN
    • FC WWN
    • Port WWN
    • Management IP Address

    For example, you can search a VM by its IP address as shown in the following screenshot:

  • The search result includes the shortest node path within a target system.
    For example, suppose the LDEV 00:00:30 is available under the following nodes in target Hitachi storage systems and VMware vCenter Server:
    • Storage Systems > Hitachi > VSP G/VSP F/VSP E > Storage-System-Instance > LDEVs
    • Storage Systems > Hitachi > VSP G/VSP F/VSP E > Storage-System-Instance > Parity Groups > Pool Parity Groups > Pool-Parity-Groups-Instance > LDEV
    • Hypervisors > VMware > Data Centers > Data-Center-Instance > Compute Resources > Compute-Resources-Instance > Hitachi LDEVs
    • Hypervisors > VMware > Data Centers > Data-Center-Instance > Datastores > Datastores-Instance > Disks > Disks-Instance > Hitachi LDEVs

    In this case, when you search for the LDEV 00:00:30, the search result will be as follows: