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

Humio 1.19.2

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.19.2

Preview

2021-01-25

2021-01-28

1.16.0

No

No

JAR Checksum

Value

MD5

01e72a42b56685f50111466e91475e9b

SHA1

7d09c09579a2c00cb2cc0a38c421969861f9c6a0

SHA256

83e7efdf3bd38eb806b30c81603e4eefe5ee17f88fa9c6440fd56d11c86d2869

SHA512

3ccc62d52899ecad9fd7626bb15f90b05bcabaf761d997c4aa63849f93702c6caf32d1f6ed191c981054c1df853ec6fbcdbd07fba0e76e289d4f71d39b542d9b

TGZ Checksum

Value

MD5

01e72a42b56685f50111466e91475e9b

SHA1

7d09c09579a2c00cb2cc0a38c421969861f9c6a0

SHA256

83e7efdf3bd38eb806b30c81603e4eefe5ee17f88fa9c6440fd56d11c86d2869

SHA512

3ccc62d52899ecad9fd7626bb15f90b05bcabaf761d997c4aa63849f93702c6caf32d1f6ed191c981054c1df853ec6fbcdbd07fba0e76e289d4f71d39b542d9b

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.19.2 release is only compatible with Humio release 1.16.0 and newer. This means that you will have to ensure that you have upgraded to minimum 1.16.0 before trying to upgrade to 1.19.2. 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.

  • Fixed automatic installation of Humio Insights package to the humio repository