Updates H1s for part of Solutions section (#2990)

natasha-moore-elastic · florent-leborgne · web-flow · commit de9b7d97f6bd · 2025-09-17T16:46:01.000Z
Updates H1s for part of the Solutions section, including links to those
pages.

---------

Co-authored-by: florent-leborgne &lt;florent.leborgne@elastic.co&gt;
diff --git a/solutions/observability/apm/configure-elasticsearch-output.md b/solutions/observability/apm/configure-elasticsearch-output.md
@@ -9,7 +9,7 @@ products:
   - id: apm
 ---
 
-# Configure the Elasticsearch output [apm-elasticsearch-output]
+# Configure the Elasticsearch output for APM Server[apm-elasticsearch-output]
 
 ::::{note}
 ![supported deployment methods](/solutions/images/observability-binary-yes-fm-no.svg "")
diff --git a/solutions/observability/get-started.md b/solutions/observability/get-started.md
@@ -153,7 +153,7 @@ For more information about creating dashboards, refer to [Create your first dash
 
 ::::::{step} Set up alerts and SLOs
 
-Elastic {{observability}} lets you define rules of different types which detect complex conditions and trigger relevant actions. {{observability}} can send alerts to email, Slack, and other third-party systems. Refer to [Create and manage rules](/solutions/observability/incident-management/create-manage-rules.md) to get started.
+Elastic {{observability}} lets you define rules of different types which detect complex conditions and trigger relevant actions. {{observability}} can send alerts to email, Slack, and other third-party systems. Refer to [](/solutions/observability/incident-management/create-manage-rules.md) to get started.
 
 {{observability}} also lets you define Service Level Objectives (SLOs) to set clear, measurable targets for your service performance, based on factors like availability, response times, error rates, and other key metrics. Refer to [Create and manage SLOs](/solutions/observability/incident-management/service-level-objectives-slos.md) to get started.
 
diff --git a/solutions/observability/get-started/logs-essentials.md b/solutions/observability/get-started/logs-essentials.md
@@ -113,7 +113,7 @@ For more information about creating dashboards, refer to [Create your first dash
 
 ::::::{step} Set up alerts
 
-Elastic {{observability}} lets you define rules of different types which detect complex conditions and trigger relevant actions. Elastic {{observability}} can send alerts to email, Slack, and other third-party systems. Refer to [Create and manage rules](/solutions/observability/incident-management/create-manage-rules.md) to get started.
+Elastic {{observability}} lets you define rules of different types which detect complex conditions and trigger relevant actions. Elastic {{observability}} can send alerts to email, Slack, and other third-party systems. Refer to [](/solutions/observability/incident-management/create-manage-rules.md) to get started.
 
 ::::::
 
diff --git a/solutions/observability/incident-management/alerting.md b/solutions/observability/incident-management/alerting.md
@@ -35,5 +35,5 @@ You can filter this table by alert status or time period, customize the visible
 
 ## Next steps [observability-alerting-next-steps]
 
-* [Create and manage rules](/solutions/observability/incident-management/create-manage-rules.md)
+* [](/solutions/observability/incident-management/create-manage-rules.md)
 * [View alerts](/solutions/observability/incident-management/view-alerts.md)
diff --git a/solutions/observability/incident-management/configure-case-settings.md b/solutions/observability/incident-management/configure-case-settings.md
@@ -5,9 +5,10 @@ mapped_pages:
 products:
   - id: observability
   - id: cloud-serverless
+navigation_title: Configure case settings
 ---
 
-# Configure case settings [manage-cases-settings]
+# Configure case settings for Elastic {{observability}} [manage-cases-settings]
 
 % Serverless only for the following role, does stateful require a special role?
 
diff --git a/solutions/observability/incident-management/create-manage-cases.md b/solutions/observability/incident-management/create-manage-cases.md
@@ -78,7 +78,7 @@ There is a 10 MiB size limit for images. For all other MIME types, the limit is
 
 To send a case to an external system, click the ![push](/solutions/images/serverless-importAction.svg "") button in the *External incident management system* section of the individual case page. This information is not sent automatically. If you make further changes to the shared case fields, you should push the case again.
 
-For more information about configuring connections to external incident management systems, refer to [Configure case settings](/solutions/observability/incident-management/configure-case-settings.md).
+For more information about configuring connections to external incident management systems, refer to [](/solutions/observability/incident-management/configure-case-settings.md).
 
 
 ## Manage existing cases [observability-create-a-new-case-manage-existing-cases]
diff --git a/solutions/observability/incident-management/create-manage-rules.md b/solutions/observability/incident-management/create-manage-rules.md
@@ -5,9 +5,10 @@ mapped_pages:
 products:
   - id: observability
   - id: cloud-serverless
+navigation_title: Create and manage rules
 ---
 
-# Create and manage rules [observability-create-manage-rules]
+# Create and manage rules for Elastic {{observability}} [observability-create-manage-rules]
 
 ::::{note}
 
diff --git a/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md b/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md
@@ -22,7 +22,7 @@ For more information, refer to the following links:
 * [View infrastructure metrics by resource type](/solutions/observability/infra-and-hosts/view-infrastructure-metrics-by-resource-type.md): Use the **Inventory page** to get a metrics-driven view of your infrastructure grouped by resource type.
 * [Analyze and compare hosts](/solutions/observability/infra-and-hosts/analyze-compare-hosts.md): Use the **Hosts** page to get a metrics-driven view of your infrastructure backed by an easy-to-use interface called Lens.
 * [Detect metric anomalies](/solutions/observability/infra-and-hosts/detect-metric-anomalies.md): Detect and inspect memory usage and network traffic anomalies for hosts and Kubernetes pods.
-* [Configure settings](/solutions/observability/infra-and-hosts/configure-settings.md): Learn how to configure infrastructure UI settings.
+* [](/solutions/observability/infra-and-hosts/configure-settings.md): Learn how to configure infrastructure UI settings.
 * [Metrics reference](/reference/data-analysis/observability/index.md): Learn about key metrics used for infrastructure monitoring.
 * [Infrastructure app fields](/reference/observability/fields-and-object-schemas.md): Learn about the fields required to display data in the Infrastructure UI.
 
diff --git a/solutions/observability/infra-and-hosts/configure-settings.md b/solutions/observability/infra-and-hosts/configure-settings.md
@@ -5,9 +5,10 @@ mapped_pages:
 products:
   - id: observability
   - id: cloud-serverless
+navigation_title: Configure settings
 ---
 
-# Configure settings [observability-configure-intra-settings]
+# Configure infrastructure and host metrics settings [observability-configure-intra-settings]
 
 ::::{note}
 
diff --git a/solutions/observability/uptime/configure-settings.md b/solutions/observability/uptime/configure-settings.md
@@ -6,9 +6,10 @@ applies_to:
   serverless: unavailable
 products:
   - id: observability
+navigation_title: Configure settings
 ---
 
-# Configure settings [configure-uptime-settings]
+# Configure Uptime monitoring settings [configure-uptime-settings]
 
 ::::{admonition} Deprecated in 8.15.0.
 :class: warning
diff --git a/solutions/security/dashboards.md b/solutions/security/dashboards.md
@@ -9,9 +9,10 @@ applies_to:
 products:
   - id: security
   - id: cloud-serverless
+navigation_title: Dashboards
 ---
 
-# Dashboards
+# {{elastic-sec}} dashboards
 
 The {{security-app}}'s default dashboards provide useful visualizations of your security environment. To view them in {{elastic-sec}}, select **Dashboards** from the navigation menu. From the Dashboards page, you can access the default dashboards, as well as create and access custom dashboards.
 
diff --git a/solutions/security/get-started/elastic-security-ui.md b/solutions/security/get-started/elastic-security-ui.md
@@ -107,7 +107,7 @@ Expand this section to access the following dashboards, which provide interactiv
 - Entity Analytics
 - Data Quality.
 
-You can also create and view custom dashboards. Refer to [Dashboards](/solutions/security/dashboards.md) for more information.
+You can also create and view custom dashboards. Refer to [](/solutions/security/dashboards.md) for more information.
 
 
 ### Rules [_rules]
diff --git a/solutions/security/investigate/configure-case-settings.md b/solutions/security/investigate/configure-case-settings.md
@@ -9,9 +9,10 @@ applies_to:
 products:
   - id: security
   - id: cloud-serverless
+navigation_title: Configure case settings
 ---
 
-# Configure case settings [security-cases-settings]
+# Configure case settings for {{elastic-sec}} [security-cases-settings]
 
 This page explains how to change case closure options, add custom fields, templates, and connectors for external incident management systems, and create custom observable types.
 First, find **Cases** in the navigation menu or search for `Security/Cases` by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md), then click **Settings**. In {{serverless-short}}, you can access case settings in an {{elastic-sec}} project, go to **Cases** → **Settings**.
diff --git a/troubleshoot/observability/apm/apm-server-performance-diagnostic.md b/troubleshoot/observability/apm/apm-server-performance-diagnostic.md
@@ -39,7 +39,7 @@ See [{{metricbeat}} documentation](beats://reference/metricbeat/exported-fields-
 
 One likely cause of excessive indexing pressure or rejected requests is undersized {{es}}. To mitigate this, follow the guidance in [Rejected requests](../../elasticsearch/rejected-requests.md).
 
-(Not recommended) If scaling {{es}} resources up is not an option, you can adjust the `flush_bytes`, `flush_interval`, `max_retries` and `timeout` settings described in [Configure the Elasticsearch output](/solutions/observability/apm/configure-elasticsearch-output.md) to reduce APM Server indexing pressure. However, consider that increasing number of buffered documents and/or reducing retries may lead to a higher rate of dropped APM events. Down below a custom configuration example is listed where the number of default buffered documents is roughly doubled while {{es}} indexing retries are decreased simultaneously. This configuration provides a generic example and might not be applicable to your situation. Try adjusting the settings further to see what works for you.
+(Not recommended) If scaling {{es}} resources up is not an option, you can adjust the `flush_bytes`, `flush_interval`, `max_retries` and `timeout` settings described in [](/solutions/observability/apm/configure-elasticsearch-output.md) to reduce APM Server indexing pressure. However, consider that increasing number of buffered documents and/or reducing retries may lead to a higher rate of dropped APM events. Down below a custom configuration example is listed where the number of default buffered documents is roughly doubled while {{es}} indexing retries are decreased simultaneously. This configuration provides a generic example and might not be applicable to your situation. Try adjusting the settings further to see what works for you.
 
 ```yaml
 output.elasticsearch:
