fix formatting

mdbirnstiehl · mdbirnstiehl · commit 9e7a2e777830 · 2025-02-25T14:41:59.000-06:00
diff --git a/solutions/observability/apps/apm-agent-explorer.md b/solutions/observability/apps/apm-agent-explorer.md
@@ -1,15 +1,14 @@
 ---
-navigation_title: "Identify deployment details for APM agents"
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-agent-explorer.html
+applies_to:
+  stack: all
 ---
 
-
-
 # APM Agent explorer [apm-agent-explorer]
 
 
-::::{warning}
+::::{important}
 This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
 ::::
 
diff --git a/solutions/observability/apps/applications-ui-settings.md b/solutions/observability/apps/applications-ui-settings.md
@@ -19,6 +19,9 @@ You can adjust Application settings to fine-tune your experience in the Applicat
 
 
 ## General settings [observability-apm-kibana-settings-general-settings]
+```{applies_to}
+stack: ga 9.1
+```
 
 To change APM settings, select **Settings** from any **Applications** page. The following settings are available.
 
diff --git a/solutions/observability/apps/collect-application-data.md b/solutions/observability/apps/collect-application-data.md
@@ -11,7 +11,7 @@ mapped_urls:
 
 ::::{note}
 
-**For Observability serverless projects**, the **Admin** role or higher is required to send APM data to Elastic. To learn more, refer to [Assign user roles and privileges](../../../deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles).
+**For Observability Serverless projects**, the **Admin** role or higher is required to send APM data to Elastic. To learn more, refer to [Assign user roles and privileges](../../../deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles).
 
 ::::
 
