Observability troubleshooting (#376)

natasha-moore-elastic · web-flow · commit 610bc95a5a59 · 2025-02-10T15:58:57.000Z
* Observability troubleshooting

* Adds quotations to nav titles

* Trigger rebuild
diff --git a/raw-migrated-files/docs-content/serverless/observability-troubleshooting-infrastructure-monitoring.md b/raw-migrated-files/docs-content/serverless/observability-troubleshooting-infrastructure-monitoring.md
diff --git a/raw-migrated-files/observability-docs/observability/troubleshooting-infrastructure-monitoring.md b/raw-migrated-files/observability-docs/observability/troubleshooting-infrastructure-monitoring.md
diff --git a/raw-migrated-files/toc.yml b/raw-migrated-files/toc.yml
@@ -398,7 +398,6 @@ toc:
       - file: docs-content/serverless/observability-triage-slo-burn-rate-breaches.md
       - file: docs-content/serverless/observability-triage-threshold-breaches.md
       - file: docs-content/serverless/observability-troubleshoot-logs.md
-      - file: docs-content/serverless/observability-troubleshooting-infrastructure-monitoring.md
       - file: docs-content/serverless/observability-view-alerts.md
       - file: docs-content/serverless/observability-view-infrastructure-metrics.md
       - file: docs-content/serverless/project-and-management-settings.md
@@ -807,7 +806,6 @@ toc:
       - file: observability-docs/observability/synthetics-troubleshooting.md
       - file: observability-docs/observability/triage-slo-burn-rate-breaches.md
       - file: observability-docs/observability/triage-threshold-breaches.md
-      - file: observability-docs/observability/troubleshooting-infrastructure-monitoring.md
       - file: observability-docs/observability/view-infrastructure-metrics.md
       - file: observability-docs/observability/view-observability-alerts.md
   - file: security-docs/security/index.md
diff --git a/troubleshoot/observability.md b/troubleshoot/observability.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "Observability"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/troubleshooting.html
 ---
 
-# Observability [troubleshooting]
+# Troubleshoot observability [troubleshooting]
 
 Learn how to troubleshoot common issues on your own or ask for help.
 
diff --git a/troubleshoot/observability/apm-agent-dotnet/apm-net-agent.md b/troubleshoot/observability/apm-agent-dotnet/apm-net-agent.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "APM .NET agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/dotnet/current/troubleshooting.html
 ---
 
-# APM .NET agent
+# Troubleshoot APM .NET agent
 
 Use the information in this section to troubleshoot common problems and find answers for frequently asked questions. As a first step, ensure your stack is compatible with the Agent’s [supported technologies](https://www.elastic.co/guide/en/apm/agent/dotnet/current/supported-technologies.html).
 
diff --git a/troubleshoot/observability/apm-agent-go/apm-go-agent.md b/troubleshoot/observability/apm-agent-go/apm-go-agent.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "APM Go Agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/go/current/troubleshooting.html
 ---
 
-# APM Go Agent
+# Troubleshoot APM Go Agent
 
 Is something not working as expected? Don’t worry if you can’t figure out what the problem is; we’re here to help! First, ensure your app is compatible with the agent’s [supported technologies](https://www.elastic.co/guide/en/apm/agent/go/current/supported-tech.html).
 
diff --git a/troubleshoot/observability/apm-agent-java/apm-java-agent.md b/troubleshoot/observability/apm-agent-java/apm-java-agent.md
@@ -1,11 +1,12 @@
 ---
+navigation_title: "APM Java Agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/java/current/trouble-shooting.html
 ---
 
-# APM Java Agent [trouble-shooting]
+# Troubleshoot APM Java Agent [trouble-shooting]
 
-Something isn’t quite working as expected? Here are some guidelines how to find out what’s going wrong.
+Something isn’t quite working as expected? Here are some guidelines how to find out what’s going wrong. 
 
 As a first step, please check if your stack is compatible with the currently [supported technologies](https://www.elastic.co/guide/en/apm/agent/java/current/setup.html#supported-technologies).
 
diff --git a/troubleshoot/observability/apm-agent-nodejs/apm-nodejs-agent.md b/troubleshoot/observability/apm-agent-nodejs/apm-nodejs-agent.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "APM Node.js Agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/nodejs/current/troubleshooting.html
 ---
 
-# APM Node.js Agent [troubleshooting]
+# Troubleshoot APM Node.js Agent [troubleshooting]
 
 Is something not working as expected? Don’t worry if you can’t figure out what the problem is; we’re here to help! As a first step, ensure your app is compatible with the agent’s [supported technologies](https://www.elastic.co/guide/en/apm/agent/nodejs/current/supported-technologies.html).
 
diff --git a/troubleshoot/observability/apm-agent-php/apm-php-agent.md b/troubleshoot/observability/apm-agent-php/apm-php-agent.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "APM PHP Agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/php/current/troubleshooting.html
 ---
 
-# APM PHP Agent [troubleshooting]
+# Troubleshoot APM PHP Agent [troubleshooting]
 
 Is something not working as expected? Don’t worry if you can’t figure out what the problem is; we’re here to help! As a first step, ensure your app is compatible with the agent’s [supported technologies](https://www.elastic.co/guide/en/apm/agent/php/current/supported-technologies.html).
 
diff --git a/troubleshoot/observability/apm-agent-python/apm-python-agent.md b/troubleshoot/observability/apm-agent-python/apm-python-agent.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "APM Python Agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/python/current/troubleshooting.html
 ---
 
-# APM Python Agent [troubleshooting]
+# Troubleshoot APM Python Agent [troubleshooting]
 
 Below are some resources and tips for troubleshooting and debugging the python agent.
 
diff --git a/troubleshoot/observability/apm-agent-ruby/apm-ruby-agent.md b/troubleshoot/observability/apm-agent-ruby/apm-ruby-agent.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "APM Ruby Agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/ruby/current/debugging.html
 ---
 
-# APM Ruby Agent [debugging]
+# Troubleshoot APM Ruby Agent [debugging]
 
 Hopefully the agent Just Works™, but depending on your situation the agent might need some tuning.
 
diff --git a/troubleshoot/observability/apm-agent-rum-js/apm-real-user-monitoring-javascript-agent.md b/troubleshoot/observability/apm-agent-rum-js/apm-real-user-monitoring-javascript-agent.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "APM Real User Monitoring JavaScript Agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/rum-js/current/troubleshooting.html
 ---
 
-# APM Real User Monitoring JavaScript Agent [troubleshooting]
+# Troubleshoot APM Real User Monitoring JavaScript Agent [troubleshooting]
 
 
 ## Some errors in the application appear to be originating from the agent’s JavaScript file [errors-originating-from-agent] 
diff --git a/troubleshoot/observability/apm-agent-swift/apm-ios-agent.md b/troubleshoot/observability/apm-agent-swift/apm-ios-agent.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: "APM iOS Agent"
 mapped_pages:
   - https://www.elastic.co/guide/en/apm/agent/swift/current/troubleshooting.html
 ---
 
-# APM iOS Agent [troubleshooting]
+# Troubleshoot APM iOS Agent [troubleshooting]
 
 Is something not working as expected? Don’t worry if you can’t figure out what the problem is; we’re here to help! As a first step, ensure your app is compatible with the agent’s [supported technologies](https://www.elastic.co/guide/en/apm/agent/swift/current/supported-technologies.html).
 
diff --git a/troubleshoot/observability/apm.md b/troubleshoot/observability/apm.md
@@ -6,7 +6,7 @@ mapped_pages:
 
 
 
-# Troubleshooting APM [apm-troubleshoot-apm]
+# Troubleshoot APM [apm-troubleshoot-apm]
 
 
 This section provides solutions to common questions and problems, and processing and performance guidance.
diff --git a/troubleshoot/observability/apm/known-issues.md b/troubleshoot/observability/apm/known-issues.md
@@ -110,8 +110,8 @@ There are three ways to fix this error:
 
 1. Find broken rules
 
-    :::::{admonition}
-    To identify rules in this exact state, you can use the [find rules endpoint](https://www.elastic.co/guide/en/kibana/current/find-rules-api.html) and search for the APM anomaly rule type as well as this exact error message indicating that the rule is in the broken state. We will also use the `fields` parameter to specify only the fields required when making the update request later.
+   :::::{admonition}
+   To identify rules in this exact state, you can use the [find rules endpoint](https://www.elastic.co/guide/en/kibana/current/find-rules-api.html) and search for the APM anomaly rule type as well as this exact error message indicating that the rule is in the broken state. We will also use the `fields` parameter to specify only the fields required when making the update request later.
 
     * `search_fields=alertTypeId`
     * `search=apm.anomaly`
@@ -124,7 +124,7 @@ There are three ways to fix this error:
     curl -u "$KIBANA_USER":"$KIBANA_PASSWORD" "$KIBANA_URL/api/alerting/rules/_find?search_fields=alertTypeId&search=apm.anomaly&filter=alert.attributes.executionStatus.error.message%3A%22params%20invalid%3A%20%5BanomalyDetectorTypes%5D%3A%20expected%20value%20of%20type%20%5Barray%5D%20but%20got%20%5Bundefined%5D%22&fields=id&fields=name&fields=actions&fields=tags&fields=schedule&fields=notify_when&fields=throttle&fields=params"
     ```
 
-    ::::{dropdown} Example result:
+   ::::{dropdown} Example result:
     ```json
     {
       "page": 1,
@@ -162,8 +162,8 @@ There are three ways to fix this error:
 
 2. Prepare the update JSON doc(s)
 
-    ::::{admonition}
-    For each broken rule found, create a JSON rule document with what was returned from the API in the previous step. You will need to make two changes to each document:
+   ::::{admonition}
+   For each broken rule found, create a JSON rule document with what was returned from the API in the previous step. You will need to make two changes to each document:
 
     1. Remove the `id` key but keep the value connected to this document (e.g. rename the file to `{{id}}.json`). **The `id` cannot be sent as part of the request body for the PUT request, but you will need it for the URL path.**
     2. Add the `"anomalyDetectorTypes"` to the `"params"` block, using the default value as seen below to mimic the pre-8.13 behavior:
@@ -183,20 +183,20 @@ There are three ways to fix this error:
         ```
 
 
-    ::::
+   ::::
 
 3. Update each rule using the `PUT /api/alerting/rule/{{id}}` API
 
-    ::::{admonition}
-    For each rule, submit a PUT request to the [update rule endpoint](https://www.elastic.co/guide/en/kibana/current/update-rule-api.html) using that rule’s ID and its stored update document from the previous step. For example, assuming the first broken rule’s ID is `046c0d4f`:
+   ::::{admonition}
+   For each rule, submit a PUT request to the [update rule endpoint](https://www.elastic.co/guide/en/kibana/current/update-rule-api.html) using that rule’s ID and its stored update document from the previous step. For example, assuming the first broken rule’s ID is `046c0d4f`:
 
     ```shell
     curl -u "$KIBANA_USER":"$KIBANA_PASSWORD" -XPUT "$KIBANA_URL/api/alerting/rule/046c0d4f" -H 'Content-Type: application/json' -H 'kbn-xsrf: rule-update' -d @046c0d4f.json
     ```
 
     Once the PUT request executes successfully, the rule will no longer be broken.
 
-    ::::
+   ::::
 
 
 
diff --git a/troubleshoot/observability/apm/what-happens-when-apm-server-elasticsearch-is-down.md b/troubleshoot/observability/apm/what-happens-when-apm-server-elasticsearch-is-down.md
@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-server-es-down.html
 ---
 
-# What happens when APM Server or Elasticsearch is down? [apm-server-es-down]
+# APM Server or Elasticsearch is down [apm-server-es-down]
 
 **If {{es}} is down**
 
diff --git a/troubleshoot/observability/explore-data.md b/troubleshoot/observability/explore-data.md
@@ -45,7 +45,7 @@ You can create multi-series visualizations for each report type, but you cannot
 The Explore {{data-source}} is currently enabled for the following apps:
 
 * Uptime
-* {user-experience}
+* {{user-experience}}
 
 To create a multi-series visualization:
 
diff --git a/troubleshoot/observability/inspect.md b/troubleshoot/observability/inspect.md
@@ -18,7 +18,7 @@ Inspecting requests is available for the following UIs:
 
 * Applications
 * Uptime
-* {user-experience}
+* {{user-experience}}
 
 
 ## Enable inspect [inspect-enable]
@@ -57,7 +57,7 @@ Hits
 Hits (total)
 :   The number of documents that match the query.
 
-{data-source-cap}
+{{data-source-cap}}
 :   The {{data-source}} that connected to the {{es}} indices.
 
 {{kib}} API query parameters
diff --git a/troubleshoot/observability/troubleshoot-mapping-issues.md b/troubleshoot/observability/troubleshoot-mapping-issues.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: "Mapping issues"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/troubleshoot-uptime-mapping-issues.html
 ---
@@ -13,9 +14,9 @@ There are situations in which {{heartbeat}} data can be indexed without the corr
 To fix this problem, you typically need to remove your {{heartbeat}} indices and data streams. Then you must create new ones with the appropriate mappings installed. To achieve this, follow the steps below.
 
 
-### Stop your {{heartbeat}}/{elastic-agent} instances [_stop_your_heartbeatelastic_agent_instances] 
+### Stop your {{heartbeat}}/{{elastic-agent}} instances [_stop_your_heartbeatelastic_agent_instances] 
 
-It is necessary to stop all {{heartbeat}}/{elastic-agent} instances that are targeting the cluster, so they will not write to or re-create indices prematurely.
+It is necessary to stop all {{heartbeat}}/{{elastic-agent}} instances that are targeting the cluster, so they will not write to or re-create indices prematurely.
 
 
 ### Delete your {{heartbeat}} indices / {{elastic-agent}} data streams [_delete_your_heartbeat_indices_elastic_agent_data_streams] 
@@ -40,7 +41,7 @@ For more information on how to use this command, or if you’re using DEB, RPM,
 This command performs the necessary startup tasks and ensures that your indices have the appropriate mapping going forward.
 
 
-### Run {{heartbeat}}/{elastic-agent} again [_run_heartbeatelastic_agent_again] 
+### Run {{heartbeat}}/{{elastic-agent}} again [_run_heartbeatelastic_agent_again] 
 
-Now, when you run {{heartbeat}}/{elastic-agent}, your data will be indexed with the appropriate mappings. When the {{uptime-app}} attempts to fetch your data, it should be able to render without issues.
+Now, when you run {{heartbeat}}/{{elastic-agent}}, your data will be indexed with the appropriate mappings. When the {{uptime-app}} attempts to fetch your data, it should be able to render without issues.
 
diff --git a/troubleshoot/observability/troubleshooting-infrastructure-monitoring.md b/troubleshoot/observability/troubleshooting-infrastructure-monitoring.md
@@ -5,11 +5,18 @@ mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/observability-troubleshooting-infrastructure-monitoring.html
 ---
 
-# Troubleshooting infrastructure monitoring
+# Troubleshoot infrastructure monitoring [troubleshooting-infrastructure-monitoring]
 
-% What needs to be done: Align serverless/stateful
+Learn how to troubleshoot common issues on your own or ask for help.
 
-% Use migrated content from existing pages that map to this page:
+* [Understanding "no results found" message](troubleshooting-infrastructure-monitoring/understanding-no-results-found-message.md)
 
-% - [ ] ./raw-migrated-files/observability-docs/observability/troubleshooting-infrastructure-monitoring.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/observability-troubleshooting-infrastructure-monitoring.md
+
+## Elastic Support [troubleshooting-infra-support] 
+
+We offer a support experience unlike any other. Our team of professionals *speak human and code* and love making your day. [Learn more about subscriptions](https://www.elastic.co/subscriptions).
+
+
+## Discussion forum [troubleshooting-infra-forum] 
+
+For other questions and feature requests, visit our [discussion forum](https://discuss.elastic.co/c/observability).
diff --git a/troubleshoot/observability/troubleshooting-infrastructure-monitoring/understanding-no-results-found-message.md b/troubleshoot/observability/troubleshooting-infrastructure-monitoring/understanding-no-results-found-message.md
@@ -4,11 +4,35 @@ mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/observability-handle-no-results-found-message.html
 ---
 
-# Understanding "no results found" message
+# Understand "no results found" message [handle-no-results-found-message]
 
-% What needs to be done: Align serverless/stateful
+To correctly render visualizations in the {{observability}} UI, all metrics used by the UI must be present in the collected data. For a description of these metrics, refer to [Metrics reference](https://www.elastic.co/guide/en/observability/current/metrics-reference.html).
 
-% Use migrated content from existing pages that map to this page:
+There are several reasons why metrics might be missing from the collected data:
 
-% - [ ] ./raw-migrated-files/observability-docs/observability/handle-no-results-found-message.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/observability-handle-no-results-found-message.md
+**The visualization requires a metric that’s not relevant to your monitored hosts**
+
+For example, if you’re only observing Windows hosts, the *load* metric is not collected because *load* is not a Windows concept. In this situation, you can ignore the "no results found" message.
+
+**You may not be collecting all the required metrics**
+
+This could be for any of these reasons:
+
+* The integration that collects the missing metrics is not installed. For example, to collect metrics from your host system, you can use the [System integration](https://docs.elastic.co/en/integrations/system). To fix the problem, install the integration and configure it to send the missing metrics.
+
+  ::::{tip}
+  Follow one of our quickstarts under **Observability** → **Add data** to make sure the correct integrations are installed and all required metrics are collected.
+  ::::
+
+* You are not using the Elastic Distribution of the OpenTelemetry Collector, which automatically maps data to the Elastic Common Schema (ECS) fields expected by the visualization.
+
+  ::::{tip}
+  Follow our OpenTelemetry quickstart under **Observability** → **Add data** to make sure OpenTelemetry data is correctly mapped to ECS-compliant fields.
+  ::::
+
+* You have explicitly chosen not to send these metrics. You may choose to limit the metrics sent to Elastic to save on space and improve cluster performance. For example, the System integration has options to choose which metrics you want to send. You can [edit the integration policy](https://www.elastic.co/guide/en/fleet/current/edit-or-delete-integration-policy.html) to begin collecting the missing metrics. For example:
+
+  :::{image} ../../../images/observability-turn-on-system-metrics.png
+  :alt: Screenshot showing system cpu and diskio metrics selected for collection
+  :class: screenshot
+  :::
