Missing documents on get
A high number of get-by-id requests are returning document-not-found results on one or more nodes. This often happens when applications update or fetch IDs that do not exist, or when upserts create new documents.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | High |
| Scope | Cluster |
| Domains | indexing |
You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to AutoOps event settings for details.
The default customization settings are:
| Setting | Type | Default |
|---|---|---|
| Maximum number of get doc requests for which the doc is not found | Integer | 100 |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
12 get-by-id requests returned a missing document.
Affected nodes: es-data-01 and es-data-02
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Check indexing operations for errors
Condition: Always shown for this insight.
High index.get.missing counts are expected during upserts: Elasticsearch tries to fetch the document first, then creates it if missing. If updates should always target existing documents, check clients and indexing pipelines for failed or skipped index operations.
A typical cause is updating or fetching a document by ID that does not exist. Upsert-heavy workloads routinely generate missing-document responses when a document is created on first write. A sustained spike above your threshold can indicate incorrect IDs, replication lag, or application logic that repeatedly requests documents that were never indexed.