Published on 2021-01-25 00:00:00

Humio 1.18.4

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.18.4

Stable

2021-01-25

2021-11-26

1.16.0

No

No

JAR Checksum

Value

MD5

d6d2999c1640e0b922b79163c9ec83b5

SHA1

a0452151aaa9437a2d4f772f23d3f817080d015c

SHA256

b786cb7edf1d2b8729a44ff73ce8239688aefd2431940d283a15537b3be01b37

SHA512

cfce44d51dce08213bfc26f5bd74cf3596185bc15e87518f63cf9b601f0e8118923d61afa17770827cd1fae6547a5d11decdacc9cffb57f95f0f3b351151632d

TGZ Checksum

Value

MD5

d6d2999c1640e0b922b79163c9ec83b5

SHA1

a0452151aaa9437a2d4f772f23d3f817080d015c

SHA256

b786cb7edf1d2b8729a44ff73ce8239688aefd2431940d283a15537b3be01b37

SHA512

cfce44d51dce08213bfc26f5bd74cf3596185bc15e87518f63cf9b601f0e8118923d61afa17770827cd1fae6547a5d11decdacc9cffb57f95f0f3b351151632d

Important Information about Upgrading

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.18.4 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.18.4. 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.

Change Log

  • Fixed an issue for on-prem users not on multitenant setup by reverted a metric change introduced in 1.18.0, jmx and Slf4j included an OrgId in all metrics for repositories.