Add applies_to tags to ES troubleshooting

troubleshoot/elasticsearch/add-tier.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Preferred data tier
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/add-tier.html

troubleshoot/elasticsearch/allow-all-cluster-allocation.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Data allocation
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-cluster-allocation.html

troubleshoot/elasticsearch/allow-all-index-allocation.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Index allocation
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-index-allocation.html

troubleshoot/elasticsearch/circuit-breaker-errors.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/circuit-breaker-errors.html
 ---

troubleshoot/elasticsearch/corruption-troubleshooting.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Data corruption
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/corruption-troubleshooting.html

troubleshoot/elasticsearch/decrease-disk-usage-data-node.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Decrease disk usage
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/decrease-disk-usage-data-node.html

troubleshoot/elasticsearch/diagnose-unassigned-shards.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Unassigned shards
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnose-unassigned-shards.html

troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Corrupted repositories
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-corrupted-repositories.html

troubleshoot/elasticsearch/diagnosing-invalid-repositories.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Invalid repositories
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-invalid-repositories.html

troubleshoot/elasticsearch/diagnosing-unknown-repositories.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Unknown repositories
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-unknown-repositories.html

troubleshoot/elasticsearch/diagnostic.md

@@ -1,11 +1,14 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Diagnostics
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnostic.html
-applies_to:
-  deployment:
-    self:
-    ece:
 ---
 
 # Capture diagnostics [diagnostic]

troubleshoot/elasticsearch/discovery-troubleshooting.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Discovery
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/discovery-troubleshooting.html

troubleshoot/elasticsearch/elasticsearch-hadoop/elasticsearch-for-apache-hadoop.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Apache Hadoop
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/hadoop/current/troubleshooting.html
@@ -65,19 +72,11 @@ When encountering a performance issue, do some benchmarking first, in as much is
 
 Indexing performance depends *heavily* on the type of data being targeted and its mapping. Same goes for searching but add the query definition to the mix. As mentioned before, experiment and measure the various parts of your dataset to find the sweet-spot of your environment before importing/searching big amounts of data.
 
-## Getting help [help]
+## Get help [help]
 
-If you need help, there is a strong, helpful community of users on the [forum](https://discuss.elastic.co/c/elasticsearch-and-hadoop) and [IRC](http://www.elastic.co/community/) who are happy to help out.
+For more help, you can [contact us](/troubleshoot/index.md#contact-us). Use the tips in this section when emailing us or using the Elastic Support Portal.
 
-If something is not working, there are two possibilities:
-
-* there is a bug
-* you are doing something wrong
-
-Whichever it is, a **clear** description of the problem will help other users to help you. The more complete your report is, the quickest you will receive help from users!
-
-
-### What information is useful? [_what_information_is_useful]
+### Provide details[_what_information_is_useful]
 
 * OS & JVM version
 * Hadoop / Spark version / distribution
@@ -86,18 +85,9 @@ Whichever it is, a **clear** description of the problem will help other users to
 * the job or script that is causing the issue
 * Hadoop / Spark cluster size
 * {{es}} cluster size
-* the size of the dataset and a snippet of it in its raw format (CSV, TSV, etc..)
-
-If you don’t provide all of the information, then it may be difficult for others to figure out where the issue is.
-
-
-### Where do I post my information? [_where_do_i_post_my_information]
-
-Please don’t paste long lines of code in the mailing list or the IRC – it is difficult to read, and people will be less likely to take the time to help.
-
-Use one of the plethora of paste sites such as [pastebin](http://pastebin.com/) or [gist](http://gist.github.com/gists) (which we recommend):
+* the size of the dataset and a snippet of it in its raw format (CSV, TSV, etc.)
 
-[TBC: FANCY QUOTE]
-Please see the Elasticsearch [help](http://www.elastic.co/help/) page for tips on how to create a detailed user report, fast and easy.
+### Use a paste site [_where_do_i_post_my_information]
 
+Don't paste long lines of code in emails or the Elastic Support Portal. Instead, use a sharing or pasting utility such as [GitHub Gist](https://gist.github.com/).
 

troubleshoot/elasticsearch/fix-common-cluster-issues.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Common cluster issues
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-common-cluster-issues.html

troubleshoot/elasticsearch/fix-data-node-out-of-disk.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Data nodes out of disk
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-data-node-out-of-disk.html

troubleshoot/elasticsearch/fix-master-node-out-of-disk.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Master nodes out of disk
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-master-node-out-of-disk.html

troubleshoot/elasticsearch/fix-other-node-out-of-disk.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Other nodes out of disk
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-other-node-out-of-disk.html

troubleshoot/elasticsearch/fix-watermark-errors.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: "Watermark errors"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-watermark-errors.html

troubleshoot/elasticsearch/high-cpu-usage.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: High CPU usage
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/high-cpu-usage.html

troubleshoot/elasticsearch/high-jvm-memory-pressure.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/high-jvm-memory-pressure.html
 ---

troubleshoot/elasticsearch/hotspotting.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: "Hot spotting"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/hotspotting.html

troubleshoot/elasticsearch/increase-capacity-data-node.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Increase disk capacity
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-capacity-data-node.html

troubleshoot/elasticsearch/increase-cluster-shard-limit.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Total number of shards per node reached
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-cluster-shard-limit.html

troubleshoot/elasticsearch/increase-shard-limit.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Total number of shards for an index exceeded
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-shard-limit.html

troubleshoot/elasticsearch/increase-tier-capacity.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Not enough nodes to allocate shard replicas
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-tier-capacity.html

troubleshoot/elasticsearch/index-lifecycle-management-errors.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: "Index lifecycle management errors"
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-error-handling.html

troubleshoot/elasticsearch/mapping-explosion.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-explosion.html
 ---

troubleshoot/elasticsearch/monitoring-troubleshooting.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Monitoring
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-troubleshooting.html

troubleshoot/elasticsearch/red-yellow-cluster-status.md

@@ -1,4 +1,11 @@
 ---
+applies_to:
+  stack: 
+  deployment:
+    eck: 
+    ess: 
+    ece: 
+    self: 
 navigation_title: Red or yellow health status
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html