﻿---
title: Manage Elastic Agent integrations
description: Elastic Agent integrations provide a simple, unified way to collect data from popular apps and services, and protect systems from security threats. Integrations...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/manage-integrations
products:
  - Elastic Agent
  - Fleet
applies_to:
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Generally available
---

# Manage Elastic Agent integrations
Elastic Agent integrations provide a simple, unified way to collect data from popular apps and services, and protect systems from security threats.
Integrations are available for a wide array of popular services and platforms. To see the full list, go to the **Integrations** page in Kibana, or visit [Elastic Integrations](https://docs-v3-preview.elastic.dev/elastic/integration-docs/tree/main/reference).
Elastic Agent integrations based on the [Elastic Common Schema](https://docs-v3-preview.elastic.dev/elastic/ecs/tree/main/reference) (ECS) come prepackaged with assets that support your observability needs:
- Data ingestion, storage, and transformation rules
- Configuration options
- Alert templates to enable users to quickly set up custom alerting rules (available in some integrations) <applies-to>Elastic Stack: Generally available since 9.2</applies-to>
- Pre-built, custom dashboards and visualizations
- Documentation

<applies-to>Elastic Stack: Preview since 9.2</applies-to> Fleet also supports installing Elastic Agent integration packages for collecting and visualizing OpenTelemetry data. For more information, refer to [Collect OpenTelemetry data with Elastic Agent integrations](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/otel-integrations).
The **Integrations** app in Kibana needs access to the public Elastic Package Registry to discover integrations. If your deployment has network restrictions, you can [deploy your own self-managed Elastic Package Registry](/elastic/docs-content/pull/5865/reference/fleet/air-gapped#air-gapped-diy-epr).
<note>
  Some integrations may function differently across different spaces, with some working only in the default space. Review the documentation specific to your integration for any space-related considerations.
</note>


## Work with integrations

You can perform a variety of actions in the **Integrations** app in Kibana. Some of these actions are also available from other places in Kibana.

| User action                                                                                                                                                                                                | Result                                                                                         |
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|
| [Add an integration to an Elastic Agent policy](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/add-integration-to-policy)                                              | Configure an integration for a specific use case and add it to an Elastic Agent policy.        |
| [View integration policies](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/view-integration-policies)                                                                  | View the integration policies created for a specific integration.                              |
| [Edit or delete an integration policy](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/edit-delete-integration-policy)                                                  | Change settings or delete the integration policy.                                              |
| [Install and uninstall integration assets](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/install-uninstall-integration-assets)                                        | Install, uninstall, and reinstall integration assets in Kibana.                                |
| [View integration assets](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/view-integration-assets)                                                                      | View the Kibana assets installed for a specific integration.                                   |
| [Upgrade an integration](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/upgrade-integration)                                                                           | Upgrade an integration to the latest version.                                                  |
| [Roll back an integration](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/roll-back-integration) <applies-to>Elastic Stack: Generally available since 9.3</applies-to> | Roll back an integration to the previously installed version if issues occur after an upgrade. |


## Customize integrations

After you've started using integrations to ingest data, you can customize how the data is managed over time. Refer to [Index lifecycle management](/elastic/docs-content/pull/5865/reference/fleet/data-streams#data-streams-ilm) to learn more.

## Deprecated integrations

<applies-to>
  - Elastic Cloud Serverless: Generally available
  - Elastic Stack: Planned
</applies-to>

Integration developers can mark integration packages or individual features as deprecated when retiring them or replacing them with newer alternatives. When an integration or feature is marked as deprecated in a specific version, Fleet displays warnings throughout the UI to help you plan for migration to alternative solutions.
Deprecated integrations enter a maintenance period (typically one year) during which they remain available in the Elastic Package Registry for installation and use. For integrations with automatic policy upgrades enabled, the upgrade is paused when deprecations are detected, and you must review and accept the upgrade before proceeding. After the maintenance period ends, the integration might be removed from the Elastic Package Registry.
For detailed information about the deprecation lifecycle, identifying deprecated integrations in the UI, and how deprecations affect integration upgrades, refer to [Understanding deprecated integrations](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5865/reference/fleet/deprecated-integrations).