Elasticsearch:Compatibility matrixes

Elasticsearch compatibility (5.x, 6.x, 7.x, 8.x)

Use the same minor version for all Elasticsearch, Kibana, Filebeat, and Logstash clusters.

^ Elasticsearch output compatibility — Beats or Logstash indexing data to Elasticsearch.

\* Use the latest versions of Beats, Logstash, and ES-Hadoop. Earlier versions may not support all features.

\*\* Starting in Elasticsearch 6.3, all X-Pack features are included in the default distributions of Elastic Stack. For more information, see X-Pack.

\*\*\* APM Server 6.7 and 6.8 work with Elasticsearch 7.0, but you must migrate your data using Upgrade Assistant before the data is visible in Kibana 7.0.

\*\*\*\* From 7.7.0, App Search is provided with Enterprise Search.

Logstash compatibility (2.4.x–7.10.x)

\* The "Monitoring and management Elasticsearch clusters" column covers clusters configured via xpack.monitoring.elasticsearch.url and xpack.management.elasticsearch.url. Use the same minor version across Elasticsearch, Kibana, and Logstash for the best monitoring and management performance. To monitor or manage clusters running 6.2 or earlier, install X-Pack on all services in the cluster.

\*\* In Logstash versions earlier than 7.4, Functionbeat supports only Elasticsearch as an output. Starting in 7.4, Functionbeat supports both Logstash and Elasticsearch as outputs.

Beats compatibility (1.3.x–8.15.x)

\* The "Monitoring Elasticsearch cluster" column covers clusters configured via xpack.monitoring.elasticsearch. Use the same minor version across Elasticsearch, Kibana, and Logstash for the best monitoring performance. To monitor clusters running 6.2 or earlier, install X-Pack on all services in the cluster.

\*\* Functionbeat supports only Elasticsearch as an output. Logstash is not supported as an output for Functionbeat.

For the full upstream compatibility matrix, see Product Compatibility.