[DOCS] Removed X-Pack installation terminology (elastic/x-pack-elasticsearch#4339)
Original commit: elastic/x-pack-elasticsearch@4987e15148
This commit is contained in:
parent
e5d18ad45c
commit
e521bb55ff
|
@ -73,7 +73,7 @@ Username to use for authentication with {es}.
|
||||||
[float]
|
[float]
|
||||||
=== Examples
|
=== Examples
|
||||||
|
|
||||||
Run the migrate tool after you install the X-Pack plugin. For example:
|
Run the migrate tool when {xpack} is installed. For example:
|
||||||
|
|
||||||
[source, sh]
|
[source, sh]
|
||||||
----------------------------------------------------------------------
|
----------------------------------------------------------------------
|
||||||
|
|
|
@ -29,7 +29,6 @@ To follow the steps in this tutorial, you will need the following
|
||||||
components of the Elastic Stack:
|
components of the Elastic Stack:
|
||||||
|
|
||||||
* {es} {version}, which stores the data and the analysis results
|
* {es} {version}, which stores the data and the analysis results
|
||||||
* {xpack} {version}, which includes the {ml} features for both {es} and {kib}
|
|
||||||
* {kib} {version}, which provides a helpful user interface for creating and
|
* {kib} {version}, which provides a helpful user interface for creating and
|
||||||
viewing jobs
|
viewing jobs
|
||||||
|
|
||||||
|
@ -44,8 +43,11 @@ single VM or even on your laptop (requires 64-bit OS).
|
||||||
As you add more data and your traffic grows,
|
As you add more data and your traffic grows,
|
||||||
you'll want to replace the single {es} instance with a cluster.
|
you'll want to replace the single {es} instance with a cluster.
|
||||||
|
|
||||||
When you install {es} and {kib}, the {ml} features are enabled by default. If
|
By default, when you install {es} and {kib}, {xpack} is installed and the
|
||||||
you have multiple nodes in your cluster, you can optionally dedicate nodes to
|
{ml} features are enabled. You cannot use {ml} with the free basic license, but
|
||||||
|
you can try all of the {xpack} features with a <<license-management,trial license>>.
|
||||||
|
|
||||||
|
If you have multiple nodes in your cluster, you can optionally dedicate nodes to
|
||||||
specific purposes. If you want to control which nodes are
|
specific purposes. If you want to control which nodes are
|
||||||
_machine learning nodes_ or limit which nodes run resource-intensive
|
_machine learning nodes_ or limit which nodes run resource-intensive
|
||||||
activity related to jobs, see <<xpack-settings>>.
|
activity related to jobs, see <<xpack-settings>>.
|
||||||
|
|
|
@ -1,8 +1,9 @@
|
||||||
[[watcher-getting-started]]
|
[[watcher-getting-started]]
|
||||||
== Getting Started with {watcher}
|
== Getting Started with {watcher}
|
||||||
|
|
||||||
{Watcher} is automatically enabled when you <<installing-xpack, install
|
By default, when you install {es} and {kib}, {xpack} is installed and the
|
||||||
{xpack}>> into Elasticsearch and Kibana.
|
{watcher} is enabled. You cannot use {watcher} with the free basic license, but
|
||||||
|
you can try all of the {xpack} features with a <<license-management,trial license>>.
|
||||||
|
|
||||||
[[watch-log-data]]
|
[[watch-log-data]]
|
||||||
To set up a watch to start sending alerts:
|
To set up a watch to start sending alerts:
|
||||||
|
|
Loading…
Reference in New Issue