Humio Server 1.18.4 LTS (2021-01-25)

Version?Type?Release Date?Availability?End of Support

Security

Updates

Upgrades

From?

Config.

Changes?
1.18.4LTS2021-01-25

Cloud

2021-11-30No1.16.0No

Hide file hashes

Show file hashes

These notes include entries from the following previous releases: 1.18.0, 1.18.1, 1.18.2, 1.18.3

Important Information about Upgrading

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.4 release is only compatible with Humio release 1.16.0 and newer. This means that you will have to ensure that you have upgraded at least to 1.16.0 before trying to upgrade to 1.18.4. 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.

Fixed in this release

  • Automation and Alerts

    • Fixes a bug where some valid repeating queries would not validate in alerts.

  • Other

    • 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)

    • Fixed a bug where TCP listener threads could take all resources from HTTP threads

    • Do not retry a query when getting a HTTP .0 error

    • Update dependencies with known vulnerabilities

    • Fixes a bug that would allow users with read access to be able to delete a file (#10133)

    • Improve handling of a node being missing from the cluster for a long time by letting other nodes handle the parts of the query that node would normally do.

    • Add non-sensitive logging that lists the versions of Humio running in the cluster. These logs can be found by searching the Humio debug log for "cluster_versions".

    • Improve performance of S3 archiving when many repositories have the feature enabled.

    • Resolves problem when starting a query spanning very large data sets, a time-out could prevent the browser from getting responses initially.

    • Adds a new configuration option for auth0: AUTH_ALLOW_SIGNUP. Default value is true.

    • Fixes a bug where top([a,b], sum=f) ignored events where f was not a positive integer. Now it ignores negative and non-numerical input but rounds decimal numbers to integer value.

    • Do not cache cancelled queries.

    • Removed config IDLE_POLL_TIME_BEFORE_DASHBOARD_QUERY_IS_CANCELLED_MINUTES. Queries on dashboards now have the same life cycle as other queries.

    • Improves handling when many transfers to secondary storage are pending.

    • Fixes a bug where the to parameter to unit:convert would cause internal server errors instead of validation errors.

    • Add GraphQL mutation to update the runAsUser for a read only dashboard token.

    • Fixes a bug where queries with @timestamp=x where x was a timestamp with the current search interval could fail

    • Fixes a bug where a query would not start automatically when requesting to filter or group by a value.

    • Fixes a bug where the merge of mini segments could fail during sampling of input for compression.

    • Fixes a bug where the permissions check on editing a connection from a view to a repository allowed altering the search prefix of connections other than the one the user currently was allowed to edit.

    • Fixed an issue for on-prem users not on multitenant setup by reverted a metric change introduced in 1.18.0, jmx and Slf4j included an OrgId in all metrics for repositories.

    • Fixed bug where the format() function produced wrong output for some floating-point numbers.

    • Increase number of vCPUs used when parsing TCP ingest, twice the number of the 1.18.0 build.

    • Fixed bug so as to reduce contention on the Query input queue.

    • Only install default Humio parser to the Humio view if it is missing. No longer overwriting local changes.

    • Fixed bug where Humio could end in a corrupted state, needing manual intervention before working again.