From 10cc0088e43bd14351f6363767387cf4126e70a1 Mon Sep 17 00:00:00 2001 From: David Roberts Date: Fri, 13 Oct 2017 09:22:21 +0100 Subject: [PATCH] [DOCS] Make clearer that xpack.xyz.enabled settings are node settings (elastic/x-pack-elasticsearch#2731) The discussion in elastic/x-pack-elasticsearch#2697 shows that this was not clear before. relates elastic/x-pack-elasticsearch#2697 Original commit: elastic/x-pack-elasticsearch@87553faa2cea34436509bff4d5e1ab2c04ead269 --- docs/en/settings/ml-settings.asciidoc | 6 +++--- docs/en/settings/monitoring-settings.asciidoc | 2 +- docs/en/settings/notification-settings.asciidoc | 2 +- docs/en/settings/security-settings.asciidoc | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/en/settings/ml-settings.asciidoc b/docs/en/settings/ml-settings.asciidoc index a0b4ff7596d..c40de482fcf 100644 --- a/docs/en/settings/ml-settings.asciidoc +++ b/docs/en/settings/ml-settings.asciidoc @@ -12,10 +12,10 @@ You do not need to configure any settings to use {ml}. It is enabled by default. ==== General Machine Learning Settings `xpack.ml.enabled`:: -Set to `true` (default) to enable {ml}. + +Set to `true` (default) to enable {ml} on the node. + + -If set to `false` in `elasticsearch.yml`, the {ml} APIs are disabled. -You also cannot open jobs, start {dfeeds}, or receive transport (internal) +If set to `false` in `elasticsearch.yml`, the {ml} APIs are disabled on the node. +Therefore the node cannot open jobs, start {dfeeds}, or receive transport (internal) communication requests related to {ml} APIs. It also affects all {kib} instances that connect to this {es} instance; you do not need to disable {ml} in those `kibana.yml` files. For more information about disabling {ml} in specific {kib} diff --git a/docs/en/settings/monitoring-settings.asciidoc b/docs/en/settings/monitoring-settings.asciidoc index 9458bbaba68..e2764eb0f2a 100644 --- a/docs/en/settings/monitoring-settings.asciidoc +++ b/docs/en/settings/monitoring-settings.asciidoc @@ -21,7 +21,7 @@ For more information, see [[general-monitoring-settings]] ==== General Monitoring Settings `xpack.monitoring.enabled`:: -Set to `false` to disable {es} {monitoring} for Elasticsearch. +Set to `false` to disable {es} {monitoring} for Elasticsearch on the node. [float] [[monitoring-collection-settings]] diff --git a/docs/en/settings/notification-settings.asciidoc b/docs/en/settings/notification-settings.asciidoc index e8414386dc1..a3727a82afd 100644 --- a/docs/en/settings/notification-settings.asciidoc +++ b/docs/en/settings/notification-settings.asciidoc @@ -14,7 +14,7 @@ Slack>>, and <>. [[general-notification-settings]] ==== General Watcher Settings `xpack.watcher.enabled`:: -Set to `false` to disable {watcher}. +Set to `false` to disable {watcher} on the node. `xpack.http.proxy.host`:: Specifies the address of the proxy server to use to connect to HTTP services. diff --git a/docs/en/settings/security-settings.asciidoc b/docs/en/settings/security-settings.asciidoc index 52f6063bdaa..790289e3967 100644 --- a/docs/en/settings/security-settings.asciidoc +++ b/docs/en/settings/security-settings.asciidoc @@ -16,7 +16,7 @@ and <>. [[general-security-settings]] ==== General Security Settings `xpack.security.enabled`:: -Set to `true` (default) to enable {security}. + +Set to `true` (default) to enable {security} on the node. + + If set to `false` in `elasticsearch.yml`, {security} is disabled. It also affects all {kib} instances that connect to this {es} instance; you do not