Docker Elk Versions Save

Default Elastic version: 8.12.1

Note See version selection to run a different version.

Notable changes

• The Fleet Server agent now has the Docker integration enabled by default, and collects the logs and metrics of all containers running on the host. This mirrors the default behaviour of the Metricsbeat and Filebeat extensions, making them obsolete for the aforementioned purpose.

Default Elastic version: 8.7.1

Note See version selection to run a different version.

Notable changes

• The setup container must now be run manually with docker-compose up setup. This makes the process of initializing users and groups more explicit, and allows re-initializing built-in users and groups with less effort. Please refer to #798 for more information.
• The minimum Compose version requirement was increased to 1.28.0.
• The curator extension was updated to v8.0. Curator is now major version locked with Elasticsearch. Please refer to the Curator Reference for more information.

Default Elastic version: 8.6.2

Note See version selection to run a different version.

Notable changes

• Elasticsearch, Logstash and Kibana now use the unless-stopped restart policy by default. As a result, their respective container gets restarted automatically after exiting, including after a reboot of the Docker host (but not when stopped manually with docker-compose [stop|down]).
• Fix Fleet Server extension listening on 127.0.0.1 (localhost) instead of 0.0.0.0 after upgrading to v8.6.

Default Elastic version: 8.5.2

Note See version selection to run a different version.

Notable changes

• Beats extensions no longer authenticate as the elastic superuser to send data to Elasticsearch. Instead, passwords for the filebeat_internal, metricbeat_internal and heartbeat_internal users (inactive by default) must be set respectively in the .env file.
• Monitoring of Elasticsearch, Logstash and Kibana is enabled by default via the Metricbeat extension. A password for the monitoring_internal user (inactive by default) must be set in the .env file for this to work.
• Self-monitoring is enabled by default in all Beats extensions. A password for the beat_system user (inactive by default) must be set in the .env file for this to work.
• Instructions for re-executing the setup were added. This allows resetting passwords to the values defined in the .env file, and forcing the creation of missing internal users and roles.
• It is no longer required to rebuild the image of the setup container when switching between the main and tls branches.

Default Elastic version: 8.5.1

Note See version selection to run a different version.

Notable changes

• Addition of the Fleet extension.
• Deletion of the deprecated standalone APM Server extension. APM Server is now deployed as an Elastic Integration via Elastic Agent.

Default Elastic version: 8.3.3

Note See version selection to run a different version.

Notable changes

• Change the default port of Logstash's TCP input from 5000 to 50000 to avoid conflicts with IANA registered ports (UPnP, Docker Registry, Apple's AirPlay Receiver, ...)

Default Elastic version: 8.2.2

Note See version selection to run a different version.

Notable changes

• Raise JVM heap size of Elasticsearch from 256 MB to 512 MB

Default Elastic version: 8.0.0

Note See version selection to run a different version.

Notable changes

• Introduce the setup service to automate the management of required roles and user passwords
• Bump minimum Compose version requirement to 1.26.0
• Update Compose file version to 3.7
• Rename ELK_VERSION to ELASTIC_VERSION

Default Elastic version: 8.0.0

Note See version selection to run a different version.

Notable changes

• The main branch now follows the 8.x release series of Elastic components.

  Moving forward, all changes on the main branch should be considered incompatible with the 7.x release series, which is now being tracked on the release-7.x branch.

List of changes impacting docker-elk:

Logstash

• The output to Elasticsearch is handled as a data stream.

  Starting with v8.0.0, the elasticsearch output for Logstash sends log data to a data stream instead of logstash-* indices by default. The name of the default data stream is logs-generic-default. docker-elk remains unopinionated and simply uses Elastic's defaults like it always has, so users who prefer to retain the old behaviour need to explicitly opt-out of data streams in their Logstash pipelines.

  Refs:

  • https://www.elastic.co/guide/en/elasticsearch/reference/8.0/data-streams.html
  • https://www.elastic.co/guide/en/logstash/8.0/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-data-streams

• The (legacy) monitoring data collection is now disabled.

  This feature was deprecated since v7.9.0, and removed in v8.0.0.

  Ref: https://www.elastic.co/guide/en/logstash/8.0/monitoring-internal-collection-legacy.html

Elasticsearch

• The command line tool elasticsearch-setup-passwords was deprecated in favour of a new elasticsearch-reset-password tool.

  Passwords for built-in users must now be generated one by one.

  Ref: https://www.elastic.co/guide/en/elasticsearch/reference/8.0/setup-passwords.html

Kibana

• An index pattern for logs-* indices is automatically created.

  It used to be required to manually create an index pattern for indices managed by Logstash, even when using the default Logstash indices. This is no longer the case since the output data is now being handled as a data stream, and Kibana automatically creates index patterns for these.

Enterprise Search

• Kibana is now the new management interface, and the only one available moving forward.

  The old standalone Enterprise Search interface was removed in v8.0.0.

  Ref: https://www.elastic.co/guide/en/enterprise-search/8.0/user-interfaces.html