Humio Server 1.16.0 Stable (2020-10-09)
|Version||Type||Release Date||End of Support||Upgrades From||JDK Compatibility||Data Migration||Config. Changes|
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
searching. This will support use cases where data is backfilled
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
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
STORAGE_REPLICATION_FACTOR configurations). See
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
property instead of the
Automation and Alerts
Add view to log lines for alerts
Fixed a problem where it was not possible to rename a dashboard.
Fixed an issue where Humio could behave incompatibly with Kafka versions prior to 2.3.0 if
Added metrics for:
JVM Garbage Collection
JVM Memory usage
Missing nodes count
Fixed missing cache update when deleting a view.
Improved merging of segments by evaluating less data.
Fixed a problem preventing saved queries from being edited.
Fixed a problem with the retention job calculating what segments to delete.
Fixed a problem preventing file export/download from the search page.
Support for license files in ES512 format.
Fixed several cases where Humio might attempt to write a larger message to Kafka than what Kafka allows.
Bulk Global operations for segments in S3 to avoid overloading Kafka with writes.
Fixed a problem where the Zone configuration would not be propagated correctly.
Log query total cost when logging query information.
Log Humio cluster version in non-sensitive log.
Added background job to fix problems with inconsistent data in global.
Other changes: (see 1.15.1 release notes)
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)
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 a problem where errors would not be shown in the UI
Changed limits for what can be fetched via HTTP from inside Humio.
Major changes: (see 1.15.0 release notes)
Fixed a problem where some deleted segments could show up as missing.