Adds elasticapm processor to the docs (#10239)

* Add elasticapm processor

* Apply suggestions from code review

Co-authored-by: Visha Angelova <[email protected]>

* Update docs/reference/edot-collector/config/default-config-standalone.md

Co-authored-by: Visha Angelova <[email protected]>

* Update docs/reference/edot-collector/config/default-config-standalone.md

Co-authored-by: Visha Angelova <[email protected]>

* Update modes.md

* Reorder table

* Fix table

---------

Co-authored-by: Visha Angelova <[email protected]>

Author: theletterf

docs/reference/edot-collector/config/default-config-standalone.md

@@ -65,12 +65,12 @@ Data is exported directly to {{es}} using the [`elasticsearch`] exporter in `OTe
 
 The application pipeline in the EDOT Collector receives data from OTel SDKs through the [`OTLP`] receiver. While logs and metrics are exported verbatim into {{es}}, traces require two additional components.
 
-The [`elastictrace`] processor enriches trace data with additional attributes that improve the user experience in the Elastic Observability UIs. In addition, the [`elasticapm`] connector generates pre-aggregated APM metrics from tracing data.
+{applies_to}`edot_collector: ga 9.2` The [`elasticapm`] processor enriches trace data with additional attributes that improve the user experience in the Elastic Observability UIs. In addition, the [`elasticapm`] connector generates pre-aggregated APM metrics from tracing data.
 
 Application-related OTel data is ingested into {{es}} in OTel-native format using the [`elasticsearch`] exporter.
 
 :::{note}
-Both components, `elastictrace` and `elasticapm` are required for Elastic APM UIs to work properly. As they aren't included in the OpenTelemetry [Collector Contrib repository](https://github.com/open-telemetry/opentelemetry-collector-contrib), you can:
+Both the `elasticapm` processor and the `elasticapm` connector are required for Elastic APM UIs to work properly. As they aren't included in the OpenTelemetry [Collector Contrib repository](https://github.com/open-telemetry/opentelemetry-collector-contrib), you can:
 
 * Use the EDOT Collector with the available configuration to ingest data into {{es}}.
 * [Build a custom, EDOT-like Collector](/reference/edot-collector/custom-collector.md) for ingesting data into {{es}}.
@@ -100,23 +100,33 @@ Platform logs are scraped with the [`filelog`] receiver, host metrics are collec
 
 Data from OTel SDKs is piped through the [`OTLP`] receiver directly to the OTLP exporter that sends data for all signals to the {{motlp}}.
 
-With the {{motlp}}, there is no need to configure any Elastic-specific components, such as [`elasticinframetrics`], [`elastictrace`] processors, the [`elasticapm`] connector, or the [`elasticsearch`] exporter. Edge setup and configuration can be 100% vendor agnostic.
+With the {{motlp}}, there is no need to configure any Elastic-specific components, such as the [`elasticinframetrics`] and [`elasticapm`] processors, the [`elasticapm`] connector, or the [`elasticsearch`] exporter. Edge setup and configuration can be fully vendor agnostic.
 
 ## Gateway mode
 
 In Gateway mode, the Collector ingests data from other Collectors running in Agent mode and forwards it to Elastic.
 
-## Example configuration
+### Example configuration
 
 The following example configuration files are available for the Gateway mode:
 
+:::::{tab-set}
+
+::::{tab-item} 9.x
 | Version | Configuration  |
 |---------|----------------|
-| 8.17    | [Gateway mode](https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v9.0.4/internal/pkg/otel/samples/linux/gateway.yml) |
-| 8.18    | [Gateway mode](https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v9.0.4/internal/pkg/otel/samples/linux/gateway.yml) |
+| 9.1     | [Gateway mode](https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v9.1.0/internal/pkg/otel/samples/linux/gateway.yml) |
 | 9.0     | [Gateway mode](https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v9.0.4/internal/pkg/otel/samples/linux/gateway.yml) |
+::::
+
+::::{tab-item} 8.x
+| Version | Configuration  |
+|---------|----------------|
 | 8.19    | [Gateway mode](https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v8.19.0/internal/pkg/otel/samples/linux/gateway.yml) |
-| 9.1     | [Gateway mode](https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v9.1.0/internal/pkg/otel/samples/linux/gateway.yml) |
+| 8.18    | [Gateway mode](https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v9.0.4/internal/pkg/otel/samples/linux/gateway.yml) |
+| 8.17    | [Gateway mode](https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v9.0.4/internal/pkg/otel/samples/linux/gateway.yml) |
+::::
+:::::
 
 Use the previous example configuration as a reference when configuring your Gateway Collector or customizing your EDOT Collector configuration.
 
@@ -175,9 +185,14 @@ processors:
   batch/metrics:
     send_batch_max_size: 0 # Prevents splitting metrics requests
     timeout: 1s
-  elastictrace: {}
+  elasticapm: {}
 ```
 
+:::{note}
+:applies_to: edot_collector: ga 9.2
+The `elasticapm` processor replaces the deprecated `elastictrace` processor.
+:::
+
 ### Data export
 
 The Gateway exports data to Elasticsearch in two formats:
@@ -212,7 +227,6 @@ The service section defines separate pipelines for different telemetry types:
 
 Each pipeline connects specific receivers, processors, and exporters to handle different data types appropriately.
 
-
 ## Central configuration
 
 The EDOT Collector can be configured to use [APM Agent Central Configuration](docs-content://solutions/observability/apm/apm-agent-central-configuration.md). Refer to [Central configuration docs](opentelemetry://reference/central-configuration.md) for more details.
@@ -312,7 +326,7 @@ The server expects incoming HTTP requests to include an API key with sufficient
 [`hostmetrics`]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver
 [`elasticsearch`]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/elasticsearchexporter
 [`elasticinframetrics`]: https://github.com/elastic/opentelemetry-collector-components/tree/main/processor/elasticinframetricsprocessor
-[`elastictrace`]: https://github.com/elastic/opentelemetry-collector-components/tree/main/processor/elastictraceprocessor
+[`elasticapm`]: https://github.com/elastic/opentelemetry-collector-components/tree/main/processor/elasticapmprocessor
 [`elasticapm`]: https://github.com/elastic/opentelemetry-collector-components/tree/main/connector/elasticapmconnector
 [`resource`]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourceprocessor
 [`resourcedetection`]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor

docs/reference/edot-collector/modes.md

@@ -58,7 +58,7 @@ This is the only case where using the {{es}} exporter is recommended. In all oth
 
 The following components are required for APM functionality in self-managed Elastic:
 
-- The `elastictrace` processor enriches trace data with additional attributes that improve the user experience in Elastic Observability UIs.
+- {applies_to}`edot_collector: ga 9.2` The `elasticapm` processor enriches trace data with additional attributes that improve the user experience in Elastic Observability UIs.
 - The `elasticapm` connector generates pre-aggregated APM metrics from trace data.
 
 In this case, EDOT Collector as a Gateway also handles routing of the different types of telemetry data to the relevant indices.