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.

Elastic Agent integrations based on the Elastic Common Schema (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) The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Generally available since 9.2 This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Pre-built, custom dashboards and visualizations
Documentation

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Preview since 9.2 This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. 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.

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.

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.

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	Configure an integration for a specific use case and add it to an Elastic Agent policy.
View integration policies	View the integration policies created for a specific integration.
Edit or delete an integration policy	Change settings or delete the integration policy.
Scale integration policies across many hosts	Use one integration policy for many hosts instead of creating a policy for each one.
Install and uninstall integration assets	Install, uninstall, and reinstall integration assets in Kibana.
View integration assets	View the Kibana assets installed for a specific integration.
Upgrade an integration	Upgrade an integration to the latest version.
Roll back an integration The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Generally available since 9.3 This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.	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 to learn more.

Deprecated integrations

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.