Humio Server 1.5.8 Archive (2019-04-25)
|Version||Type||Release Date||End of Support||Upgrades From||JDK Compatibility||Data Migration||Config. Changes|
New dashboard editing code and many other improvements
Humio's own Jitrex regular expression engine is again the default one.
Alerts notifiers with standard template did not produce valid JSON.
parseTimestamp()now handles dates, e.g. 31-08-2019.
The Auth0 integration now supports importing Auth0-defined roles. New config
AUTH0_ROLES_KEYidentifies the name of the role attribute coming in the AWT token from Auth0. See new auth0 config options Map Auth0 Roles.
@source and @host is now supported for Filebeat v7.
Dashboard queries that are not live and uses a timeinterval relative to now, are migrated to be live queries. Going forward, queries with timeintervals relative to now will be live queries when added to dashboards.
In tableview, if column data is of the form
\[Label](URL)it is displayed as
Labelwith a link to URL.
S3 archiving now supports forward proxies.
Validation of bucket and region when configuring S3 archiving.
Built-in audit-log parser now handles a variable number of fractions of seconds.
>KAFKA_DELETES_ALLOWEDhas been removed and instead
DELETE_ON_INGEST_QUEUEis set to
trueby default. When this flag is set, Humio will delete data on the Kafka ingest queue, when data has been written in Humio. If the flag is not set, Humio will not delete from the ingest queue. No matter how this flag is set, it is important to configure retention for the queue in Kafka. If Kafka is managed by Humio, Humio will set a 48hour retention when creating the queue. This defines how long data can be kept on the ingest queue and thus how much time Humio has to read the data and store it internally.