Humio Server 1.16.0 Stable (2020-10-09)

VersionTypeRelease DateEnd of SupportUpgrades FromData MigrationConfig. Changes
JAR ChecksumValue

This release promotes the latest 1.15 release from preview to stable. To see more details, go through the individual 1.15.x release notes (links in the changelog).

Humio will set ingest timestamps on all events. This is set in the field named @ingesttimestamp. In later versions, Humio will also support specifying the search time interval using @ingesttimestamp when searching. This will support use cases where data is backfilled etc.

Field based throttling: It is now possible to make an alert throttle based on a field, so that new values for the field trigger the alert, but already seen values do not until the throttle period has elapsed.

Notifier logging to a Humio repository: It is now possible to configure an alert notifier that will log all events to a Humio repository.

Slack notifier upgrade to notify multiple Slack channels: It is now possible to use the Slack notifier to notify multiple Slack channels at once.

Events as HTML table: In an email notifier, it is now possible to format the events as an HTML table using the new message template {events_html}. Currently, the order of the columns is not well-defined. This problem will be fixed in the 1.17.0 release.

Configure notifier to not use the internet proxy: It is now possible to configure an alert notifier to not use the HTTP proxy configured in Humio.

Redesigned signup and login pages. For cloud, we have have split the behavior so users have to explicitly either login or signup.

Invite flow: When adding a user to Humio they will now by default get an email telling them that they have been invited to use Humio.

Configure Humio to not use the internet proxy for S3: It is now possible to configure Humio to not use the globally configured HTTP proxy for communcation with S3.

Auto-Balanced Partition Table Suggestions

When changing digest and storage partitions it is now possible to get auto-balanced suggestions based on node zone and replication factor settings (via ZONE, DIGEST_REPLICATION_FACTOR and STORAGE_REPLICATION_FACTOR configurations). See Configuration reference pages.

The AWS SDK Humio uses has been upgraded to v2. When configuring Humio bucket storage with Java system properties, the access key must now be in the aws.secretAccessKey property instead of the aws.secretKey property.

Bug Fixes

  • Other

    • Fixed a problem where the Zone configuration would not be propagated correctly.

    • Fixed a problem where errors would not be shown in the UI

    • Other changes: (see 1.15.1 release notes)

    • Support for license files in ES512 format.

    • Add view to log lines for alerts

    • Fixed a problem preventing file export/download from the search page.

    • Improved merging of segments by evaluating less data.

    • Fixed an issue where Humio could behave incompatibly with Kafka versions prior to 2.3.0 if KAFKA_MANAGED_BY_HUMIO was true.

    • Fixed a problem with the retention job calculating what segments to delete.

    • Fixed several cases where Humio might attempt to write a larger message to Kafka than what Kafka allows.

    • Added metrics for:

      • JVM Garbage Collection

      • JVM Memory usage

      • Missing nodes count

    • Fixed a problem preventing saved queries from being edited.

    • Log query total cost when logging query information.

    • Added background job to fix problems with inconsistent data in global.

    • Log Humio cluster version in non-sensitive log.

    • Bulk Global operations for segments in S3 to avoid overloading Kafka with writes.

    • Fixed a problem where some deleted segments could show up as missing.

    • Fixed a problem with auto sharding not working when two repositories had the same tags but differing shard counts.

    • Other changes: (see 1.15.2 release notes)

    • Major changes: (see 1.15.0 release notes)

    • Fixed a problem where the QueryScheduler could spend time idling even though there was work to do in situations where digest delays were high.

    • Fixed missing cache update when deleting a view.

    • Fixed a problem where it was not possible to rename a dashboard.

    • Changed limits for what can be fetched via HTTP from inside Humio.