Humio Server 1.11.0 Preview (2020-05-19)

VersionTypeRelease DateEnd of SupportUpgrades FromData MigrationConfig. Changes
1.11.0Preview2020-05-192021-05-191.10.0YesYes
JAR ChecksumValue
MD570406b0710c9c999ec5293357e03b05a
SHA1f50294f5d0267d582d7207f7df33e16eee2744af
SHA256c1a79a8f1ca41e14158992ba5dfff0a05ce39292b5ed5bfa8d5507973d054fdb
SHA512f0f210d24aac849457839588202d662294911bf095e0f5a791093c61c435969b300f0a303d457a0e8cdbb13d742a81b3d09c6e11fad28f927ee9782153d05fc8

Export to Bucket, findTimestamp(), selfjoin(), Emergency User Sub-System

The selfJoin() query function allows selecting log lines that share an identifier; for which there exists (separate) log lines that match a certain filtering criteria; such as "all log lines with a given userid for which there exists a successful and an unsuccessful login".

The findTimestamp() query function will try to find and parse timestamps in incoming data. The function should be used in parsers and support automatic detection of timestamps. It can be used instead of making regular expressions specifying where to find the timestamp and parsing it with parseTimestamp(). See the findTimestamp() reference page for details.

As an alternative to downloading streaming queries directly, Humio can now upload them to an S3 or GCS bucket from which the user can download the data. See Bucket Storage.

If there are issues with the identity provider that Humio is configured to use, it might not be possible to log in to Humio. To mitigate this, Humio now provides emergency users that can be created locally within the Humio cluster. See Emergency Access.

Behavior Changes

Scripts or environment which make use of these tools should be checked and update for the new configuration:

Bug Fixes