Humio Server 1.2.0 Archive (2018-12-11)
|Version||Type||Release Date||End of Support||Upgrades From||JDK Compatibility||Data Migration||Config. Changes|
Create parsers using Humio's search language. Changes to "Backup" layout.
Blacklist queries. In the administration section of Humio it is now possible to blacklist queries. This can also be done from the
Query Monitorpage, by clicking a query and then block it in the details section, or using the Query Blacklist page directly.
New parsers. It is now possible to create parsers using Humio's search syntax. Check out the Creating a Parser documentation. Existing parsers has not been migrated and it is still possible to use the old parsers. We encourage using the new parsers and will automatically migrate old parsers in a future release.
The parser overview page now shows parser errors. This is a quick way to detect if parsers are working as expected.
parseTimestamp()function has changed signature. The parameter
nowIfNonehas been removed and a new
addErrorsintroduced. This can break existing searches/alerts/dashboards (but the parameter has not been widely used). See docs
In a cluster where any node did not have any digest roles, queries could get polled much too frequently.
kvParse()function no longer overrides existing fields by default. To override existing fields based on input use:
kvParse(override=true). See docs
The backup feature now stores the copies of the segment files in separate folders for each Humio node. This allows the Humio nodes to delete files that are no longer owned by that node also in the case where all Humio nodes share a shared network drive. This change has the effect that existing backups are no longer valid and cannot be read by this version. Delete any existing backups when upgrading, or reconfigure Humio to use a fresh location for the backups.