Replace diagram and rewrite (#2260)

Fixes #2145
Fixes #2196

Author: theletterf

solutions/images/observability-apm-otel-distro2.png

@@ -11,34 +11,22 @@ products:
   - id: observability
 ---
 
-# Use OpenTelemetry with APM [apm-open-telemetry]
-
-::::{note}
-For a complete overview of using OpenTelemetry with Elastic, explore [**Elastic Distributions of OpenTelemetry**](opentelemetry://reference/index.md).
-::::
+# Use OpenTelemetry with APM [apm-otel-elastic-distros]
 
 [OpenTelemetry](https://opentelemetry.io/docs/concepts/what-is-opentelemetry/) is a set of APIs, SDKs, tooling, and integrations that enable the capture and management of telemetry data from your services and applications.
 
-Elastic integrates with OpenTelemetry, allowing you to reuse your existing instrumentation to easily send observability data to the {{stack}}. There are several ways to integrate OpenTelemetry with the {{stack}}:
-
-* [Elastic Distributions of OpenTelemetry language SDKs](/solutions/observability/apm/use-opentelemetry-with-apm.md#apm-otel-elastic-distros)
-* [Upstream OpenTelemetry API/SDK + Elastic APM agent](/solutions/observability/apm/use-opentelemetry-with-apm.md#apm-otel-api-sdk-elastic-agent)
-* [Upstream OpenTelemetry Collector and language SDKs](/solutions/observability/apm/use-opentelemetry-with-apm.md#apm-otel-upstream)
-* [AWS Lambda Collector exporter](/solutions/observability/apm/use-opentelemetry-with-apm.md#apm-otel-lambda)
-
-## Elastic Distributions of OpenTelemetry language SDKs [apm-otel-elastic-distros]
+Elastic offers several distributions of OpenTelemetry language SDKs. Each Elastic Distribution of OpenTelemetry is a customized version of an [OpenTelemetry language SDK](https://opentelemetry.io/docs/languages/), ready to send data to the [Managed OTLP endpoint](opentelemetry://reference/motlp.md), Elastic APM server, or directly to {{es}}.
 
-Elastic offers several distributions of OpenTelemetry language SDKs. A *distribution* is a customized version of an upstream OpenTelemetry repository. Each Elastic Distribution of OpenTelemetry is a customized version of an [OpenTelemetry language SDK](https://opentelemetry.io/docs/languages/).
-
-:::{image} /solutions/images/observability-apm-otel-distro.png
-:alt: apm otel distro
+:::{image} /solutions/images/observability-apm-otel-distro2.png
+:alt: APM data ingest path
 :screenshot:
 :::
 
 With an Elastic Distribution of OpenTelemetry language SDK you have access to all the features of the OpenTelemetry SDK that it customizes, plus:
 
-* You may get access to SDK improvements and bug fixes contributed by the Elastic team *before* the changes are available upstream in the OpenTelemetry repositories.
-* The distribution preconfigures the collection of tracing and metrics signals, applying some opinionated defaults, such as which sources are collected by default.
+* You can get access to SDK improvements and bug fixes contributed by the Elastic team before the changes are available upstream in the OpenTelemetry repositories.
+* The distribution preconfigures the collection of tracing and metrics signals, applying opinionated defaults, such as which sources are collected by default.
+* By sending data through the [EDOT Collector](opentelemetry://reference/edot-collector/index.md), you make sure to onboard infrastructure logs and metrics.
 
 Get started with an Elastic Distribution of OpenTelemetry language SDK:
 
@@ -48,28 +36,17 @@ Get started with an Elastic Distribution of OpenTelemetry language SDK:
 * [**Elastic Distribution of OpenTelemetry Python**](opentelemetry://reference/edot-sdks/python/index.md)
 * [**Elastic Distribution of OpenTelemetry PHP**](opentelemetry://reference/edot-sdks/php/index.md)
 
-::::{note}
-For more details about OpenTelemetry distributions in general, visit the [OpenTelemetry documentation](https://opentelemetry.io/docs/concepts/distributions).
+::::{important}
+For a complete overview of OpenTelemetry and Elastic, explore [**Elastic Distributions of OpenTelemetry**](opentelemetry://reference/index.md).
 ::::
 
-## Upstream OpenTelemetry Collector and language SDKs [apm-otel-upstream]
+## Upstream OpenTelemetry Collector and SDKs [apm-otel-upstream]
 
 The {{stack}} natively supports the OpenTelemetry protocol (OTLP). This means trace data and metrics collected from your applications and infrastructure by an OpenTelemetry Collector or OpenTelemetry language SDK can be sent to the {{stack}}.
 
-You can set up an [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/), instrument your application with an [OpenTelemetry language SDK](https://opentelemetry.io/docs/languages/) that sends data to the collector, and use the collector to process and export the data to either {{apm-server-or-mis}}.
-
-:::{image} /solutions/images/observability-apm-otel-api-sdk-collector.png
-:alt: apm otel api sdk collector
-:screenshot:
-:::
-
-::::{note}
-It’s also possible to send data directly to either {{apm-server-or-mis}} from an upstream OpenTelemetry SDK. You might do this during development or if you’re monitoring a small-scale application. Read more about when to use a collector in the [OpenTelemetry documentation](https://opentelemetry.io/docs/collector/#when-to-use-a-collector).
-::::
-
-This approach works well when you need to instrument a technology that Elastic doesn’t provide a solution for. For example, if you want to instrument C or C++ you could use the [OpenTelemetry C++ client](https://github.com/open-telemetry/opentelemetry-cpp).
+You can set up an [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/), instrument your application with an [OpenTelemetry language SDK](https://opentelemetry.io/docs/languages/) that sends data to the Collector, and use the Collector to process and export the data to either the [Managed OTLP endpoint](opentelemetry://reference/motlp.md) or {{apm-server-or-mis}}.
 
-However, there are some limitations when using collectors and language SDKs built and maintained by OpenTelemetry, including:
+This approach works well when you need to instrument a technology that Elastic doesn’t provide a solution for. For example, if you want to instrument C or C++ you could use the [OpenTelemetry C++ client](https://github.com/open-telemetry/opentelemetry-cpp). However, there are some limitations when using upstream OpenTelemetry collectors and language SDKs, including:
 
 * Elastic can’t provide implementation support on how to use upstream OpenTelemetry tools.
 * You won’t have access to Elastic enterprise APM features.
@@ -79,24 +56,13 @@ For more on the limitations associated with using upstream OpenTelemetry tools,
 
 [**Get started with upstream OpenTelemetry Collectors and language SDKs →**](/solutions/observability/apm/upstream-opentelemetry-collectors-language-sdks.md)
 
-## AWS Lambda collector exporter [apm-otel-lambda]
-
-AWS Lambda functions can be instrumented with OpenTelemetry and monitored with Elastic {{observability}} or {{obs-serverless}}.
-
-To get started, follow the official AWS Distro for OpenTelemetry Lambda documentation, and configure the OpenTelemetry Collector to output traces and metrics to your Elastic cluster:
-
-[**Get started with the AWS Distro for OpenTelemetry Lambda**](https://aws-otel.github.io/docs/getting-started/lambda)
-
-## Upstream OpenTelemetry with the Elastic APM agent [apm-otel-api-sdk-elastic-agent]
-
-You can  use the OpenTelemetry API/SDKs with [Elastic APM agents](/solutions/observability/apm/get-started-fleet-managed-apm-server.md#_step_3_install_apm_agents) to translate OpenTelemetry API calls to Elastic APM API calls.
-
-:::{image} /solutions/images/observability-apm-otel-api-sdk-elastic-agent.png
-:alt: apm otel api sdk elastic agent
-:screenshot:
+:::{note}
+To understand the differences between Elastic Distributions of OpenTelemetry and upstream OpenTelemetry, refer to [EDOT compared to upstream OpenTelemetry](opentelemetry://reference/compatibility/edot-vs-upstream.md).
 :::
 
-This allows you to reuse your existing OpenTelemetry instrumentation to create Elastic APM transactions and spans — avoiding vendor lock-in and having to redo manual instrumentation.
+## Upstream OpenTelemetry with Elastic APM agent [apm-otel-api-sdk-elastic-agent]
+
+You can use the OpenTelemetry API/SDKs with [Elastic APM agents](/solutions/observability/apm/get-started-fleet-managed-apm-server.md#_step_3_install_apm_agents) to translate OpenTelemetry API calls to Elastic APM API calls. This allows you to reuse your existing OpenTelemetry instrumentation to create Elastic APM transactions and spans, avoiding vendor lock-in and having to redo manual instrumentation.
 
 However, not all features of the OpenTelemetry API are supported when using this approach, and not all Elastic APM agents support this approach.
 
@@ -105,4 +71,12 @@ Find more details about how to use an OpenTelemetry API or SDK with an Elastic A
 * [**APM Java agent**](apm-agent-java://reference/opentelemetry-bridge.md)
 * [**APM .NET agent**](apm-agent-dotnet://reference/opentelemetry-bridge.md)
 * [**APM Node.js agent**](apm-agent-nodejs://reference/opentelemetry-bridge.md)
-* [**APM Python agent**](apm-agent-python://reference/opentelemetry-api-bridge.md)
+* [**APM Python agent**](apm-agent-python://reference/opentelemetry-api-bridge.md)
+
+## AWS Lambda Collector Exporter [apm-otel-lambda]
+
+AWS Lambda functions can be instrumented with OpenTelemetry and monitored with Elastic {{observability}} or {{obs-serverless}}.
+
+To get started, follow the official AWS Distro for OpenTelemetry Lambda documentation, and configure the OpenTelemetry Collector to output traces and metrics to your Elastic cluster:
+
+[**Get started with the AWS Distro for OpenTelemetry Lambda**](https://aws-otel.github.io/docs/getting-started/lambda)