We strive to maintain backward compatibility between minor versions (6.x to 6.y, for example) so that you can upgrade without changing any configuration files. Breaking changes are usually introduced only between major versions (such as 5.x to 6.y). On occasion, we are forced to break compatibility within a given major release to ensure correctness of operation.
This section covers the changes that you need to be aware of when migrating to Logstash 6.0.0 and later.
Migrating directly between non-consecutive major versions (1.x to 6.x) is not recommended.
See these topics for a description of breaking changes:
See also Release Notes.
Breaking change across PQ versions prior to Logstash 6.3.0edit
If you are upgrading from Logstash 6.2.x or any earlier version (including 5.x) and have the persistent queue enabled, we strongly recommend that you drain or delete the persistent queue before you upgrade. See Upgrading with Persistent Queues Enabled for information and instructions.
Breaking changes in 6.0edit
Here are the breaking changes for 6.0.
Changes in Logstash Coreedit
These changes can impact any instance of Logstash and are plugin agnostic, but only if you are using the features that are impacted.
config.reload.intervalhas been changed to use time value strings such as
10setc. Previously, users had to convert this to a millisecond time value themselves.
RPM/Deb package changesedit
debrelease artifacts, config files that match the
*.confglob pattern must be in the conf.d folder, or the files will not be loaded.
Command Line Interface behavioredit
-fCLI options are now mutually exclusive. This also applies to the corresponding long form options
path.config. This means any configurations provided via
-ewill no longer be appended to the configurations provided via
Configurations provided with
config.pathwill not be appended with
List of plugins bundled with Logstashedit
The following plugins were removed from the 5.0 default bundle based on usage data. You can still install these plugins manually: