- CI: upgrade testing #83
- Removed JRuby check when using FIFOs #75
- Fix a bug introduced in v4.2.4 where events on low-volume pipelines could remain unflushed for long periods when
flush_interval
was non-zero #70
- Fix a bug where flush interval was being called for each event when enabled #67
- Docs: Set the default_codec doc attribute.
- Add feature
write_behavior
to the documentation #58
- Bugfix: Move require of flores into the spec file instead of main file.rb
- New
write_behavior
feature. Value can be "append" (default) or "overwrite". If "append", events will be appended to the end of the file. If "overwrite", the file will only contain the last event written.
- Update gemspec summary
- Fix some documentation issues
- Remove obsolete option
message_format
- Move one log message from info to debug to avoid noise
- Make 'message_format' option obsolete
- Use new Logsash 2.4/5.0 APIs for working batchwise and with shared concurrency
- Relax constraint on logstash-core-plugin-api to >= 1.60 <= 2.99
- Republish all the gems under jruby.
- Update the plugin to the version 2.0 of the plugin api, this change is required for Logstash 5.0 compatibility. See elastic/logstash#5141
- Depend on logstash-core-plugin-api instead of logstash-core, removing the need to mass update plugins on major releases of logstash
- New dependency requirements for logstash-core for the 5.0 release
- Rename Dir.exists? to Dir.exist? to fix deprecation warning
- Allow setting dir and file permissions
- Fixed specs to not depend on pipeline ordering
- Fixed Time specs
- Add support for codec, using json_lines as default codec to keep default behavior. Ref: logstash-plugins#9
- Add create_if_deleted option to create a destination file in case it was deleted by another agent in the machine. In case of being false the system will add the incomming messages to the failure file.
- Plugins were updated to follow the new shutdown semantic, this mainly allows Logstash to instruct input plugins to terminate gracefully, instead of using Thread.raise on the plugins' threads. Ref: elastic/logstash#3895
- Dependency on logstash-core update to 2.0