Humio Server 1.22.0 Stable (2021-03-02)
| Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | JDK Compatibility? | Req. Data Migration | Config. Changes? |
|---|---|---|---|---|---|---|---|---|---|
| 1.22.0 | Stable | 2021-03-02 | Cloud On-Prem | 2022-03-31 | No | 1.16.0 | 11 | No | Yes |
| JAR Checksum | Value |
|---|---|
| MD5 | 115532e6c7c321a1fe737bdde5731f4b |
| SHA1 | 8a42ec6f7ba168939c60d521d30eba202479173e |
| SHA256 | 4cff315346b9edb1ba625f48fe36105666dc9b95e711190578ff62752fa763e4 |
| SHA512 | 0173d8b48f8612198cb4a20146b15d23769cacee4fac12a7c710a93ef2f17a30140ccee8e09c8f7c5262815cbb2e03876fe30986f276a9d36155832c4e03a233 |
Important Information about Upgrading
This release promotes the latest 1.21 release from preview to stable.
Beginning with version 1.17.0, if your current version of Humio is not directly able to upgrade to the new version, you will get an error if you attempt to start up the incompatible version. The 1.22.0 release is only compatible with Humio release 1.16.0 and newer. This means that you will have to ensure that you have upgraded at least to 1.16.0 before trying to upgrade to 1.22.0. In case you need to do a rollback, this can also ONLY happen back to 1.16.0 or newer. Rolling directly back to an earlier release can result in data loss.
UI revamp In this version the UI has been given a complete makeover.
Bug Fixes
Other
Restrict concurrency when mirroring uploaded files within the cluster
Fixed issue where tag filters in anonymous parts within an aggregate did not get applied
Fix issue where updating account settings would present the user with an error even though the update was successful
Change log lines creating a 'kind' field. Kind is used as a tag for the different humio logs
Add the "ProxyOrganization" header to the list of general auth headers used on REST calls
Fixed issue where local segment files would not get deleted in time, potentially filling the disk
Major changes: (see version 1.21.0 and 1.21.1 release notes)
Fixed issue where root users were not allowed to set unlimited time in retention settings
Increase HTTP chunk size from 16MB to 128MB