Humio Server 1.5.19 Archive (2019-07-03)

VersionTypeRelease DateEnd of SupportUpgrades FromData MigrationConfig. Changes
1.5.19Archive2019-07-032019-11-191.5.8NoNo
JAR ChecksumValue
MD5fa9d61d17a037583bbe067a4aab64ab3
SHA11793534d22cfc53c5b15dde0dc60d008ad9c9204
SHA2566e21cd3874a948a3ddf3554911c3104e60a2ca33e8e4a039755eca42c03e1508
SHA512ec09a60164c981970b20fd401140a5dac2e3814f6e1254c3472721ace2db957b92f9035b8833436008054220385b55e1e83b93f6b1547842c289a0194522913c

File based parameters on dashboards. This release makes it easier to configure load balancers by adding sticky session headers to most UI Http requests.

The existing header Humio-Query-Session is used. For non-search related HTTP requests it will contain a random sticky session ID. For search related HTTP requests it contains a hash of the query being executed - just like it has done previously.

New file based parameter type is added to dashboards.

Bug Fixes

  • Other

    • New type of parameter: Dashboards can now have file based parameters, which are populated with data from files uploaded to Humio

    • The HTTP request header Humio-Query-Session is now added to most requests from the UI.

    • Improved performance on servers with many cores for functions (such as top) that may require large states internally.

    • New shared files. Shared files can be used like the existing files, that are uploaded to repositories. A shared file is visible in all repositories and can be used by everyone. Only root users can create and manage them. For now, shared files can only be added using Humio's Lookup API. Shared files are visible in the files tab in all repositories for all users. Root users can also edit and delete shared files there. Shared files can be used from query functions like function lookup() and function match() they are referenced using the path /shared/filename.

    • Make failover to the next node in digest when a node gets shut down gracefully faster by delaying the shutdown a few seconds while letting the follower catch up.

    • Bug Fix: Fixed Interval Queries on dashboards used the time of the dashboard being loaded as the definition of "now". It will now use the time of the last change in the dashboard's global time.