Update H1s to remove duplicates, update link references

vishaangelova · vishaangelova · commit 47f6d621ea3d · 2025-09-17T15:03:58.000+02:00
diff --git a/reference/fleet/debug-standalone-agents.md b/reference/fleet/debug-standalone-agents.md
@@ -12,7 +12,7 @@ When you run standalone {{agent}}s, you are responsible for monitoring the statu
 
 Use the following tips to help identify potential issues.
 
-Also refer to [Troubleshoot common problems](/troubleshoot/ingest/fleet/common-problems.md) for guidance on specific problems.
+Also refer to [](/troubleshoot/ingest/fleet/common-problems.md) for guidance on specific problems.
 
 ::::{note}
 You might need to log in as a root user (or Administrator on Windows) to run these commands.
diff --git a/reference/fleet/install-fleet-managed-elastic-agent.md b/reference/fleet/install-fleet-managed-elastic-agent.md
@@ -99,6 +99,6 @@ If the status hangs at Enrolling, make sure the `elastic-agent` process is runni
 If you run into problems:
 
 * Check the {{agent}} logs. If you use the default policy, agent logs and metrics are collected automatically unless you change the default settings. For more information, refer to [Monitor {{agent}} in {{fleet}}](/reference/fleet/monitor-elastic-agent.md).
-* Refer to the [troubleshooting guide](/troubleshoot/ingest/fleet/common-problems.md).
+* Refer to [](/troubleshoot/ingest/fleet/common-problems.md).
 
 For information about managing {{agent}} in {{fleet}}, refer to [Centrally manage {{agent}}s in {{fleet}}](/reference/fleet/manage-elastic-agents-in-fleet.md).
diff --git a/reference/fleet/install-standalone-elastic-agent.md b/reference/fleet/install-standalone-elastic-agent.md
@@ -223,4 +223,4 @@ Refer to [Installation layout](/reference/fleet/installation-layout.md) for the
 
 Because {{agent}} is installed as an auto-starting service, it will restart automatically if the system is rebooted.
 
-If you run into problems, refer to [Troubleshoot common problems](/troubleshoot/ingest/fleet/common-problems.md).
+If you run into problems, refer to [](/troubleshoot/ingest/fleet/common-problems.md).
diff --git a/reference/fleet/uninstall-elastic-agent.md b/reference/fleet/uninstall-elastic-agent.md
@@ -62,7 +62,7 @@ C:\"Program Files"\Elastic\Agent\elastic-agent.exe uninstall
 :::::::
 Follow the prompts to confirm that you want to uninstall {{agent}}. The command stops and uninstalls any managed programs, such as {{beats}} and {{elastic-endpoint}}, before it stops and uninstalls {{agent}}.
 
-If you run into problems, refer to [Troubleshoot common problems](/troubleshoot/ingest/fleet/common-problems.md).
+If you run into problems, refer to [](/troubleshoot/ingest/fleet/common-problems.md).
 
 If you are using DEB or RPM, you can use the package manager to remove the installed package.
 
diff --git a/solutions/observability/logs/stream-any-log-file.md b/solutions/observability/logs/stream-any-log-file.md
@@ -420,7 +420,7 @@ If you're not seeing your log files in the UI, verify the following in the `elas
 * The path to your logs file under `paths` is correct.
 * Your API key is in `<id>:<key>` format. If not, your API key may be in an unsupported format, and you'll need to create an API key in **Beats** format.
 
-If you're still running into issues, see [{{agent}} troubleshooting](/troubleshoot/ingest/fleet/common-problems.md) and [Configure standalone Elastic Agents](/reference/fleet/configure-standalone-elastic-agents.md).
+If you're still running into issues, see [](/troubleshoot/ingest/fleet/common-problems.md) and [Configure standalone Elastic Agents](/reference/fleet/configure-standalone-elastic-agents.md).
 
 
 ## Next steps [logs-stream-next-steps]
