The template files are automatically generated. Please do not edit the files directly.
In order to edit the template please modify template-operations.yml, template-project.yml and the respective namespace files referenced there.
To rebuild the template, run:
make
For details about the mapping please see ElasticSearch reference and Kibana reference
This file contains the skeleton of the template without the mappings section.
by sections:
aliases
: Aliases for the indices produces from the template. Aliases will be automatically generated along with the indices in future.
mappings
: mappings section
_default_
: default mapping skeleton. It is the only mapping present in the skeleton. Other mappings from template-operations.yml, template-project.yml will copy this skeleton.
date_detection
: we force no date detection in the unknown fields.
dynamic_templates
: describes the mapping for autocreated fields.
properties
: empty section that is populated with the content from template-operations.yml, template-project.yml
order
: order of the template. lower order templates are applied first.
settings
: various settings
index_patterns
: indices that will be matched by this template
This file the skeleton of the index pattern file.
by sections:
title
: Filled in by the openshift-elasticseach-plugin index pattern loader
timeFieldName
: Name of the time field - the script will look for the first field in the default
namespace that has type: date
fields
: The script will fill this in based on the namespace
name
: The name of the field from the namespacetype
: Field data type (string, date, etc.) - this is thetype
parameter from the namespacecount
: Always has value of 0scripted
:true
orfalse
- all of our fields are not scripted, sofalse
indexed
:true
orfalse
- all of our fields are indexed, sotrue
analyzed
:true
orfalse
-true
if the namespace field hasindex: analyzed
,false
otherwisedoc_values
:true
orfalse
- taken from the namespacedoc_values
field
This is the file that contains all the settings information and pointers to the specific mappings.
skeleton_path
: The path to theskeleton.json
file that contain the initial JSON structure of the template.elasticsearch_template
: This section defines the parameters common for the entire template, they are explicitly overwritten in the final template file. **name
: index pattern matched. **order
: template order. Lower order is applied first. detailsnamespaces
: filenames of various namespace definitions to be included in the template