github-mirrors/elasticsearch
1
0
Fork 0
mirror of https://github.com/elastic/elasticsearch.git synced 2025-04-25 07:37:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

[DOCS] Remove unneeded articles for Elasticsearch Service and Elastic Agent

Browse source
This commit is contained in:
James Rodewig 2021-04-02 16:01:30 -04:00
parent 4ff17c1b7a
commit d3c56e6fca
5 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/reference/datatiers.asciidoc
View file

@ -105,7 +105,7 @@ transitioning into the frozen tier into a shared-cache searchable snapshot.
Search is typically slower on the frozen tier than the cold tier, because {es} Search is typically slower on the frozen tier than the cold tier, because {es}
must sometimes fetch data from the snapshot repository. must sometimes fetch data from the snapshot repository.
NOTE: The frozen tier is not yet available on the {ess-trial}[{ess}]. To NOTE: The frozen tier is not yet available on {ess-trial}[{ess}]. To
recreate similar functionality, see recreate similar functionality, see
<<searchable-snapshots-frozen-tier-on-cloud>>. <<searchable-snapshots-frozen-tier-on-cloud>>.

2
docs/reference/indices/index-templates.asciidoc
View file

@ -46,7 +46,7 @@ following index patterns:
- `synthetics-*-*` - `synthetics-*-*`
// end::built-in-index-template-patterns[] // end::built-in-index-template-patterns[]
The {fleet-guide}/fleet-overview.html[{agent}] uses these templates to create {fleet-guide}/fleet-overview.html[{agent}] uses these templates to create
data streams. Index templates created by {fleet} integrations use similar data streams. Index templates created by {fleet} integrations use similar
overlapping index patterns and have a priority up to `200`. overlapping index patterns and have a priority up to `200`.

2
docs/reference/indices/put-component-template.asciidoc
View file

@ -99,7 +99,7 @@ Name of the component template to create.
- `synthetics-settings` - `synthetics-settings`
// end::built-in-component-templates[] // end::built-in-component-templates[]
The {fleet-guide}/fleet-overview.html[{agent}] uses these templates to configure {fleet-guide}/fleet-overview.html[{agent}] uses these templates to configure
backing indices for its data streams. If you use {agent} and want to overwrite backing indices for its data streams. If you use {agent} and want to overwrite
one of these templates, set the `version` for your replacement template higher one of these templates, set the `version` for your replacement template higher
than the current version. than the current version.

2
docs/reference/modules/indices/index_management.asciidoc
View file

@ -38,7 +38,7 @@ Specifies the hosts that can be <<reindex-from-remote,reindexed from remotely>>.
+ +
-- --
(<<dynamic-cluster-setting,Dynamic>>) (<<dynamic-cluster-setting,Dynamic>>)
If `true`, enables built-in index and component templates. The If `true`, enables built-in index and component templates.
{fleet-guide}/fleet-overview.html[{agent}] uses these templates to create data {fleet-guide}/fleet-overview.html[{agent}] uses these templates to create data
streams. If `false`, {es} disables these index and component templates. Defaults streams. If `false`, {es} disables these index and component templates. Defaults
to `true`. to `true`.

4
docs/reference/searchable-snapshots/index.asciidoc
View file

@ -219,9 +219,9 @@ repository storage then you are responsible for its reliability.
[[searchable-snapshots-frozen-tier-on-cloud]] [[searchable-snapshots-frozen-tier-on-cloud]]
=== Configure a frozen tier on {ess} === Configure a frozen tier on {ess}
The frozen data tier is not yet available on the {ess-trial}[{ess}]. However, The frozen data tier is not yet available on {ess-trial}[{ess}]. However,
you can configure another tier to use <<shared-cache,shared snapshot caches>>. you can configure another tier to use <<shared-cache,shared snapshot caches>>.
This effectively recreates a frozen tier in your {ess} deployment. Follow these This effectively recreates a frozen tier in your deployment. Follow these
steps: steps:
. Choose an existing tier to use. Typically, you'll use the cold tier, but the . Choose an existing tier to use. Typically, you'll use the cold tier, but the