Skip to main content
For the complete documentation index for agents and LLMs, see llms.txt.

Index Pages and Status Reference

Look up what the Indexes page and the Index Details page show, and what each index status means.

The Indexes Page​

The Indexes page lists all indexes that exist in a workspace and their status. There are two tabs on the page:

  • Active, for enabled indexes
  • Drafts, for indexes that were saved but not yet enabled

The Index Details Page​

Click an index name to open the Index Details Page where you can check:

  • The index ID
  • The status of files this index processes
  • Details of pipelines connected to this index
  • Index logs
  • Index metrics
  • Settings

File Statistics​

You can see the following statistics for the files in the index:

  • Total files
  • Indexed files: The number of files successfully indexed into the document store.
  • Documents in index: The cumulative total of documents stored in the document store across all indexing runs.
  • Pending tasks: The count of ongoing indexing tasks, like adding files to the document store or updating metadata.
  • Skipped files: The number of files that were processed but produced no documents.
  • Failed files: The count of files that encountered errors during indexing.

Metrics​

Open the Metrics tab on the Index Details page to see how much hardware your index uses. The tab shows pod-level charts, grouped by pod, for CPU usage, memory usage, and replica count. Use them to find out whether an index is running out of resources or whether the number of replicas you set in the index settings matches the load. If indexing is slow or fails, check these charts together with the index logs.

Index Status​

The status is shown on the Indexes page and reflects the current state of file indexing for an index:

  • Not indexed: The pipeline is being deployed, but the files have not yet been indexed
  • Indexing: Your files are being indexed. You can see how many files have already been indexed if you hover your mouse over the Indexing label.
  • Indexed: Your pipeline is deployed, all the files are indexed, and you can use your pipeline for search.
  • Partially indexed: At least one of the files wasn't indexed. This may be a problem with your file or a component in the pipeline. You can still run a search if at least some files were indexed. Check the index logs for details.
  • Skipped: All files were processed but none produced any documents. This happens when every file is skipped during indexing, for example, when files are duplicates or don't match the index's processing criteria. No documents are available for search.
  • Failed to index: All files failed during indexing.