honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-09 06:25:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Add UUID troubleshooting tip for stack monitoring (#55744)

Browse Source
This commit is contained in:
Lisa Cawley 2020-05-11 07:47:09 -07:00 committed by lcawl
parent 1474606b18
commit 7ce0a25fbc
2 changed files with 36 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/monitoring/how-monitoring-works.asciidoc
View File

@ -6,8 +6,8 @@
<titleabbrev>How it works</titleabbrev> <titleabbrev>How it works</titleabbrev>
++++ ++++
Each {es} node, {ls} node, {kib} instance, and Beat is considered unique in the Each {es} node, {ls} node, {kib} instance, and Beat instance is considered
cluster based on its persistent UUID, which is written to the unique in the cluster based on its persistent UUID, which is written to the
<<path-settings,`path.data`>> directory when the node or instance starts. <<path-settings,`path.data`>> directory when the node or instance starts.
Monitoring documents are just ordinary JSON documents built by monitoring each Monitoring documents are just ordinary JSON documents built by monitoring each

34
docs/reference/monitoring/troubleshooting.asciidoc
View File

@ -14,6 +14,10 @@ a ticket in the
https://support.elastic.co/customers/s/login/[Elastic Support portal]. https://support.elastic.co/customers/s/login/[Elastic Support portal].
Or post in the https://discuss.elastic.co/[Elastic forum]. Or post in the https://discuss.elastic.co/[Elastic forum].
[discrete]
[[monitoring-troubleshooting-no-data]]
=== No monitoring data is visible in {kib}
*Symptoms*: *Symptoms*:
There is no information about your cluster on the *Stack Monitoring* page in There is no information about your cluster on the *Stack Monitoring* page in
{kib}. {kib}.
@ -27,3 +31,33 @@ monitoring data by using {metricbeat} the indices have `-mb` in their names. If
the indices do not exist, review your configuration. For example, see the indices do not exist, review your configuration. For example, see
<<monitoring-production>>. <<monitoring-production>>.
[discrete]
[[monitoring-troubleshooting-uuid]]
=== Monitoring data for some {stack} nodes or instances is missing from {kib}
*Symptoms*:
The *Stack Monitoring* page in {kib} does not show information for some nodes or
instances in your cluster.
*Resolution*:
Verify that the missing items have unique UUIDs. Each {es} node, {ls} node,
{kib} instance, Beat instance, and APM Server is considered unique based on its
persistent UUID, which is found in its `path.data` directory. Alternatively, you
can find the UUIDs in the product logs at startup.
In some cases, you can also retrieve this information via APIs:
* For Beat instances, use the HTTP endpoint to retrieve the `uuid` property.
For example, refer to
{filebeat-ref}/http-endpoint.html[Configure an HTTP endpoint for {filebeat} metrics].
* For {kib} instances, use the
{kibana-ref}/access.html#status[status endpoint] to retrieve the `uuid` property.
* For {ls} nodes, use the
{logstash-ref}/monitoring-logstash.html[monitoring APIs root resource] to
retrieve the `id` property.
TIP: When you install {es}, {ls}, {kib}, APM Server, or Beats, their `path.data`
directory should be non-existent or empty; do not copy this directory from other
installations.