Humio Server 1.18.0 Stable (2020-11-26)
|Version||Type||Release Date||End of Support||Upgrades From||Data Migration||Config. Changes|
Important Information about Upgrading
This release promotes the latest 1.17 release from preview to stable.
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.0 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.18.0. 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.
Humio can now run repeating queries using the beta:repeating()
function. These are live queries that are implemented by
repeatedly making a query. This allows using functions in alerts
and dashboards that typically do not work in live queries, such
selfJoinFilter(). See the
beta:repeating() reference page for more
In order to prevent alert notifiers being used to probe services
on the internal network (eg. Zookeeper or the AWS metadata
service), Humio now has an IP filter on alert notifiers. The
default is to block access to all link-local addresses and any
addresses on the internal network; however, you can opt-in to
the old behavior by setting the configuration option
allow all. See
IP Filter documentation.
New Experimental Query Function series()
A new experimental query function called
series() has been added. It needs to be
explicitly enabled on the cluster using the config option
series() improves upon
collect() for grouping events into
transactions. What used to be done with: groupby(id,
function=session(function=collect([fields, ...]))) can now be
done using: groupby(id, function=series([fields, ..])).
series() reference page for more
This new feature stores a copy of live search results to the local disk in the server nodes, and reuses the relevant parts of that cached result when an identical live search is later started. Caching is controlled with the config option QUERY_CACHE_MIN_COST, which has a default value of .0. To disable caching, set the config option to a very high number, such as 9223372036854775807 (max long value).
To see more details, go through the individual 1.17.x release notes (links in the changelog).
Fixed a bug where TCP listener threads could take all resources from HTTP threads
Changed behaviour when the config ZONE is set to the empty string. It is now considered the same as omitting ZONE.
Major changes (see 1.17.0 release notes)
Removed config IDLE_POLL_TIME_BEFORE_DASHBOARD_QUERY_IS_CANCELLED_MINUTES. Queries on dashboards now have the same life cycle as other queries.