Elasticsearch Metadata

Opster Team

Last updated: May 22, 2022

| 1 min read

In addition to reading this guide, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.

The Elasticsearch Check-Up is free and requires no installation.

Overview

Metadata in Elasticsearch refers to additional information stored for each document. This is achieved using the specific metadata fields available in Elasticsearch. The default behavior of some of these metadata fields can be customized during mapping creation.

Examples

Using _meta meta-field for storing application-specific information with the mapping:

PUT /my_index?pretty
{
  "mappings": {
    "_meta": { 
      "domain": "security",
      "release_information": {
        "date": "18-01-2020",
        "version": "7.5"
      }
    }
  }
}

Notes

  • In version 2.x, Elasticsearch had a total 13 meta fields available, which are: _index, _uid, _type, _id, _source, _size, _all, _field_names, _timestamp, _ttl, _parent, _routing, _meta
  • In version 5.x, _timestamp and _ttl meta fields were removed.
  • In version 6.x, the _parent meta field was removed.
  • In version 7.x, _uid and _all meta fields were removed.

Related log errors to this ES concept


Templates are still reported as out of date after the upgrade. The template upgrade will be retried.
Templates were upgraded successfully to version
Unable to resolve default zone from metadata server for GCE discovery service
Metadata state not restored; reason:
Error loading template as part of metadata upgrading
Creating index; cause ; templates ; shards /; mappings
Failed to open / find files while reading metadata snapshot
createmapping
Skipping unknown custom object with type
Unable to resolve project from metadata server for GCE discovery service
Unable to shutdown GCE Http Transport
Failed to remove snapshot deletion metadata

< Page: 1 of 7 >

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content