diff --git a/solutions/security/get-started/_snippets/agentless-integrations-faq.md b/solutions/security/get-started/_snippets/agentless-integrations-faq.md
@@ -40,7 +40,7 @@ On the **{{fleet}}** page, the agent associated with an agentless integration ha
     ```
 
 
-For instructions on checking {{fleet}} logs, refer to [{{fleet}} troubleshooting](/troubleshoot/ingest/fleet/common-problems.md).
+For instructions on checking {{fleet}} logs, refer to [](/troubleshoot/ingest/fleet/common-problems.md).
 
 
 ## How do I delete an agentless integration? [_how_do_i_delete_an_agentless_integration]
diff --git a/solutions/security/investigate/add-osquery-response-actions.md b/solutions/security/investigate/add-osquery-response-actions.md
@@ -23,7 +23,7 @@ Osquery Response Actions allow you to add live queries to custom query rules so
 ::::{admonition} Requirements
 * Ensure you have the appropriate [{{stack}} subscription](https://www.elastic.co/pricing) or [{{serverless-short}} project tier](../../../deploy-manage/deploy/elastic-cloud/project-settings.md).
 * The [Osquery manager integration](manage-integration.md) must be installed.
-* {{agent}}'s [status](/reference/fleet/monitor-elastic-agent.md) must be `Healthy`. Refer to [{{fleet}} Troubleshooting](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
+* {{agent}}'s [status](/reference/fleet/monitor-elastic-agent.md) must be `Healthy`. Refer to [](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
 * Your role must have [Osquery feature privileges](/solutions/security/investigate/osquery.md).
 * You can only add Osquery Response Actions to custom query rules.
 
diff --git a/solutions/security/investigate/indicators-of-compromise.md b/solutions/security/investigate/indicators-of-compromise.md
@@ -20,7 +20,7 @@ The Indicators page collects data from enabled threat intelligence feeds and pro
 * In serverless, the Indicators page requires the Security Analytics Complete [project feature](/deploy-manage/deploy/elastic-cloud/project-settings.md)
 * You must have *one* of the following installed on the hosts you want to monitor:
 
-    * **{{agent}}** - Install a [{{fleet}}-managed {{agent}}](/reference/fleet/install-fleet-managed-elastic-agent.md) and ensure the agent’s status is `Healthy`. Refer to [{{fleet}} Troubleshooting](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
+    * **{{agent}}** - Install a [{{fleet}}-managed {{agent}}](/reference/fleet/install-fleet-managed-elastic-agent.md) and ensure the agent’s status is `Healthy`. Refer to [](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
     * **{{filebeat}}** - Install [{{filebeat}}](beats://reference/filebeat/filebeat-installation-configuration.md) version 8.x or later. Earlier {{filebeat}} versions are incompatible with ECS and will prevent indicator data from displaying in the Indicators table.
 
 
diff --git a/solutions/security/investigate/run-osquery-from-alerts.md b/solutions/security/investigate/run-osquery-from-alerts.md
@@ -17,7 +17,7 @@ Run live queries on hosts associated with alerts to learn more about your infras
 
 ::::{admonition} Requirements
 * The [Osquery manager integration](/solutions/security/investigate/manage-integration.md) must be installed.
-* {{agent}}'s [status](/reference/fleet/monitor-elastic-agent.md) must be `Healthy`. Refer to [{{fleet}} Troubleshooting](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
+* {{agent}}'s [status](/reference/fleet/monitor-elastic-agent.md) must be `Healthy`. Refer to [](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
 * Your role must have the appropriate [feature privileges](/solutions/security/investigate/osquery.md#required_osquery-privileges) in {{stack}} or [user role](/deploy-manage/users-roles/cloud-organization/user-roles.md) in {{serverless-short}}.
 
 ::::
diff --git a/solutions/security/investigate/run-osquery-from-investigation-guides.md b/solutions/security/investigate/run-osquery-from-investigation-guides.md
@@ -24,7 +24,7 @@ Detection rule investigation guides suggest steps for triaging, analyzing, and r
 
 ::::{admonition} Requirements
 * The [Osquery manager integration](/solutions/security/investigate/manage-integration.md) must be installed.
-* {{agent}}'s [status](/reference/fleet/monitor-elastic-agent.md) must be `Healthy`. Refer to [{{fleet}} Troubleshooting](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
+* {{agent}}'s [status](/reference/fleet/monitor-elastic-agent.md) must be `Healthy`. Refer to [](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
 * In {{stack}}, your role must have [Osquery feature privileges](/solutions/security/investigate/osquery.md).
 * In {{serverless-short}}, you must have the appropriate user role to use this feature.
 
diff --git a/troubleshoot/deployments/cloud-enterprise/common-issues.md b/troubleshoot/deployments/cloud-enterprise/common-issues.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Common problems
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-issues.html
 applies_to:
@@ -7,8 +8,7 @@ applies_to:
 products:
   - id: cloud-enterprise
 ---
-
-# Common issues [ece-issues]
+# Common problems with {{ece}} [ece-issues]
 
 This set of common symptoms and resolutions can help you to diagnose unexpected behavior with Elastic Cloud Enterprise. You can also refer to the list of product [Limitations and known problems](cloud://release-notes/cloud-enterprise/known-issues.md).
 
diff --git a/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md b/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md
@@ -9,7 +9,7 @@ products:
   - id: cloud-enterprise
 ---
 
-# Troubleshoot deployment health warnings [ece-deployment-no-op]
+# Troubleshoot deployment health warnings on {{ece}} [ece-deployment-no-op]
 
 The {{ece}} **Deployments** page shows the current status of your active deployments. From time to time you may get one or more health warnings, such as the following:
 
@@ -36,5 +36,5 @@ To run a no-op plan:
 If multiple health warnings appear for one of your deployments, check [](/troubleshoot/deployments/cloud-enterprise/common-issues.md) or [contact us](/troubleshoot/index.md#contact-us).
 
 ## Additional resources
-* [Elastic Cloud Hosted deployment health warnings](/troubleshoot/monitoring/deployment-health-warnings.md)
+* [](/troubleshoot/monitoring/deployment-health-warnings.md)
 * [Troubleshooting overview](/troubleshoot/index.md)
diff --git a/troubleshoot/elasticsearch/diagnostic.md b/troubleshoot/elasticsearch/diagnostic.md
@@ -13,7 +13,7 @@ products:
   - id: elasticsearch
 ---
 
-# Capture diagnostics [diagnostic]
+# Capture Elasticsearch diagnostics [diagnostic]
 
 
 The {{es}} [Support Diagnostic](https://github.com/elastic/support-diagnostics) tool captures a point-in-time snapshot of cluster statistics and most settings. It works against all {{es}} versions.
diff --git a/troubleshoot/ingest/fleet/common-problems.md b/troubleshoot/ingest/fleet/common-problems.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Common problems
 mapped_pages:
   - https://www.elastic.co/guide/en/fleet/current/fleet-troubleshooting.html
 applies_to:
@@ -9,7 +10,7 @@ products:
   - id: elastic-agent
 ---
 
-# Common problems [fleet-troubleshooting]
+# Common problems with {{fleet}} and {{elastic-agent}} [fleet-troubleshooting]
 
 We have collected the most common known problems and listed them here. If your problem is not described here, review the open issues in the following GitHub repositories:
 
diff --git a/troubleshoot/ingest/fleet/fleet-elastic-agent.md b/troubleshoot/ingest/fleet/fleet-elastic-agent.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Fleet and Elastic Agent
 mapped_pages:
   - https://www.elastic.co/guide/en/fleet/current/troubleshooting-intro.html
 applies_to:
@@ -9,7 +10,7 @@ products:
   - id: elastic-agent
 ---
 
-# Fleet and Elastic Agent [troubleshooting-intro]
+# Troubleshoot {{fleet}} and {{elastic-agent}} [troubleshooting-intro]
 
 This section provides an [FAQ](frequently-asked-questions.md) and [troubleshooting](common-problems.md) tips to help you resolve common problems with {{fleet}} and {{agent}}.
 
diff --git a/troubleshoot/ingest/logstash/diagnostic.md b/troubleshoot/ingest/logstash/diagnostic.md
@@ -11,7 +11,7 @@ products:
   - id: logstash
 ---
 
-# Capture diagnostics [diagnostic]
+# Capture Logstash diagnostics [diagnostic]
 
 The {{ls}} [Support Diagnostic](https://github.com/elastic/support-diagnostics) tool captures a point-in-time snapshot of its statistics and most settings. It works against all {{ls}} versions.
 
diff --git a/troubleshoot/monitoring/deployment-health-warnings.md b/troubleshoot/monitoring/deployment-health-warnings.md
@@ -10,7 +10,7 @@ products:
   - id: cloud-hosted
 ---
 
-# Troubleshoot deployment health warnings [ec-deployment-no-op]
+# Troubleshoot deployment health warnings on {{ech}} [ec-deployment-no-op]
 
 The {{ecloud}} [Deployments](https://cloud.elastic.co/deployments) page shows the current status of your active deployments. From time to time you may get one or more health warnings, such as the following:
 
@@ -37,5 +37,5 @@ If the warning refers to a system change, check the deployment’s [Activity](/d
 :::
 
 ## Additional resources
-* [Elastic Cloud Enterprise deployment health warnings](/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md)
+* [](/troubleshoot/deployments/cloud-enterprise/deployment-health-warnings.md)
 * [Troubleshooting overview](/troubleshoot/index.md)
diff --git a/troubleshoot/observability/apm.md b/troubleshoot/observability/apm.md
@@ -17,7 +17,7 @@ products:
 
 This section provides solutions to common questions and problems, and processing and performance guidance.
 
-* [Common problems](/troubleshoot/observability/apm/common-problems.md)
+* [](/troubleshoot/observability/apm/common-problems.md)
 * [What happens when APM Server or {{es}} is down?](/troubleshoot/observability/apm/what-happens-when-apm-server-elasticsearch-is-down.md)
 * [APM Server response codes](/troubleshoot/observability/apm/apm-server-response-codes.md)
 * [Processing and performance](/troubleshoot/observability/apm/processing-performance.md)
@@ -31,15 +31,15 @@ For additional help with other APM components, see the links below.
 
 {{agent}}, the Applications UI, and each {{apm-agent}} has its own troubleshooting guide:
 
-* [**{{fleet}} and {{agent}}** troubleshooting](../ingest/fleet/fleet-elastic-agent.md)
-* [**.NET agent** troubleshooting](/troubleshoot/observability/apm-agent-dotnet/apm-net-agent.md)
-* [**Go agent** troubleshooting](/troubleshoot/observability/apm-agent-go/apm-go-agent.md)
-* [**Java agent** troubleshooting](/troubleshoot/observability/apm-agent-java/apm-java-agent.md)
-* [**Node.js agent** troubleshooting](/troubleshoot/observability/apm-agent-nodejs/apm-nodejs-agent.md)
-* [**PHP agent** troubleshooting](/troubleshoot/observability/apm-agent-php/apm-php-agent.md)
-* [**Python agent** troubleshooting](/troubleshoot/observability/apm-agent-python/apm-python-agent.md)
-* [**Ruby agent** troubleshooting](/troubleshoot/observability/apm-agent-ruby/apm-ruby-agent.md)
-* [**RUM agent** troubleshooting](/troubleshoot/observability/apm-agent-rum-js/apm-real-user-monitoring-javascript-agent.md)
+* [](/troubleshoot/ingest/fleet/fleet-elastic-agent.md)
+* [](/troubleshoot/observability/apm-agent-dotnet/apm-net-agent.md)
+* [](/troubleshoot/observability/apm-agent-go/apm-go-agent.md)
+* [](/troubleshoot/observability/apm-agent-java/apm-java-agent.md)
+* [](/troubleshoot/observability/apm-agent-nodejs/apm-nodejs-agent.md)
+* [](/troubleshoot/observability/apm-agent-php/apm-php-agent.md)
+* [](/troubleshoot/observability/apm-agent-python/apm-python-agent.md)
+* [](/troubleshoot/observability/apm-agent-ruby/apm-ruby-agent.md)
+* [](/troubleshoot/observability/apm-agent-rum-js/apm-real-user-monitoring-javascript-agent.md)
 
 
 ## Elastic Support [apm-elastic-support]
diff --git a/troubleshoot/observability/apm/common-problems.md b/troubleshoot/observability/apm/common-problems.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Common problems
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-common-problems.html
   - https://www.elastic.co/guide/en/serverless/current/observability-apm-troubleshooting.html
@@ -11,7 +12,7 @@ products:
   - id: cloud-serverless
 ---
 
-# Common problems [apm-common-problems]
+# Common problems with APM [apm-common-problems]
 
 This section describes common problems you might encounter when using APM Server and the Applications UI in {{kib}}.
 
diff --git a/troubleshoot/security/agentless-integrations.md b/troubleshoot/security/agentless-integrations.md
@@ -1,11 +1,12 @@
 ---
+navigation_title: Troubleshoot agentless integrations
 applies_to:
   stack: all
   serverless:
     security: all
 ---
 
-# Agentless integrations FAQ [agentless-integration-troubleshoot]
+# Troubleshoot agentless integrations [agentless-integration-troubleshoot]
 
 :::{include} /solutions/security/get-started/_snippets/agentless-integrations-faq.md
 :::
diff --git a/troubleshoot/security/elastic-defend.md b/troubleshoot/security/elastic-defend.md
@@ -42,7 +42,7 @@ Common causes of failure in the {{elastic-defend}} integration policy include mi
 * [Resolve a potential system deadlock](../../troubleshoot/security/elastic-defend.md#linux-deadlock) (Linux)
 
 ::::{tip}
-If the {{elastic-defend}} integration policy is not the cause of the `Unhealthy` agent status, refer to [{{fleet}} troubleshooting](../ingest/fleet/common-problems.md) for help with the {{agent}}.
+If the {{elastic-defend}} integration policy is not the cause of the `Unhealthy` agent status, refer to [](/troubleshooting/ingest/fleet/common-problems.md) for help with the {{agent}}.
 ::::
 
 

Original file line number	Diff line number	Diff line change
`@@ -223,4 +223,4 @@ Refer to [Installation layout](/reference/fleet/installation-layout.md) for the`
`223`	`223`
`224`	`224`	`Because {{agent}} is installed as an auto-starting service, it will restart automatically if the system is rebooted.`
`225`	`225`
`226`		`-If you run into problems, refer to [Troubleshoot common problems](/troubleshoot/ingest/fleet/common-problems.md).`
	`226`	`+If you run into problems, refer to [](/troubleshoot/ingest/fleet/common-problems.md).`