From 0dd5c3c186d832500bc88f1416f06544cb293fa1 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 9 Jul 2020 10:40:38 +0200 Subject: [PATCH] [Backport 7.x] Added sniffing blog post to documentation (#1252) Co-authored-by: Tomas Della Vedova --- docs/authentication.asciidoc | 2 ++ docs/configuration.asciidoc | 6 +++--- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/authentication.asciidoc b/docs/authentication.asciidoc index 7866d8c74..09b96c90a 100644 --- a/docs/authentication.asciidoc +++ b/docs/authentication.asciidoc @@ -20,6 +20,8 @@ override this option by configuring them. IMPORTANT: Do not enable sniffing when using Elastic Cloud, since the nodes are behind a load balancer, Elastic Cloud will take care of everything for you. +Take a look https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how[here] +to know more. [source,js] ---- diff --git a/docs/configuration.asciidoc b/docs/configuration.asciidoc index 6182effec..f090e9f81 100644 --- a/docs/configuration.asciidoc +++ b/docs/configuration.asciidoc @@ -84,11 +84,11 @@ _Default:_ `30000` _Default:_ `3000` |`sniffInterval` -|`number, boolean` - Perform a sniff operation every `n` milliseconds. + +|`number, boolean` - Perform a sniff operation every `n` milliseconds. Sniffing might not be the best solution for you, take a look https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how[here] to know more. + _Default:_ `false` |`sniffOnStart` -|`boolean` - Perform a sniff once the client is started. + +|`boolean` - Perform a sniff once the client is started. Sniffing might not be the best solution for you, take a look https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how[here] to know more. + _Default:_ `false` |`sniffEndpoint` @@ -96,7 +96,7 @@ _Default:_ `false` _Default:_ `'_nodes/_all/http'` |`sniffOnConnectionFault` -|`boolean` - Perform a sniff on connection fault. + +|`boolean` - Perform a sniff on connection fault. Sniffing might not be the best solution for you, take a look https://www.elastic.co/blog/elasticsearch-sniffing-best-practices-what-when-why-how[here] to know more. + _Default:_ `false` |`resurrectStrategy`