Logstash 5.3.0 Breaking Changes
editLogstash 5.3.0 Breaking Changes
editThis section discusses the changes that you need to be aware of when migrating your application from Logstash 5.2 to 5.3.
Changes in Logstash Core
editPersistent queue
editThe default location on disk where the queue data is stored has been changed from <path.data>/queue to
<path.data>/queue/main. The directory hierarchy now includes the pipeline ID which defaults to main.
This change was made to accommodate an upcoming feature where multiple, isolated pipelines can be run on
the same Logstash instance. In this future situation, each pipeline will have its own queue; hence the new directory
structure.
Upgrading to 5.3
If you are using the persistent queue feature and intend to upgrade to 5.3:
- Ensure you completely drain the queue data in 5.2 by stopping the incoming data and processing all of the in-flight events.
-
Stop Logstash and manually move the files under
<path.data>/queue/to<path.data>/queue/mainbefore upgrading to 5.3. -
If you do not intend to process the data currently buffered in the queue in 5.2, you can manually delete
the
path.data/queuedirectory before upgrading to 5.3.
Breaking Changes in Plugins
editKV filter: trim and trimkey options are renamed to trim_value and trim_key respectively. Their behavior has been
changed as well to trim the characters at the beginning or end of the values.