diff --git a/solutions/observability/apps/configure-individual-browser-monitors.md b/solutions/observability/apps/configure-individual-browser-monitors.md
@@ -19,7 +19,7 @@ After [writing synthetic journeys](../../../solutions/observability/apps/write-s
 
 You’ll need to set a few configuration options:
 
-* **Give your monitor a name.** Provide a human readable name and a unique ID for the monitor. This will appear in {{kib}} or your Observability serverless project where you can view and manage monitors after they’re created.
+* **Give your monitor a name.** Provide a human readable name and a unique ID for the monitor. This will appear in {{kib}} or your Observability Serverless project where you can view and manage monitors after they’re created.
 * **Set the schedule.** Specify the interval at which your tests will run.
 * **Specify where the monitors should run.** You can run monitors on Elastic’s global managed testing infrastructure or [create a {{private-location}}](../../../solutions/observability/apps/monitor-resources-on-private-networks.md) to run monitors from your own premises.
 * **Set other options as needed.** There are several other options you can set to customize your implementation including params, tags, screenshot options, throttling options, and more.
diff --git a/solutions/observability/apps/configure-lightweight-monitors.md b/solutions/observability/apps/configure-lightweight-monitors.md
@@ -17,7 +17,7 @@ Lightweight monitors can be configured using either the [Synthetics UI](../../..
 
 ## Synthetics UI [synthetics-lightweight-ui]
 
-To use the UI, go to the Synthetics UI in {{kib}} or in your Observability serverless project to create and configure monitors. For step-by-step instructions, refer to [Use the Synthetics UI](../../../solutions/observability/apps/create-monitors-in-synthetics-app.md).
+To use the UI, go to the Synthetics UI in {{kib}} or in your Observability Serverless project to create and configure monitors. For step-by-step instructions, refer to [Use the Synthetics UI](../../../solutions/observability/apps/create-monitors-in-synthetics-app.md).
 
 :::{image} ../../../images/observability-synthetics-get-started-ui-lightweight.png
 :alt: Synthetics Create monitor UI
@@ -130,7 +130,7 @@ $$$monitor-service_name$$$
 **`service.name`**
 :   Type: [string](../../../solutions/observability/apps/configure-lightweight-monitors.md#synthetics-lightweight-data-string)
 
-    APM service name for this monitor. Corresponds to the `service.name` ECS field. Set this when monitoring an app that is also using APM to enable integrations between Synthetics and APM data in Kibana or your Observability serverless project.
+    APM service name for this monitor. Corresponds to the `service.name` ECS field. Set this when monitoring an app that is also using APM to enable integrations between Synthetics and APM data in Kibana or your Observability Serverless project.
 
 
 $$$monitor-enabled$$$
diff --git a/solutions/observability/apps/cross-cluster-search-with-application-data.md b/solutions/observability/apps/cross-cluster-search-with-application-data.md
@@ -37,8 +37,7 @@ There are two ways to edit the default {{data-source}}:
 * In the Applications UI — Find **Applications** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Go to **Settings** → **Indices** and change all `xpack.apm.indices.*` values to include remote clusters.
 * In `kibana.yml` — Update the [`xpack.apm.indices.*`](asciidocalypse://docs/kibana/docs/reference/configuration-reference/apm-settings.md) configuration values to include remote clusters.
 
-::::{admonition} Exclude data tiers from search
-:class: tip
+::::{tip}
 
 In a cross-cluster search (CCS) environment, it’s possible for different clusters to serve different data tiers in responses. If one of the requested clusters responds slowly, it can cause a timeout at the proxy after 320 seconds. This results in 502 Bad Gateway server error responses presented as failure toast messages in the UI, and no data loaded.
 
diff --git a/solutions/observability/apps/elastic-apm-agents.md b/solutions/observability/apps/elastic-apm-agents.md
@@ -11,7 +11,7 @@ navigation_title: "APM agents"
 
 ::::{note}
 
-**For Observability serverless projects**, the **Admin** role or higher is required to use APM agents. To learn more, refer to [Assign user roles and privileges](../../../deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles).
+**For Observability Serverless projects**, the **Admin** role or higher is required to use APM agents. To learn more, refer to [Assign user roles and privileges](../../../deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles).
 
 ::::
 
diff --git a/solutions/observability/apps/explore-mobile-sessions-with-discover.md b/solutions/observability/apps/explore-mobile-sessions-with-discover.md
@@ -1,6 +1,8 @@
 ---
 mapped_pages:
   - https://www.elastic.co/guide/en/observability/current/apm-mobile-session-explorer.html
+applies_to:
+  stack: all
 ---
 
 # Explore mobile sessions with Discover [apm-mobile-session-explorer]
@@ -33,19 +35,19 @@ Copy this value and open the Discover page:
 :class: screenshot
 :::
 
-set the data view. `APM` selected in the example:
+Set the data view. `APM` selected in the example:
 
 :::{image} ../../../images/observability-mobile-session-explorer-apm.png
 :alt: Example view of Explorer selecting APM data view
 :class: screenshot
 :::
 
-filter using the `session.id`: `session.id: "<copied session id guid>"`:
+Filter using the `session.id`: `session.id: "<copied session id guid>"`:
 
 :::{image} ../../../images/observability-mobile-session-filter-discover.png
 :alt: Filter Explor using session.id
 :class: screenshot
 :::
 
-explore all the documents associated with that session id including crashes, lifecycle events, network requests, errors, and other custom events!
+Explore all the documents associated with that session id including crashes, lifecycle events, network requests, errors, and other custom events!
 
diff --git a/solutions/observability/apps/find-transaction-latency-failure-correlations.md b/solutions/observability/apps/find-transaction-latency-failure-correlations.md
@@ -19,8 +19,6 @@ To find correlations:
 
 Select a service on the **Services** page in the Applications UI then select a transaction group from the **Transactions** tab.
 
-Active queries *are* applied to correlations.
-
 
 :::
 
@@ -32,12 +30,14 @@ Active queries *are* applied to correlations.
 3. Select the **Transactions** tab.
 4. Select a transaction group in the **Transactions** table.
 
-Active queries *are* applied to correlations.
-
 :::
 
 ::::
 
+:::: {note}
+Active queries *are* applied to correlations.
+::::
+
 
 ## Find high transaction latency correlations [observability-apm-find-transaction-latency-and-failure-correlations-find-high-transaction-latency-correlations]
 
diff --git a/solutions/observability/apps/infrastructure.md b/solutions/observability/apps/infrastructure.md
@@ -6,8 +6,7 @@ mapped_urls:
 
 # Infrastructure [observability-apm-infrastructure]
 
-::::{admonition} Applications UI Infrastructure is in beta
-:class: important
+::::{important}
 
 The Applications UI Infrastructure functionality is in beta and is subject to change. The design and code is less mature than official generally available features and is being provided as-is with no warranties.
 
@@ -28,8 +27,8 @@ The **Infrastructure** tab provides information about the containers, pods, and
 
 IT ops and software reliability engineers (SREs) can use this tab to quickly find a service’s underlying infrastructure resources when debugging a problem. Knowing what infrastructure is related to a service allows you to remediate issues by restarting, killing hanging instances, changing configuration, rolling back deployments, scaling up, scaling out, and so on.
 
-::::{admonition} Why is the infrastructure tab empty?
-:class: tip
+::::{tip}
+**Why is the infrastructure tab empty?**
 
 If there is no data in the Application UI’s infrastructure tab for a selected service, you can read more about why this happens and how to fix it in the [troubleshooting docs](../../../troubleshoot/observability/apm/common-problems.md#troubleshooting-apm-infra-data).
 
diff --git a/solutions/observability/apps/monitor-resources-on-private-networks.md b/solutions/observability/apps/monitor-resources-on-private-networks.md
@@ -50,9 +50,9 @@ By default {{private-location}}s are configured to allow two simultaneous browse
 ::::
 
 
-## Connect to the {{stack}} or your Observability serverless project [synthetics-private-location-connect]
+## Connect to the {{stack}} or your Observability Serverless project [synthetics-private-location-connect]
 
-After setting up {{fleet}}, you’ll connect {{fleet}} to the {{stack}} or your Observability serverless project and enroll an {{agent}} in {{fleet}}.
+After setting up {{fleet}}, you’ll connect {{fleet}} to the {{stack}} or your Observability Serverless project and enroll an {{agent}} in {{fleet}}.
 
 Elastic provides Docker images that you can use to run {{fleet}} and an {{agent}} more easily. For monitors running on {{private-location}}s, you *must* use the `elastic-agent-complete` Docker image to create a self-hosted {{agent}} node. The standard {{ecloud}} or self-hosted {{agent}} will not work.
 
diff --git a/solutions/observability/apps/observe-lambda-functions.md b/solutions/observability/apps/observe-lambda-functions.md
@@ -34,11 +34,6 @@ Cold start is also displayed in the trace waterfall, where you can drill-down in
 
 The [latency correlations](../../../solutions/observability/apps/find-transaction-latency-failure-correlations.md) feature can be used to visualize the impact of Lambda cold starts on latency—​just select the `faas.coldstart` field.
 
-:::{image} ../../../images/observability-lambda-correlations.png
-:alt: lambda correlations example
-:class: screenshot
-:::
-
 
 ## AWS Lambda function grouping [apm-lambda-service-config]
 
diff --git a/solutions/observability/apps/services.md b/solutions/observability/apps/services.md
@@ -29,16 +29,14 @@ Want to monitor service logs without instrumenting all your services? Learn abou
 
 ## Service groups [service-groups]
 
-::::{admonition} Required role
-:class: note
+::::{note}
 
-For Observability serverless projects, the **Editor** role or higher is required to create and manage service groups. To learn more, refer to [Assign user roles and privileges](../../../deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles).
+For Observability Serverless projects, the **Editor** role or higher is required to create and manage service groups. To learn more, refer to [Assign user roles and privileges](../../../deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles).
 
 ::::
 
 
-::::{admonition} Service grouping is in beta
-:class: important
+::::{important}
 
 The Service grouping functionality is in beta and is subject to change. The design and code is less mature than official generally available features and is being provided as-is with no warranties.
 
diff --git a/solutions/observability/apps/track-deployments-with-annotations.md b/solutions/observability/apps/track-deployments-with-annotations.md
@@ -8,10 +8,9 @@ navigation_title: "Track deployments with annotations"
 
 # Track deployments with annotations [apm-transactions-annotations]
 
-::::{admonition} Required role
-:class: note
+::::{note}
 
-For Observability serverless projects, the **Admin** role or higher is required to create and manage annotations. To learn more, refer to [Assign user roles and privileges](../../../deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles).
+**For Observability Serverless projects**, the **Admin** role or higher is required to create and manage annotations. To learn more, refer to [Assign user roles and privileges](../../../deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles).
 
 ::::
 
diff --git a/solutions/observability/apps/transaction-sampling.md b/solutions/observability/apps/transaction-sampling.md
@@ -95,14 +95,15 @@ Refer to the documentation of your favorite OpenTelemetry agent or SDK for more
 % Stateful only for tail-based sampling
 
 ## Tail-based sampling [apm-tail-based-sampling]
+```{applies_to}
+stack: all
+```
 
-::::{admonition} Support for tail-based sampling
-:class: note
+::::{note}
+**Support for tail-based sampling**
 
 Tail-based sampling is only supported when writing to {{es}}. If you are using a different [output](../../../solutions/observability/apps/configure-output.md), tail-based sampling is *not* supported.
 
-Tail-based sampling is *not* compatible with [{{serverless-full}}](https://docs.elastic.co/serverless).
-
 ::::
 
 
diff --git a/solutions/observability/apps/use-synthetics-cli.md b/solutions/observability/apps/use-synthetics-cli.md
@@ -155,7 +155,7 @@ If the journey contains external NPM packages other than the `@elastic/synthetic
 
 
 `--url <string>`
-:   The URL for the deployment or Observability serverless project to which you want to upload the monitors.
+:   The URL for the deployment or Observability Serverless project to which you want to upload the monitors.
 
     This can also be set in the configuration file using [`project.url`](../../../solutions/observability/apps/configure-synthetics-projects.md#synthetics-configuration-project). The value defined via the CLI will take precedence.
 
@@ -267,7 +267,7 @@ Run `npx @elastic/synthetics locations` with no flags to list all the available
 To list both locations on Elastic’s global managed infrastructure and {{private-locations}}, include:
 
 `--url <string>`
-:   The URL for the {{kib}} deployment or Observability serverless project from which to fetch all available public and {{private-location}}s.
+:   The URL for the {{kib}} deployment or Observability Serverless project from which to fetch all available public and {{private-location}}s.
 
 `--auth <string>`
 :   API key used for [authentication](../../../deploy-manage/api-keys/elasticsearch-api-keys.md).
diff --git a/solutions/observability/apps/work-with-params-secrets.md b/solutions/observability/apps/work-with-params-secrets.md
@@ -29,7 +29,7 @@ The values in the configuration file are read in the following order:
 
 1. **Global parameters in an Observability project**: The *Global parameters* set using the UI are read first.
 2. **Configuration file**: Then the *Global parameters* are merged with any parameters defined in a configuration file. If a parameter is defined in both the Observability UI **and** a Synthetics project configuration file, the value in the configuration file will be used.
-3. **CLI**: Then the parameters defined in the configuration are merged with any parameters passed to the CLI `--params` argument. If a parameter is defined in a Synthetics project configuration file **and** using the CLI argument, the value defined using the CLI will be used. When running a script using the CLI, *Global parameters* defined in {{kib}} or the Observability serverless project have no impact on the test because it won’t have access to {{kib}} or the Observability project.
+3. **CLI**: Then the parameters defined in the configuration are merged with any parameters passed to the CLI `--params` argument. If a parameter is defined in a Synthetics project configuration file **and** using the CLI argument, the value defined using the CLI will be used. When running a script using the CLI, *Global parameters* defined in {{kib}} or the Observability Serverless project have no impact on the test because it won’t have access to {{kib}} or the Observability project.
 
 
 ### Global parameters in your Observability project [observability-synthetics-params-secrets-global-parameters-in-your-observability-project]
diff --git a/solutions/observability/apps/write-synthetic-test.md b/solutions/observability/apps/write-synthetic-test.md
@@ -42,7 +42,7 @@ The synthetics agent exposes an API for creating and running tests, including:
 :   Runs a provided function after a single `journey` has completed. Takes one parameter: a `callback` (function). Learn more in [Set up and remove a global state](../../../solutions/observability/apps/write-synthetic-test.md#before-after).
 
 `monitor`
-:   The `monitor.use` method allows you to determine a monitor’s configuration on a journey-by-journey basis. If you want two journeys to create monitors with different intervals, for example, you should call `monitor.use` in each of them and set the `schedule` property to different values in each. Note that this is only relevant when using the `push` command to create monitors in {{kib}} an Observability serverless project. Learn more in [Configure individual monitors](../../../solutions/observability/apps/configure-individual-browser-monitors.md).
+:   The `monitor.use` method allows you to determine a monitor’s configuration on a journey-by-journey basis. If you want two journeys to create monitors with different intervals, for example, you should call `monitor.use` in each of them and set the `schedule` property to different values in each. Note that this is only relevant when using the `push` command to create monitors in {{kib}} an Observability Serverless project. Learn more in [Configure individual monitors](../../../solutions/observability/apps/configure-individual-browser-monitors.md).
 
 
 ## Create a journey [synthetics-create-journey]
diff --git a/solutions/observability/get-started.md b/solutions/observability/get-started.md
@@ -24,7 +24,7 @@ Learn about key features available to help you get value from your observability
 
 ## Get started with your use case [get-started-with-use-case]
 
-Learn how to spin up a deployment on {{ech}} or create an Observability serverless project and use Elastic Observability to gain deeper insight into the behavior of your applications and systems.
+Learn how to spin up a deployment on {{ech}} or create an Observability Serverless project and use Elastic Observability to gain deeper insight into the behavior of your applications and systems.
 
 :::{image} ../../images/observability-get-started.svg
 :alt: get started
