Add optional OpAmp step and tip (elastic#3519)

theletterf · alexandra5000 · naemono · commit be7237030534 · 2025-10-28T08:44:09.000-05:00
Fixes elastic#3515 --------- Co-authored-by: Aleksandra Spilkowska <96738481+alexandra5000@users.noreply.github.com>
diff --git a/solutions/_snippets/obs-apm-project.md b/solutions/_snippets/obs-apm-project.md
@@ -1,11 +1,11 @@
-Bring traces, logs, and metrics into Elastic APM to help you troubleshoot and optimize your applications. You can collect this data using OpenTelemetry or APM Server.
+Bring traces, logs, and metrics into Elastic APM to help you troubleshoot and optimize your applications. You can collect this data using OpenTelemetry or {{product.apm-server}}.
 
 :::::{dropdown} Steps for collecting application traces, metrics, and logs
 
 ::::{tab-set}
 :::{tab-item} OpenTelemetry
 
-The [Elastic Distribution of OpenTelemetry (EDOT) SDKs](opentelemetry://reference/edot-sdks/index.md) facilitate the collection of traces, metrics, and logs in OpenTelemetry format into Elastic APM.
+The [{{product.edot-collector}} SDKs](opentelemetry://reference/edot-sdks/index.md) facilitate the collection of traces, metrics, and logs in OpenTelemetry format into Elastic {{product.apm}}.
 
 1. Select **Add data** from the main menu and then select **Application**.
 2. Select **OpenTelemetry**.
@@ -21,4 +21,5 @@ Use the [APM agents](/solutions/observability/apm/apm-agents/index.md) to collec
 3. Select the tab for your language or framework.
 4. Follow the instructions in the tab.
 :::
+::::
 :::::
diff --git a/solutions/observability/get-started.md b/solutions/observability/get-started.md
@@ -15,7 +15,7 @@ products:
 # Get started with Elastic {{observability}} [observability-get-started]
 
 ```{note}
-Use this guide to get started with the Observability Complete feature tier of {{obs-serverless}}. Refer to the [Logs Essentials getting started](/solutions/observability/get-started/logs-essentials.md) docs to get started with {{obs-serverless}} Logs Essentials. The [{{obs-serverless}} feature tiers](/solutions/observability/observability-serverless-feature-tiers.md) page details the difference between tiers.
+Use this guide to get started with the {{observability}} Complete feature tier of {{obs-serverless}}. Refer to the [Logs Essentials getting started](/solutions/observability/get-started/logs-essentials.md) docs to get started with {{obs-serverless}} Logs Essentials. The [{{obs-serverless}} feature tiers](/solutions/observability/observability-serverless-feature-tiers.md) page details the difference between tiers.
 ```
 
 New to Elastic {{observability}}? Discover more about our observability features and how to get started. The following instructions guides you through setting up your first Elastic {{observability}} deployment, collecting data from infrastructure and applications, and exploring your data.
@@ -26,7 +26,7 @@ Learn how to create an {{obs-serverless}} project and use Elastic {{observabilit
 
 :::::::{stepper}
 
-::::::{step} Create an Observability project
+::::::{step} Create an {{observability}} project
 
 :::{include} /solutions/_snippets/obs-serverless-project.md
 :::
@@ -39,52 +39,52 @@ For other types of deployments, refer to [Deploy](/deploy-manage/deploy.md). For
 
 ::::::{step} Collect infrastructure logs and metrics
 
-Bring logs and metrics from your hosts and services into Elastic {{observability}} to monitor the health and performance of your infrastructure. You can collect this data from hosts, containers, Kubernetes, and Cloud services.
+Bring logs and metrics from your hosts and services into Elastic {{observability}} to monitor the health and performance of your infrastructure. You can collect this data from hosts, containers, {{k8s}}, and Cloud services.
 
 :::::{dropdown} Steps for collecting infrastructure logs and metrics
 
 ::::{tab-set}
 :::{tab-item} Hosts
 
-Elastic {{observability}} can collect telemetry data from hosts, containers, and Kubernetes through the EDOT Collector or the Elastic Agent.
+Elastic {{observability}} can collect telemetry data from hosts, containers, and {{k8s}} through the EDOT Collector or the Elastic Agent.
 
 1. Select **Add data** from the main menu and then select **Host**.
 2. Select one of these options:
-    * **OpenTelemetry: Full Observability**: Collect native OpenTelemetry metrics and logs.
-    * **Elastic Agent: Logs & Metrics**: Bring data from Elastic integrations.
+    * **OpenTelemetry: Full {{observability}}**: Collect native OpenTelemetry metrics and logs.
+    * **{{product.elastic-agent}}: Logs & Metrics**: Bring data from Elastic integrations.
 3. Follow the instructions for your platform.
 
-For an overview of the Elastic Distribution of OpenTelemetry Collector, refer to [Elastic Distribution of OpenTelemetry (EDOT)](opentelemetry://reference/index.md).
+For an overview of the {{product.edot-collector}}, refer to [{{edot}} (EDOT)](opentelemetry://reference/index.md).
 
 :::
 
-:::{tab-item} Kubernetes
+:::{tab-item} {{k8s}}
 
-Elastic {{observability}} can collect telemetry data from Kubernetes through the Elastic Distribution of OpenTelemetry Collector or the Elastic Agent.
+Elastic {{observability}} can collect telemetry data from {{k8s}} through the Elastic Distribution of OpenTelemetry Collector or the Elastic Agent.
 
-1. Select **Add data** from the main menu and then select **Kubernetes**.
+1. Select **Add data** from the main menu and then select **{{k8s}}**.
 2. Select one of these options:
-    * **OpenTelemetry: Full Observability**: Collect native OpenTelemetry metrics and logs.
-    * **Elastic Agent: Logs & Metrics**: Bring data from Elastic integrations.
+    * **OpenTelemetry: Full {{observability}}**: Collect native OpenTelemetry metrics and logs.
+    * **{{product.elastic-agent}}: Logs & Metrics**: Bring data from Elastic {{integrations}}.
 3. Follow the instructions for your platform.
 
-For an overview of EDOT, refer to [Elastic Distribution of OpenTelemetry (EDOT)](opentelemetry://reference/index.md).
+For an overview of EDOT, refer to [{{edot}} (EDOT)](opentelemetry://reference/index.md).
 
 :::
 
-:::{tab-item} Integrations
+:::{tab-item} {{integrations}}
 
-Elastic {{observability}} can collect telemetry data from services through Elastic integrations.
+Elastic {{observability}} can collect telemetry data from services through Elastic {{integrations}}.
 
 1. Select **Add data** from the main menu.
-2. In **Search through other ways of ingesting data**, type the name of an integration (for example, NGINX).
+2. In **Search through other ways of ingesting data**, enter the name of an integration (for example, NGINX).
 3. Select the integration you want to add.
 4. Select **Add**.
 :::
 
 :::{tab-item} Cloud
 
-Elastic {{observability}} can collect telemetry data from cloud services through Elastic integrations.
+Elastic {{observability}} can collect telemetry data from cloud services through Elastic {{integrations}}.
 
 1. Select **Add data** from the main menu and then select **Cloud**.
 2. Select your Cloud provider to view the collection of integrations available for that provider.
@@ -143,7 +143,7 @@ After you've onboarded your data, you can explore it in the following Elastic {{
 
 ::::::{step} Create your first dashboards
 
-Elastic provides a wide range of prebuilt dashboards for visualizing observability data from a variety of sources. These dashboards are loaded automatically when you install [Elastic integrations](https://docs.elastic.co/integrations). You can also create new dashboards and visualizations based on your data views.
+Elastic provides a wide range of prebuilt dashboards for visualizing observability data from a variety of sources. These dashboards are loaded automatically when you install [Elastic {{integrations}}](https://docs.elastic.co/integrations). You can also create new dashboards and visualizations based on your data views.
 
 To create a new dashboard, select **Create Dashboard** and begin adding visualizations. You can create charts, graphs, maps, tables, and other types of visualizations from your data, or you can add visualizations from the library. You can also add other types of panels, such as filters and controls.
 
@@ -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 [](/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) for more information.
 
 {{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.
 
@@ -171,12 +171,12 @@ Quickstarts are compact hands-on guides that help you experiment with {{observab
 
 [Browse the Elastic {{observability}} quickstarts](/solutions/observability/get-started/quickstarts.md) to get started with specific use cases.
 
-### Observability integrations
+### {{observability}} integrations
 
 Many [{{observability}} integrations](https://www.elastic.co/integrations/data-integrations?solution=observability) are available to collect and process your data. Refer to [Elastic integrations](https://www.elastic.co/docs/reference/integrations) for more information.
 
 ### Other resources
 
 * [What's Elastic {{observability}}](/solutions/observability/get-started/what-is-elastic-observability.md)
-* [What's new in Elastic Stack](/release-notes/elastic-observability/index.md)
+* [What's new in {{product.elastic-stack}}](/release-notes/elastic-observability/index.md)
 * [{{obs-serverless}} billing dimensions](/deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md)
diff --git a/solutions/observability/get-started/opentelemetry/quickstart/ech/docker.md b/solutions/observability/get-started/opentelemetry/quickstart/ech/docker.md
@@ -13,7 +13,7 @@ products:
   - id: edot-collector
 ---
 
-# Quickstart for Docker on Elastic Cloud Hosted
+# Quickstart for Docker on {{product.cloud-hosted}}
 
 Learn how to set up the EDOT Collector and EDOT SDKs in a Docker environment with {{ech}} (ECH) to collect host metrics, logs, and application traces.
 
@@ -108,6 +108,10 @@ instrument your target applications following the setup instructions:
 
    Configure your SDKs to send the data to the local EDOT Collector using OTLP/gRPC (`http://localhost:4317`) or OTLP/HTTP (`http://localhost:4318`).
 
+:::{tip}
+Activate Central Configuration to configure your EDOT SDKs from within {{product.kibana}}. Refer to [EDOT SDKs Central Configuration](opentelemetry://reference/central-configuration.md).
+:::
+
 ::::
 
 ::::{step} Install the content packs
diff --git a/solutions/observability/get-started/opentelemetry/quickstart/ech/hosts_vms.md b/solutions/observability/get-started/opentelemetry/quickstart/ech/hosts_vms.md
@@ -122,6 +122,10 @@ instrument your target applications following the setup instructions:
 - [Python](elastic-otel-python://reference/edot-python/setup/index.md)
 
 Configure your SDKs to send the data to the local EDOT Collector using OTLP/gRPC (`http://localhost:4317`) or OTLP/HTTP (`http://localhost:4318`).
+
+:::{tip}
+Activate Central Configuration to configure your EDOT SDKs from within {{product.kibana}}. Refer to [EDOT SDKs Central Configuration](opentelemetry://reference/central-configuration.md).
+:::
 :::::
 
 :::::{step} Install the content pack
diff --git a/solutions/observability/get-started/opentelemetry/quickstart/self-managed/hosts_vms.md b/solutions/observability/get-started/opentelemetry/quickstart/self-managed/hosts_vms.md
@@ -120,6 +120,9 @@ instrument your target applications following the setup instructions:
 
 Configure your SDKs to send the data to the local EDOT Collector using OTLP/gRPC (`http://localhost:4317`) or OTLP/HTTP (`http://localhost:4318`).
 
+:::{tip}
+Activate Central Configuration to configure your EDOT SDKs from within {{product.kibana}}. Refer to [EDOT SDKs Central Configuration](opentelemetry://reference/central-configuration.md).
+:::
 :::::
 
 :::::{step} Install the content pack
diff --git a/solutions/observability/get-started/quickstart-monitor-your-application-performance.md b/solutions/observability/get-started/quickstart-monitor-your-application-performance.md
@@ -86,9 +86,10 @@ If your application runs on Kubernetes, the OpenTelemetry operator automatically
    - [PHP](elastic-otel-php://reference/edot-php/setup/index.md)
    - [Python](elastic-otel-python://reference/edot-python/setup/index.md)
 4. Configure your EDOT SDK to send data to the [Managed OTLP endpoint](opentelemetry://reference/motlp.md). The **OpenTelemetry** tab provides the required configuration values.
+5. (Optional) Activate Central Configuration to configure your EDOT SDKs from within {{product.kibana}}. Refer to [EDOT SDKs Central Configuration](opentelemetry://reference/central-configuration.md).
 
 :::{note}
-If your application runs on Kubernetes, the OpenTelemetry operator automatically instruments your application, provided you've added language-specific annotations. Refer to [Auto-instrument applications](/solutions/observability/get-started/opentelemetry/quickstart/serverless/k8s.md).
+If your application runs on {{k8s}}, the OpenTelemetry operator automatically instruments your application, provided you've added language-specific annotations. Refer to [Auto-instrument applications](/solutions/observability/get-started/opentelemetry/quickstart/serverless/k8s.md).
 :::
 
 ::::
