Logstash 8.5.0 Release Notes

Known issues

Due to a recent change in the Red Hat scan verification process, this version of Logstash is not available in the Red Hat Ecosystem Catalog. This bug will be fixed in the next release. Please use the Elastic docker registry to download the 8.5.0 Logstash image.

New features and enhancements

  • It is often difficult to understand the health of a pipeline, including whether it is exerting or propagating back-pressure or otherwise staying reasonably “caught up” with its inputs. This release adds pipeline "flow" metrics to the node_stats API for each pipeline, which includes the current and lifetime rates for five key pipeline metrics: input_throughput, filter_throughput, output_throughput, queue_backpressure, and worker_concurrency. #14518

Notable issues fixed

  • Added missing "monitoring.cluster_uuid" to the env2yaml list of accepted configurations and enables the user to set this configuration option via environment variable #14425
  • Use COPY instruction instead of ADD in Dockerfiles #14423

Documentation Improvements and Fixes

  • Add missing reference to full config of Logstash to Logstash over HTTP #14466
  • Describe DLQ’s age retention policy #14340
  • Document the cleaning of consumed events from DLQ #14341


Translate Filter - 3.4.0

  • Refactor: leverage scheduler mixin #93

Elasticsearch Input - 4.16.0

  • Added ssl_certificate_verification option to control SSL certificate verification #180
  • Feat: add retries option. allow retry for failing query #179

Exec Input - 3.6.0

  • Refactor: start using scheduler mixin #33
  • Fix: behavior incompatiblity between (standalone) LS and LS in Docker #30

File Input - 4.4.4

  • Fixes gzip file handling in read mode when run on JDK12+, including JDK17 that is bundled with Logstash 8.4+ #312

Http_poller Input - 5.4.0

  • Refactor: start using scheduler mixin #134

Elasticsearch Output - 11.9.0

  • Feature: force unresolved dynamic index names to be sent into DLQ. This feature could be explicitly disabled using dlq_on_failed_indexname_interpolation setting #1084
  • Feature: Adds a new dlq_custom_codes option to customize DLQ codes #1067
  • Feature: deprecates the failure_type_logging_whitelist configuration option, renaming it silence_errors_in_log #1068