|
@@ -23,16 +23,27 @@ If a new data stream or index matches more than one index template, the index te
|
|
|
// tag::built-in-index-templates[]
|
|
|
[IMPORTANT]
|
|
|
====
|
|
|
-{es} has built-in index templates for the `metrics-*-*`, `logs-*-*`, and
|
|
|
-`synthetics-*-*` index patterns, each with a priority of `100`. The
|
|
|
-{fleet-guide}/fleet-overview.html[{agent}] uses these templates to create data
|
|
|
-streams. If you use the {agent}, assign your index templates a priority lower
|
|
|
-than `100` to avoid overriding the built-in templates.
|
|
|
+{es} has built-in index templates, each with a priority of `100`, for the
|
|
|
+following index patterns:
|
|
|
|
|
|
-Otherwise, to avoid accidentally applying the built-in templates, use a
|
|
|
-non-overlapping index pattern or assign templates with an overlapping pattern a
|
|
|
-`priority` higher than `100`.
|
|
|
+// tag::built-in-index-template-patterns[]
|
|
|
+- `logs-*-*`
|
|
|
+- `metrics-*-*`
|
|
|
+- `synthetics-*-*`
|
|
|
+// end::built-in-index-template-patterns[]
|
|
|
|
|
|
+The {fleet-guide}/fleet-overview.html[{agent}] uses these templates to create
|
|
|
+data streams. If you use the {agent}, assign your index templates a priority
|
|
|
+lower than `100` to avoid overriding the built-in templates. Otherwise, to avoid
|
|
|
+accidentally applying the built-in templates, do one or more of the following:
|
|
|
+
|
|
|
+- To disable all built-index index and component templates, set
|
|
|
+<<stack-templates-enabled,`stack.templates.enabled`>> to `false` using the
|
|
|
+<<cluster-update-settings,cluster update settings API>>.
|
|
|
+
|
|
|
+- Use a non-overlapping index pattern.
|
|
|
+
|
|
|
+- Assign templates with an overlapping pattern a `priority` higher than `100`.
|
|
|
For example, if you don't use the {agent} and want to create a template for the
|
|
|
`logs-*` index pattern, assign your template a priority of `200`. This ensures
|
|
|
your template is applied instead of the built-in template for `logs-*-*`.
|