Knowledge Base

Release Notes v1.5.3

Fluent Bit is a Fast and Lightweight Data Processor and Forwarder for Linux, BSD and OSX. We are proud to announce the availability of Fluent Bit v1.5.3.

For people upgrading from previous versions you must read the Upgrading Notes section of our documentation:


Changes

Fluent Bit v1.5.3 is the next patch release on v1.5 series and comes with the following changes:


List of general changes

  • Core
    • engine: validate connection event thread is not null
    • stacktrace: fix can not print stack trace when Fluent Bit runs in container (#2421)
    • lib: chunkio: upgrade to v1.0.5
    • dump: use stderr instead of stdout when getting SIGCONT (#2438)
    • parser: use built-in flb_strptime() instead of system strptime() (#2311)
    • gzip: fix uncompress routine and add crc32 checks (#2396)
    • io: tls: add connect_timeout handler routine
    • io: tls: do not assume handshake is in async mode
    • io: fix blocking mode
    • io: split logic for sync/async connection
    • http_client: fix format string mismatch (#2442)
    • upstream: fix async mode check and set missing co-routine context
    • upstream: upon KA reuse, validate socket
  • Plugins
    • Tail (Input)
      • When option exit_on_eof is set to true, wait for all the files to be read (#2436)
    • Stackdriver (Output)
      • Abort initialization if ‘project_id’ is not set
      • Add tag_prefix option to configuration
      • Fix metadata not assigned correctly
      • Construct local_resource_id from tag
      • Support special fields: timestamp, httprequest, sourcelocation and insertid
    • HTTP (Output)
      • If json_date_key is set to false, skip date key
    • Tcp (Output)
      • If json_date_key is set to false, skip date key
    • Stdout (Output)
      • If json_date_key is set to false, skip date key

Contributors

On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!

Since the list grows every time, it’s hard to mention every single person involved. In a best effort possible, we are mentioning people who have signed contributions in our GIT project history through commits. We would like to thanks to the following people who have been involved doing coding, bug fixes, documentation and general contributions on this release:

Join us!

We want to hear about you, our community is growing and you can be part of it!, you can contact us at: