Limitations of this releaseedit

This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.

This is an experimental release and there is no migration path for future releases, so YOU MUST TEST IN A DEDICATED CLUSTER. In a future release, we plan to add support for a new way of managing rolling indices that will make the experience easier for users. However, any data stored in this release will not be migrated in our next release, and you must wipe any data and settings changed in Kibana and Elasticsearch to avoid future conflicts. We recommend using a dedicated test cluster or deployment that can be deleted when you are done.

Ingest Manager is currently only available to users with the superuser role. This role is necessary to create indices, install integration assets, and update Elastic Agent configurations. In order to use Fleet, the Elastic Agents must have a direct network connection to Kibana and Elasticsearch. It is also possible to run the Elastic Agents in standalone mode in cases where a network connection is not available or not needed.

This feature has several additional limitations at the current time:

  • Support for only 9 integrations (more coming soon)
  • Support for only Filebeat and Metricbeat
  • We recommend you enroll no more than 100 Agents
  • No output to Logstash, Kafka, or other remote clusters
  • No proxy support in Elastic Agent
  • Kibana must have internet access to download integration packages
  • No support for advanced Beats settings like multiline, processors, and so on
  • No custom index templates or pipelines
  • No support for Kubernetes or Docker autodiscovery

Experimental releases are not officially supported, but we encourage you to report issues in our discuss forum.