[DOCS] Adding Getting Help section to troubleshooting docs (#87095)

* Adding Getting Help section

Add getting help section in the troubleshooting guide to be pointed by health API when issues are too complicated to be addressed. 

This is taken from https://www.elastic.co/guide/en/cloud/current/ec-get-help.html, someone might want to elaborate it a bit more?

* Fix broken partintro, modify headings, and update wording

Co-authored-by: Adam Locke <adam.locke@elastic.co>
This commit is contained in:
Leaf-Lin 2022-05-26 05:58:41 +10:00 committed by GitHub
parent b4668ca868
commit ad0228fd2f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 34 additions and 18 deletions

View file

@ -39,4 +39,3 @@ include::local-export.asciidoc[]
include::http-export.asciidoc[]
include::pause-export.asciidoc[]
include::troubleshooting.asciidoc[]

View file

@ -1,9 +1,5 @@
[[monitoring-troubleshooting]]
== Troubleshooting monitoring
++++
<titleabbrev>Troubleshooting</titleabbrev>
++++
Use the information in this section to troubleshoot common problems and find
answers for frequently asked questions. See also
{logstash-ref}/monitoring-troubleshooting.html[Troubleshooting monitoring in {ls}].

View file

@ -9,5 +9,4 @@ include::api-quickref.asciidoc[leveloffset=+2]
include::ecommerce-tutorial.asciidoc[leveloffset=+2]
include::examples.asciidoc[leveloffset=+2]
include::painless-examples.asciidoc[leveloffset=+2]
include::troubleshooting.asciidoc[leveloffset=+2]
include::limitations.asciidoc[leveloffset=+2]

View file

@ -2,9 +2,6 @@
[[transform-troubleshooting]]
= Troubleshooting {transforms}
[subs="attributes"]
++++
<titleabbrev>Troubleshooting</titleabbrev>
++++
Use the information in this section to troubleshoot common problems.

View file

@ -3,11 +3,35 @@
[partintro]
--
This section provides a series of troubleshooting guides aimed at helping users
fix problems an Elasticsearch deployment might encounter.
This section provides a series of troubleshooting solutions aimed at helping users
fix problems that an {es} deployment might encounter.
Reporting and diagnosing the problems presented in this section is assisted
by the <<health-api,health API>>.
Several troubleshooting issues can be diagnosed using the
<<health-api,health API>>.
If none of these solutions relate to your issue, you can still get help:
* For users with an active subscription, you can get help in several ways:
** Go directly to the http://support.elastic.co[Support Portal]
** From the {ess} Console, go to the
https://cloud.elastic.co/support{ess-baymax}[Support page], or select the
support icon that looks like a life preserver on any page.
** Contact us by email: support@elastic.co
+
[TIP]
====
If you contact us by email, use the email address that you registered with so
that we can help you more quickly. If you are using a distribution list as your
registered email, you can also register a second email address with us. Just
open a case to let us know the name and email address you want to add.
====
* For users without an active subscription, visit the
https://discuss.elastic.co/[Elastic community forums] and get answers from
the experts in the community, including people from Elastic.
--
include::troubleshooting/data/increase-shard-limit.asciidoc[]
@ -21,3 +45,9 @@ include::troubleshooting/data/enable-cluster-allocation.asciidoc[]
include::troubleshooting/data/data-tiers-mixed-with-node-attr.asciidoc[]
include::troubleshooting/data/diagnose-unassigned-shards.asciidoc[]
include::monitoring/troubleshooting.asciidoc[]
include::transform/troubleshooting.asciidoc[leveloffset=+1]
include::../../x-pack/docs/en/watcher/troubleshooting.asciidoc[]

View file

@ -91,6 +91,4 @@ include::managing-watches.asciidoc[]
include::example-watches.asciidoc[]
include::troubleshooting.asciidoc[]
include::limitations.asciidoc[]

View file

@ -2,9 +2,6 @@
[[watcher-troubleshooting]]
== Troubleshooting {watcher}
[subs="attributes"]
++++
<titleabbrev>Troubleshooting</titleabbrev>
++++
[discrete]
=== Dynamic mapping error when trying to add a watch