Relevance Inspector

This is for:

Developer System Administrator

The Relevance Inspector (platform-ca | platform-eu | platform-au) (RI) is a tool that allows members of the Administrators built-in group to assess and troubleshoot the relevance of the search results returned for a specific query.

More specifically, it lets users inspect:

  • The query parameters applied to a query before it reaches the query pipeline.

  • The query pipeline in which the query was routed.

  • The query pipeline rules that affected the query.

  • The query parameters applied to the query after it went through the query pipeline.

  • The search results that were returned for the query, along with their respective fields, field values, and ranking scores.

To use RI, you must first find the searchUid associated to the query you want to inspect. The searchUid is a GUID representing the unique identifier of a specific query. See Find the searchUid for instructions on how to find this value.

Note

In search interfaces built with the Coveo Atomic library, you can access RI directly from the search interface.

To inspect a query from an Atomic search interface

  1. Perform a query in the search box.

  2. Select and hold Alt (Windows) or Option (Mac) and double-click anywhere in the search interface.

  3. Click the Open in Relevance Inspector button.

The query will open in the Relevance Inspector (platform-ca | platform-eu | platform-au) page of the Coveo Administration Console.

Note that this option isn’t available on search interfaces built with the Coveo JavaScript Search Framework.

Find the searchUid

When accessing the Relevance Inspector (platform-ca | platform-eu | platform-au) page from the Coveo Administration Console, you must use the query’s searchUid to access the information available for this specific query.

To find the query’s searchUid

  1. Open the search interface in which you want to inspect how the query would behave.

  2. Open your web browser’s developer tools.

    Note

    The examples in this article use the Google Chrome developer tools. For browser-specific information, see:

  3. Select the Network tab.

  4. In the search box of the search interface, perform the desired query.

  5. Back in the developer tools window, under the Name column, click the latest request to the Search API. The request path should contain v2.

  6. Find the searchUid property, and then copy the value.

    `searchuid` in developer tools

Use the Relevance Inspector

  1. Access the Relevance Inspector (platform-ca | platform-eu | platform-au) page of the Coveo Administration Console.

  2. Under Type a Search UID, enter the searchUid of the query you want to inspect, and then click Inspect.

    type a `searchuid` section
    Note

    There may be a delay before the query is available for inspection.

  3. Under Query journey, the page now shows the following expandable sections. They correspond to the different steps of the query execution:

  4. Inspect the information to troubleshoot the query.

Results returned

This section shows the result items that the query returned, as shown in the search interface where the query was performed.

The table shows the score that was attributed by each ranking factor of the index.

You can also expand a given search result to get more information about ranking scores attributed by Coveo Machine Learning (Coveo ML) models or query ranking expressions (QREs).

results returned section
Notes

  • RI can replay queries that are up to seven days old.

  • When using RI, the original user query is replayed. However, the results may vary because RI considers the current indexed items, pipeline configuration, and user permissions of the person replaying the query. Therefore, if there are any differences in the indexed items, pipeline configuration, or user permissions between the person using RI and the original user who executed the query, RI may display different results compared to what the original user obtained.

Fields

In the Returned results section, you can select the Fields tab to get information about the fields and field values available for each returned result item.

fields tab

Query sent to pipeline

When you click See details, this section shows the query parameters that were applied to the query before it reached the query pipeline. Those represent the request payload sent to the Search API.

Note

Some available parameters are JSON objects (for example, actionsHistory). You can expand these objects to get more information.
query sent to pipeline section

Query pipeline selection

This section shows in which query pipeline the query was routed. See Query pipeline routing mechanisms and rules for further information about query routing.

When you click See details, this section lists all the pipelines available in the Coveo organization along with the reason why a given query pipeline was selected or not.

query pipeline selection section

Query pipeline rules and models

This section shows how the query pipeline rules along with the associated ML models were evaluated and executed according to the query you’re inspecting.

  • Click a type of rule to see more details on the execution of a specific rule and how it modified the query.

    query pipeline rules | Coveo

  • If a ML model was applied to the query, click the model name to see more details on how it modified the query.

    query pipeline model | Coveo

Query sent to index

When you click See details, this section shows the query parameters that were applied to the query after it went through the query pipeline. This represents the final information sent to query the index.

Note

Some available parameters are JSON objects (for example, facets). You can expand these objects to get more information.
query sent to index section

Required privileges

The following table indicates the privileges required to access the Relevance Inspector.

Action Service - Domain Required access level

Access the Relevance Inspector

Organization - Organization
Search - Replay any query

View

Search - Execute queries

Allowed