Document OTel integrations for Fleet-managed Elastic Agent

Author: vishaangelova

reference/fleet/manage-integrations.md

@@ -2,34 +2,32 @@
 navigation_title: Manage integrations
 mapped_pages:
   - https://www.elastic.co/guide/en/fleet/current/integrations.html
+applies_to:
+  stack: ga
+  serverless: ga
 products:
   - id: fleet
   - id: elastic-agent
 ---
 
 # Manage {{agent}} integrations [integrations]
 
+{{agent}} integrations provide a unified way to collect data from apps and services and to protect systems from security threats. 
 
-::::{admonition}
-Integrations are available for a wide array of popular services and platforms. To see the full list of available integrations, go to the **Integrations** page in {{kib}}, or visit [Elastic Integrations](integration-docs://reference/index.md).
+Integrations are available for a wide array of services and platforms. To see the full list of available integrations, go to the **Integrations** page in {{kib}}, or visit [Elastic Integrations](integration-docs://reference/index.md).
 
-{{agent}} integrations provide a simple, unified way to collect data from popular apps and services, and protect systems from security threats.
-
-Each integration comes prepackaged with assets that support all of your observability needs:
+Each integration comes prepackaged with assets that support your observability needs:
 
 * Data ingestion, storage, and transformation rules
 * Configuration options
 * Pre-built, custom dashboards and visualizations
 * Documentation
 
-::::
-
-
 ::::{note}
-Be aware that some integrations may function differently across different spaces. Also, some might only work in the default space. We recommend reviewing the specific integration documentation for any space-related considerations.
-
+Some integrations may function differently across different spaces, and some might only work in the default space. For any  space-related considerations, review the documentation for the specific integration.
 ::::
 
+## Integration actions
 
 The following table shows the main actions you can perform in the **Integrations** app in {{kib}}. You can perform some of these actions from other places in {{kib}}, too.
 
@@ -44,9 +42,36 @@ The following table shows the main actions you can perform in the **Integrations
 
 ::::{note}
 The **Integrations** app in {{kib}} needs access to the public {{package-registry}} to discover integrations. If your deployment has network restrictions, you can [deploy your own self-managed {{package-registry}}](/reference/fleet/air-gapped.md#air-gapped-diy-epr).
-
 ::::
 
 :::{tip}
 Once you've started using integrations to ingest data, you can customize how that data is managed over time. Refer to [Index lifecycle management](/reference/fleet/data-streams.md#data-streams-ilm) to learn more.
 :::
+
+## Using {{agent}} integrations to collect OpenTelemetry data
+
+```{applies_to}
+stack: preview 9.2
+```
+
+{{fleet}} now supports installing {{agent}} integration input packages for collecting OpenTelemetry (OTel) data such as logs, metrics, and traces. To find the available OpenTelemetry (OTel) integrations, select the **OpenTelemetry** category on the **Integrations** page in {{kib}}.
+
+Unlike {{agent}} integrations based on the [Elastic Common Schema](ecs://reference/index.md) (ECS), OTel integrations use OTel Collector receivers to collect OTel data following [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv).
+
+:::{important}
+OTel integrations are for use with {{Fleet}} and {{agent}} running in default mode. They are distinct from [running {{agent}} as an EDOT Collector](/reference/fleet/otel-agent.md).
+:::
+
+### OTel integration configuration
+
+To add an OTel integration in {{fleet}}, configure its integration policy similarly to how you would configure an ECS-based integration.
+
+When the integration policy is created, assets such as pre-built dashboards and visualizations for OTel data are automatically installed if available.
+
+{{fleet}} also creates a managed [index template](/manage-data/data-store/templates.md#index-templates) with an OTel configuration and an `.otel` suffix in its index pattern. The index template uses {{fleet}} [component templates](/manage-data/data-store/templates.md#component-templates) for settings and OTel component templates for default mappings. It also includes `@custom` component templates that allow you to [customize your Elasticsearch index](/reference/fleet/data-streams.md#data-streams-index-templates-edit) similarly to ECS-based integrations.
+
+On the OTel integration's **Configs** page, you can view a generated sample configuration, which you can use as a starting point to set up the integration on a standalone {{agent}}.
+
+:::{note}
+Currently, OTel integrations only support sending data using the {{es}} output.
+:::