Using the Indexing Metrics Dashboard and Visualizations

Access the Indexing Metrics dashboard by selecting Dashboard, and then selecting Indexing Metrics from the list of dashboards.

The Indexing Metrics dashboard provides statistics on the transactions and segments during indexing.

This example illustrates the visualizations on the Indexing Metrics dashboard. You can find definitions for the visualizations later on this page.

Indexing Metrics Dashboard
Field or Control Description

Transaction Status

Displays the status of transactions as a pie-chart. The transaction statuses are:

  • Success

  • Error - The transactions in Error status. Refer to the example described later in this section on the steps to troubleshoot these transactions.

  • Reject - Search Framework attempts to re-run the indexing for the transactions in Reject status. If the number of transaction in Reject status are high, it may indicate that the OpenSearch cluster has resource constraints.

Selecting any of the slices from the pie-chart enables you to view only the transactions in the selected status in the Transaction Status visualization and the Transaction History visualization displays only the transactions of the selected status, thus enabling you to drill down to each transaction and view details of the transaction, such as process instance, index name, etc.

For example, to drill down to the transactions that are in Error status and to understand why the transaction is in Error status, you can perform the following steps:

  1. Select the Error status slice of the pie-chart. The Transaction History visualization displays only the transactions in the Error status.

  2. Select a transaction. The transaction expands to display data in a tabular format. You can use the JSON tab to view it in raw JSON format.

  3. Note down the process instance and the name of the index where the error occurred.

    Note:The name of the database forms the suffix for an index name. For example, ptportalregistry_xxxx, where xxxx refers to the database name. The database name is handy when you are monitoring multiple PeopleSoft applications, for example, HCM, FMS, etc. It is also handy when the same OpenSearch server is used in shared test environments of an application, for example, HCM, HCMdev, HCMTEST, etc.

  4. Log on to PIA, and navigate to the Build Search Index page (select PeopleTools, and then Search Framework, and then Search Admin Activity Guide, and then Administration, and then Schedule Search Index) where you can use the process instance number to obtain information on the transaction in error.

Transaction/Segment Count

Displays the count of transactions and segment at a specific time period in the form of a vertical bar chart.

Segment History

Displays the segment history and includes the attachment count and document count in each segment.

Transaction History

Displays the transaction history and includes the attachment type (attachment or non attachment) in each transaction and the time taken for each transaction.