---
title: Use the Log Browser to review indexing logs
slug: '1864'
canonical_url: https://docs.coveo.com/en/1864/
collection: index-content
source_format: adoc
---
# Use the Log Browser to review indexing logs
The [**Log Browser**](https://platform.cloud.coveo.com/admin/#/orgid/logs/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/logs/browser/)) allows members with the [required privileges](#required-privileges) to review [indexing](https://docs.coveo.com/en/204/) logs.

Coveo [sources](https://docs.coveo.com/en/246/) are responsible to send a copy of your content to your [index](https://docs.coveo.com/en/204/), and to periodically update this index.
When a source indexes your content, your content [items](https://docs.coveo.com/en/210/) go through a series of small data handling processes.
This series is called the [_indexing pipeline_](https://docs.coveo.com/en/1893/), and each of the processes is a _stage_.
Every time an item goes through a stage of the pipeline, Coveo creates a log with the process result and details.
Therefore, each log represents an item at a stage of the indexing pipeline.

The Log Browser is a search page for indexing logs.
It's particularly useful when troubleshooting indexing issues that apply to specific items.
For example, you could use it to:

* Proactively review recently-logged indexing errors and warnings.

* Follow an item through the pipeline and find which stage failed because the item doesn't seem to have been indexed.

## Filter logs

By default, the [**Log Browser**](https://platform.cloud.coveo.com/admin/#/orgid/logs/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/logs/browser/)) shows all logs for all items during the selected time period.

To filter logs, you can:

* [Filter logs using facets](#filter-logs-using-facets)

* [Filter logs by URI](#filter-logs-by-uri)

* Select a time period

> **Tip**
>
> Check the [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) for a list of the [update operations](https://docs.coveo.com/en/2039/) performed on a [source](https://docs.coveo.com/en/246/), along with timestamps.

### Filter logs using facets

Use the [facets](https://docs.coveo.com/en/198/) on the left to narrow down the information displayed.
For details on the facet values, see [Operations](#operations) and [Results](#results).
See also [Indexing pipeline stages](https://docs.coveo.com/en/1893/) for details on the stages of the query pipeline, which appear in the **Stages** facet.

### Filter logs by URI

Filtering logs by URI allows you to display logs for a single item.

In the [**Log Browser**](https://platform.cloud.coveo.com/admin/#/orgid/logs/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/logs/browser/)), select a log of the desired item, and then click **Filter by URI** in the Action bar.

Alternatively, if you already have the desired URI, paste it in the **Search an exact item URI** box.
Item URIs can be obtained from the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)).

## Operations

An operation is what happens with the item at the end of the indexing process.
For example, you can send items through the indexing pipeline for them to be added to or deleted from the index.

The possible operations are:

[cols="1,4"]
|===
|Operation |Description

|Add
|Indexes the item for the first time or updates the item that is already indexed.

|Add reference
|[Indexes the item by reference](https://docs.coveo.com/en/l3qg9275/).

|Batch
a|Pushes a batch of items.
This operation can only be done through the [Push API](https://docs.coveo.com/en/68/).

|Delete
|Deletes the item from the index.

|Delete with children
a|Deletes the item from the index along with child items.
For example, when deleting a folder that contains subfolders, you delete the item and its children.
This operation can only be done through the [Push API](https://docs.coveo.com/en/68/).
|===

## Results

Each stage of the indexing pipeline represents a process.
The result of this process is included in the stage log.
Most rows may be expanded to show details.

The possible stage results are:

[cols="1,4"]
|===
|Result |Description

|Completed
|Stage completed successfully.

|Error
|An error occurred and the process failed.

|Rejected
a|
Item rejected by the indexing pipeline.
For example, when an [indexing pipeline extension (IPE)](https://docs.coveo.com/en/206/) rejects any item matching a certain condition.

|Skipped
a|Item skipped.
For example:

* During a source [refresh](https://docs.coveo.com/en/2710/), the [crawler](https://docs.coveo.com/en/2121/) skips items that didn't change since the last refresh.
If the entire source didn't change, the indexing process is dropped, and restarts at the next refresh.

* In the source JSON, you've [set the `action` parameter to `ignore`](https://docs.coveo.com/en/l3qg9275/) for items of a certain format.

|Warning
a|Something unexpected happened during the indexing process, but it didn't cause it to fail.
The process may work properly later or with a different method.
For example:

* The source wasn't ready for the Push API to push items.
Items will be added later, when the source is ready to receive content.

* An error occurred when trying to retrieve the item.
The [`actionOnError`](https://docs.coveo.com/en/l3qg9275/) setting will be applied.
|===

> **Note**
>
> The **Mapping extension** option corresponds to a Coveo default extension that applies source mappings.
> Therefore, when selected, the **Mapping extension** option shows the same logs as the **Mapping** option in the **Stages** facet.


## Required privileges

The following table indicates the privileges required for members to view elements of the [**Log Browser**](https://platform.cloud.coveo.com/admin/#/orgid/logs/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/logs/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/logs/browser/)) page.
See [Manage privileges](https://docs.coveo.com/en/3151/) and [Privilege reference](https://docs.coveo.com/en/1707/) for details.

This includes the ability to inspect the status of an item sent through the indexing pipeline.

[cols="~,~,~",options="header"]
|===
|Action |Service - Domain |Required access level

.3+|View the Log Browser
|Content - Fields
|View

|Content - Sources
|View

|Organization - Organization
|View
|===