Humio Server 1.11.1 Preview (2020-05-28)

VersionTypeRelease DateEnd of SupportUpgrades FromData MigrationConfig. Changes
1.11.1Preview2020-05-282020-06-091.10.0NoNo
JAR ChecksumValue
MD55cb65fb38f5882c86e170fc19932bc2c
SHA1d8639e7541b0de1b2ef5c3909f88d864b18faf63
SHA25663e5264b32fc02774e1f4dd3a7dbd1ddbb124158e915d5df219b355faaf278d0
SHA5127c7832559a5a1f43f87d7cf12bbb63b5a7ea6c0922a4c917b652caba08fe77375b49517f2675f819f9fdf0519e90310e572bee1cee8e72bade531605ddd14942

Bug Fixes and Memory Optimizations

Bug Fixes

  • Other

    • Elastic Bulk API change

    • Dashboard widgets now display an error if data is not compatible with the widget

    • Several improvements to memory handling

    • Several improvements to query error handling

Known Issues

  • Other

    • Fluent Bit users might need to change the Fluent Bit configuration. To ensure compatibility with the newest Beats clients, the Elastic Bulk API has been changed to always return the full set of status information for all operations, as it is done in the official Elastic API.

      This can however cause problems when using Fluent Bit to ingest data into Humio.

      Fluent Bit in default configuration uses a small buffer (4KB) for responses from the Elastic Bulk API, which causes problems when enough operations are bulked together. The response will then be larger than the response buffer as it contains the status for each individual operation. Make sure the response buffer is large enough, otherwise Fluent Bit will stop shipping data. See: https://github.com/fluent/fluent-bit/issues/2156 and https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch