Stable Releases

Below is a list of all of the Stable releases of Humio, in reverse order of their release — the latest at the top and the oldest at the bottom. If you want to see all of the Preview releases go to the Preview Releases page for a list of them. For a list of all releases, Preview and Stable, go to the All Releases page.

Remember, the way to distinguish between Preview and Stable releases is based on the secondary number for the release. If it’s an even number, it indicates it’s a stable release; if the secondary number is an odd number, it indicates it’s a preview of the stable release that will follow it. See the main Humio Releases page for a more detailed explanation of this numbering system.

1.24.2

Minor bug fix release

Release Date: 2021-04-19
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.24.1 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.24.1. 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.

Changelog

  • Fixed an issue where cost spent in a long-running query got accounted as spent “now” when the query ended in terms of Query Quota
  • Fixed an issue where a repository with very high number of datasources could trigger an error writing an oversized message to kafka from the ingest-reader-leader thread
  • Reduced off-heap memory usage

1.24.1

Minor bug fix release

Release Date: 2021-04-12
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.24.1 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.24.1. 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.

Changelog

  • Ensure that if the Kafka leader loop thread dies, it kills the Humio process. In rare cases it was possible for this thread to die, leaving the node incapable of performing digest work
  • Allow reverse proxies using 10s as timeout to work also for a query that takes longer than that to initialize
  • Fixes an issue where the user would get stuck in infinite loading after having been invited into an organization
  • Fixed a bug where ingestOnly nodes could not start on a more recent version that the statefull nodes in the cluster

1.24.0

Humio activity log and GraphQL API policy

Release Date: 2021-04-06
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: true

This release promotes the latest 1.23 release from preview to stable.

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.24.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 at least to 1.16.0 before trying to upgrade to 1.24.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.

New humio-activity repository

Humio will make some internal logs available in a new repository called humio-activity. This is meant for logs that are relevant to users of Humio, as compared to logs that are only relevant for operators. The latter logs are still put into the humio repository. For this release, only new log events will be put into humio-activity, but in later releases, some existing log events that are relevant for users, will be put into the humio-activity repository instead of the humio repository.

For cloud users, the logs for your organization can be accessed through the humio-organization-activity view.

For on-prem users, the logs can be accessed directly through the humio-activity repository. They are also output into a new log file named humio-activity.log which can be ingested into the humio repository, if you want it available there as well. If you do and you are using the Humio Insights Application, you should upgrade that to version 0.0.4. For more information, see docs.

GraphQL API policy

Humio has decided to adopt an evoutionary approach to its GraphQL API, meaning that we will strive to do only backwards compatible changes. Instead of making non-backwards compatible changes to existing fields, we will instead add new fields alongside the existing fields. The existing fields will be deprecated and might be removed in some later release. We reserve the right to still do non-backwards compatible changes, for instance to fix security issues.

For new experimental features, we will mark the corresponding GraphQL fields as PREVIEW. There will be no guarantees on backwards compatibility on fields marked as PREVIEW.

Deprecations and preview

Deprecated and preview fields and enum values will be marked as such in the GraphQL schema and will be shown as deprecated or preview in the API Explorer. Apart from that, the result of running a GraphQL query using a deprecated or preview field will contain a new field extensions, which contains a field deprecated with a list of all deprecated fields used in the query and a field preview with a list of all preview fields used in the query. Example:

{
  "data": ...
  "extensions": {
    "deprecated": [
      {
        "name": "alert",
        "reason": "[DEPRECATED: Since 2020-11-26. Deprecated since 1.19.0. Will be removed March 2021. Use 'searchDomain.alert' instead]"
      }
    ]
  }
}

Deprecated fields and enum values will also be noted in the release note, when they are first deprecated. All use of deprecated fields and enum values will also be logged in the Humio repository humio-activity. They will have #category=GraphQL, subCategory=Deprecation and #severity=Warning. If you are using the API, consider creating an alert for such logs.

Removed support for CIDR shorthand

Previous version of Humio supported a shorthand for IPv4 CIDR expressions.

For example 127.1/16 would be equivalent to 127.1.0.0/16. This was contrary to other implementations like the Linux function inet_aton, where 127.1 expands to 127.0.0.1. Support for this shorthand has been removed and the complete address must now be written instead.

Changelog

  • Major changes: 1.23.0 1.23.1
  • Fixed a scrolling issues on the Kafka cluster admin page
  • Fixed an issue which prevented Safari users from seeing alert actions
  • Fixed an issue which caused problems with forward/backward compatibility of LanguageVersion in GraphQL
  • Fixed an issue on the search page that prevented the event list from scrolling correctly.
  • Removed the QUERY_QUOTA_EXCEEDED_PENALTYconfig (introduced in 1.19.0).
  • The query scheduler now prioritizes new queries started by a user based on the cumulative cost of recent queries started by that user. Added new config QUERY_SPENT_FACTOR with the default value 0.5, which defines the weight of recent query costs when scheduling. Higher values mean that users with high recent query costs will see their queries penalized harder in the scheduling.

1.22.1

Minor bug fix release

Release Date: 2021-03-02
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.22.1 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.22.1. 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.

Changelog

  • Fixes problem where alertpages have no height in safari.
  • Fixes parserlist having no height on safari
  • Fixes overflowing editor bug

1.22.0

Complete UI revamp

Release Date: 2021-03-02
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: true

This release promotes the latest 1.21 release from preview to stable.

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.22.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 at least to 1.16.0 before trying to upgrade to 1.22.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.

UI revamp

In this version the UI has been given a complete makeover.

Details

To see more details, go through the individual 1.21.x release notes (links in the changelog).

Changelog

  • Major changes: 1.21.0 1.21.1
  • Fixed issue where root users were not allowed to set unlimited time in retention settings
  • Fixed issue where tag filters in anonymous parts within an aggregate did not get applied
  • Increase HTTP chunk size from 16MB to 128MB
  • Add the “ProxyOrganization” header to the list of general auth headers used on REST calls
  • Restrict concurrency when mirroring uploaded files within the cluster
  • Change log lines creating a ‘kind’ field. Kind is used as a tag for the different humio logs
  • Fix issue where updating account settings would present the user with an error even though the update was successful
  • Fixed issue where local segment files would not get deleted in time, potentially filling the disk

1.20.4

Minor bug fix release

Release Date: 2021-02-22
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.20.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.20.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.

Changelog

  • Fixed an issue causing event redirection to break when using copyEvent() to get the same events forwarded to multiple repositories.
  • Connecting to the Package Marketplace now respects the Humio proxy configuration
  • Fix newline glob handling in in() and match()

1.20.3

Minor bug fix release

Release Date: 2021-02-16
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.20.3 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.20.3. 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.

Changelog

  • Improve auto completion suggestions.

1.20.2

Minor bug fix release

Release Date: 2021-02-11
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.20.2 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.20.2. 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.

Changelog

  • Improve query cache hit rate by not starting queries locally when the preferred nodes are down, if the local node has just started - as there is a fair chance the preferred nodes will show up shortly too.
  • Query scheduling now tracks cost spent across queries for each user and tends to select next task so that users (rather than queries) each get a fair share of available CPU time.
  • Fixed a bug that exporting a package using a saved query with spaces in the name would not export the correct name.
  • Fixed a bug that exporting a package with dashboard parameters would not set the correct name space for a saved query called in a parameter.
  • Reduce triggering of auto completion in the query editor.
  • Handle inconsistencies in the global entities file gracefully rather than crashing.
  • Fixed a bug in parseJson which resulted in failed JSON parsing if an object contained an empty key ("").
  • Fixed a bug in upper() and lower() which could cause its output to be corrupted (in cases where no characters had been changed).
  • Fixed a bug where fields panel was not scrollable in safari
  • Fixed an issue where some parts of regexes did not shown in the parser editor
  • Fixed an issue where cloning a dashboard or parser would clone the wrong entity

1.20.1

Minor bug fix release

Release Date: 2021-02-01
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.20.1 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.20.1. 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.

Changelog

  • Minor fix to Humio internal JSON logging when using the configuration HUMIO_LOG4J_CONFIGURATION=log4j2-json-stdout.xml

1.20.0

New query editor, Packages (in beta)

Release Date: 2021-01-28
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: true

This release promotes the latest 1.19 release from preview to stable.

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.20.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 at least to 1.16.0 before trying to upgrade to 1.20.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.

Packages

This version introduces Humio packages - a way of bundling and sharing assets such as dashboards and parsers. You can create your own packages to keep your Humio assets in Git or create utility packages that can be installed in multiple repositories. All assets can be serialized to YAML files (like what has been possible for dashboards for a while). With tight integration with Humio’s CLI humioctl you can install packages from local disk, URL, or directly from a Github repository. Packages are still in beta, but we encourage you do start creating packages yourself, and sharing them with the community. At Humio we are also very interested in talking with package authors about getting your packages on our upcoming marketplace. Read more about packages on our package documentation.

Humio Insights application

With the introduction of Humio packages we have created the application Humio Insights. The application is a collection of dashboards and saved searches making it possible to monitor and observe a Humio cluster.

New Query Editor

The new query editor has a much better integration with Humio’s query language. It will give you suggestions as you type, and gives you inline errors if you make a mistake. We will continue to improve the capabilities of the query editor to be aware of fields, saved queries, and other contextual information.

If Humio is running behind a reverse proxy, it must be configured to permit WebSockets to pass through. Given this scenario, if when using the query editor in Humio, if you’re not seeing syntax coloring, it’s an indication that this is not yet configured and the reverse proxy is blocking the sockets. (edited)

New Test Function

A new function called test() has been added for convenience. What used to be done like: tmp := <expression> | tmp=true can now be done using: test( <expression> ). Inside <expression> field names appearing on the right hand side of an equality test, such as field1==field2 compares the values of the two fields. When comparing using = at top-level field1=field2 compares the value of field1 against the string "field2". This distinction is a cause of confusion for some users, and using test() simplifies that.

Changes to Humio’s internal logging

We have made small changes to how Humio logs internally. We did this to better support the new Humio Insights Application. We have tried to keep the changes as small and compatible as possible, but we have made some changes that can break existing searches in the humio repository (or other repositories receiving Humio logs). We made these changes as we think they are important in order to improve things moving forward. One of the benefits is the new Humio Insights App Read more about the details here

Details

To see more details, go through the individual 1.19.x release notes (links in the changelog).

Changelog

  • Major changes: 1.19.0
  • Fixed an issue causing the secondary storage transfer job to plan more segments for transfer than necessary.
  • Segment download timeout raised from 120s to 1800s. Avoids situations where large segments could not be moved around a cluster.
  • Fixed a bug where merged segments could grow too large if the source events were large.
  • Enable Package marketplace (in beta)

1.18.4

Bug fix release

Release Date: 2021-01-25
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.

Changelog

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

1.18.3

Bug fix release

Release Date: 2021-01-20
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.3 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.3. 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.

Changelog

  • Fixed bug where the format() function produced wrong output for some floating-point numbers
  • Update dependencies with known vulnerabilities
  • Do not retry a query when getting a HTTP 400 error
  • Do not cache cancelled queries.

1.18.2

Bug fix release

Release Date: 2021-01-08
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.2 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.2. 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.

Changelog

  • Fixed bug where Humio could end in a corrupted state, needing manual intervention before working again.
  • Fixed bug so as to reduce contention on the Query input queue.
  • Adds a new configuration option for auth0: AUTH_ALLOW_SIGNUP. Default value is true.
  • Resolves problem when starting a query spanning very large data sets, a time-out could prevent the browser from getting responses initially.
  • Improves handling when many transfers to secondary storage are pending.

1.18.1

Bug fix release

Release Date: 2020-12-17
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false

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.1 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.1. 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.

Changelog

  • Fixes a bug where some valid repeating queries would not validate in alerts
  • Fixes a bug where the merge of mini segments could fail during sampling of input for compression.
  • Fixes a bug where a query would not start automatically when requesting to filter or group by a value.
  • Fixes a bug that would allow users with read access to be able to delete a file (#10133)
  • Fixes a bug where queries with @timestamp=x where x was a timestamp with the current search interval could fail
  • 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.
  • 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.
  • Fixes a bug where the to parameter to unit:convert would cause internal server errors instead of validation errors.
  • Only install default Humio parser to the Humio view if it is missing. No longer overwriting local changes.
  • Add GraphQL mutation to update the runAsUser for a read only dashboard token.
  • Increase number of vCPUs used when parsing TCP ingest, twice the number of the 1.18.0 build.
  • 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.
  • Improve performance of S3 archiving when many repositories have the feature enabled.
  • 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”.

1.18.0

Repeating Queries, search result caching and new query functions.

Release Date: 2020-11-26
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: true

Repeating Queries, search result caching and new query functions.

This release promotes the latest 1.17 release from preview to stable.

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.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.

Repeating Queries

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 as selfJoin() or selfJoinFilter(). See the function docs for more information.

Improved Security for Alerts

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 IP_FILTER_NOTIFIERS to 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_ENABLED=true.

series() improves upon session() and 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, ..])).

See docs for more details.

Search result caching

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 1000. To disable caching, set the config option to a very high number, such as 9223372036854775807 (max long value).

Details

To see more details, go through the individual 1.17.x release notes (links in the changelog).

Changelog

  • Major changes: 1.17.0
  • Removed config IDLE_POLL_TIME_BEFORE_DASHBOARD_QUERY_IS_CANCELLED_MINUTES. Queries on dashboards now have the same life cycle as other queries.
  • Changed behaviour when the config ZONE is set to the empty string. It is now considered the same as omitting ZONE.
  • Fixed a bug where TCP listener threads could take all resources from HTTP threads

1.16.4

Bugfixes

Release Date: 2020-11-26
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Bugfixes

Changelog

  • Fixed an issue causing Humio to fail to upload files to bucket storage in rare cases.
  • Switched from JDK to BouncyCastle provider for AES decrypt to reduce memory usage.
  • Fix negating join expressions.
  • Fixed a bug causing sort/head/tail to work incorrectly after other aggregating functions.
  • Fixed a bug causing the sub-queries of join etc. not to see events with an @ingesttimestamp occurring later than the search time interval.
  • Fixed a bug where the {events_html} message template was formatted as raw HTML in alert emails.
  • Fixed a bug where TCP listener threads could take all resources from HTTP threads.
  • Fixed an issue preventing the metric datasource-count from counting datasources correctly.

1.16.3

Bugfixes

Release Date: 2020-11-10
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Bugfixes

Changelog

  • Reduce memory usage when using the “match” or “regex” query functions.
  • Fixed an issue where cleanup of empty datasource directories could race with other parts of the system and cause issues.
  • Fixed an issue when starting a query, where resources related to HTTP requests were not released in a timely manner, causing an error log when the resources were released by hitting a timeout.
  • Fixed an issue which caused free-text-search to not work correctly for large (>64KB) events.

1.16.2

Email and global database improvements

Release Date: 2020-10-30
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Email and global database improvements

Changelog

  • Optimize how certain delete operations in the global database are performed to improve performance in large clusters.
  • Prevent automatic url to link conversion in email clients.

1.16.1

Bug fixes and stability enhancements.

Release Date: 2020-10-21
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes and stability enhancements.

Changelog

  • Fixed an issue where errors were not properly shown in the Humio UI.
  • Convert some non-fatal logs to warning level instead of error.
  • Avoid logging the license key.
  • Ensure metric label names can be sent to Prometheus.
  • Fixed an issue with truncating files on the XFS file system, leading to excess data usage.
  • Fixed an issue where it was impossible to bootstrap a new cluster if ingest or storage replication factors had been configured greater than 1.
  • Fixed an issue where RegEx field extraction did not work in a query.
  • Fixed an issue where missing input validation in alerts could lead to HTML injection in email notifications.
  • Improved the performance for GroupBy.
  • Added new metric jvm-hiccup for measuring stalls/pauses in the JVM.
  • Fixed an issue where sorting of work in the Humio input could end up being wrong.
  • Log information about sorting of snapshots.
  • Raise time to wait until deleting data to improve handling of node failures.
  • Add query parameter sanitization for login and signup pages.
  • HTML sanitization for user fields in invitation mails.
  • Returning bad request when hitting authentication endpoint without a provider id.

1.16.0

Improved alerts and addition of ingest timestamps

Release Date: 2020-10-09
Minimum previous Humio version: 1.12.0
Requires data migrations: true
Has changes to configuration: true

This release promotes the latest 1.15 release from preview to stable.

New features

Ingest timestamps

Humio will set ingest timestamps on all events. This is set in the field named @ingesttimestamp. In later versions, Humio will also support specifying the search time interval using @ingesttimestamp when searching. This will support use cases where data is backfilled etc.

Alerts and notifiers

Field based throttling

It is now possible to make an alert throttle based on a field, so that new values for the field trigger the alert, but already seen values do not until the throttle period has elapsed. See docs.

Notifier logging to a Humio repository

It is now possible to configure an alert notifier that will log all events to a Humio repository. See docs.

Slack notifier upgrade to notify multiple Slack channels

It is now possible to use the Slack notifier to notify multiple Slack channels at once. See docs.

Events as HTML table

In an email notifier, it is now possible to format the events as an HTML table using the new message template {events_html}. Currently, the order of the columns is not well-defined. This problem will be fixed in the 1.17.0 release. See docs.

Configure notifier to not use the internet proxy

It is now possible to configure an alert notifier to not use the HTTP proxy configured in Humio. See docs.

User signup/login flow

Signup & Login

Redesigned signup/login pages. For cloud, we have have split the behavior so users have to explicitly either login or signup.

Invite flow

When adding a user to Humio they will now by default get an email telling them that they have been invited to use Humio. See docs.

Configure Humio to not use the internet proxy for S3

It is now possible to configure Humio to not use the globally configured HTTP proxy for communcation with S3. See docs.

Auto-balanced partition table suggestions

When changing digest and storage partitions it is now possible to get auto-balanced suggestions based on node zone and replication factor settings (via ZONE, DIGEST_REPLICATION_FACTOR and STORAGE_REPLICATION_FACTOR configurations). See docs.

Breaking changes

AWS Java SDK V2

The AWS SDK Humio uses has been upgraded to v2. When configuring Humio bucket storage with Java system properties, the access key must now be in the aws.secretAccessKey property instead of the aws.secretKey property.

Details

To see more details, go through the individual 1.15.x release notes (links in the changelog).

Changelog

  • Major changes: 1.15.0
  • Other changes: 1.15.1
  • Other changes: 1.15.2
  • Fixed missing cache update when deleting a view.
  • Fixed a problem where it was not possible to rename a dashboard.
  • Added metrics for:
    • JVM Garbage Collection
    • JVM Memory usage
    • Missing nodes count
  • Add view to log lines for alerts
  • Log query total cost when logging query information.
  • Fixed a problem where some deleted segments could show up as missing.
  • Added background job to fix problems with inconsistent data in global.
  • Changed limits for what can be fetched via HTTP from inside Humio.
  • Log Humio cluster version in non-sensitive log.
  • Fixed a problem preventing file export/download from the search page.
  • Fixed a problem preventing saved queries from being edited.
  • Fixed a problem where errors would not be shown in the UI
  • Fixed several cases where Humio might attempt to write a larger message to Kafka than what Kafka allows.
  • Fixed an issue where Humio could behave incompatibly with Kafka versions prior to 2.3.0 if KAFKA_MANAGED_BY_HUMIO was true.
  • Fixed a problem with the retention job calculating what segments to delete.
  • Fixed a problem where the QueryScheduler could spend time idling even though there was work to do in situations where digest delays were high.
  • Fixed a problem with auto sharding not working when two repositories had the same tags but differing shard counts.
  • Improved merging of segments by evaluating less data.
  • Bulk Global operations for segments in S3 to avoid overloading Kafka with writes.
  • Support for license files in ES512 format.
  • Fixed a problem where the Zone configuration would not be propagated correctly.

1.14.6

Email notification improvements

Release Date: 2020-10-30
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Email notification improvements.

Changelog

  • Fixed an issue where missing input validation in alerts could lead to HTML injection in email notifications.
  • Prevent automatic url to link conversion in email clients.

1.14.5

Bug fixes and new metric.

Release Date: 2020-10-21
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes and new metric.

Changelog

  • Fixed an issue where Humio might attempt to write a larger message to Kafka than what Kafka allows.
  • Fixed an issue where Humio could behave incompatibly with Kafka versions prior to 2.3.0 if KAFKA_MANAGED_BY_HUMIO was true.
  • Added new metric jvm-hiccup for measuring stalls/pauses in the JVM.

1.14.4

Bug fixes and stability enhancements.

Release Date: 2020-10-09
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes and stability enhancements.

Changelog

  • Avoid overloading Kafka with updates for the global database by collecting operations in bulk.
  • Fixed a problem where duplicated uploaded files would not be deleted from /tmp.
  • Log Humio cluster version in non-sensitive log.
  • Changed limits for what can be fetched via HTTP from inside Humio.
  • Fixed a problem where some deleted segments could show up as missing.
  • Fixed several cases where Humio might attempt to write a larger message to Kafka than Kafka allows.

1.14.3

Bug fixes and improved query scheduling.

Release Date: 2020-09-24
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes and improved query scheduling.

Changelog

  • Fix missing cache update when deleting a view.
  • Add logging to detect issues when truncating finished files.
  • Fixed an issue where a slow data stream could cause Humio to retain more data in Kafka than necessary, as well as cause a restarted Humio node to reprocess too much data.
  • Improve handling of sub-queries polling state from the main query when using join().
  • Change priorities when fetching segments to a node which have been offline for a longer period. This avoids waiting too long before the cluster becomes fully synced.
  • Changed the query scheduling to account for the work of the overall query, rather than per job started. This allows fairer scheduling of queries hitting many dataspaces e.g. when using search-all.
  • Improve naming of threads to get more usable thread dumps.

1.14.2

Bug fixes, HEC endpoint validation and new metrics

Release Date: 2020-09-17
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes, HEC endpoint validation and new metrics

Changelog

  • Fixed a race condition when cleaning up datasources.
  • Fixed a problem where segments could be downloaded to stateless frontend nodes from Bucket storage.
  • Fixed a problem where too many segments could be generated when restarting nodes.
  • HEC endpoint is now strictly validated as documented for top-level fields, which means non-valid input will be rejected. See docs.
  • Added log rotation for humio-non-sensitive logs.
  • The job for updating the IP location database now uses the configured HTTP proxy, if present. See docs.
  • Improved handling of data replication when nodes are offline.
  • Include user email in metrics when queries end.
  • New metrics for scheduling of queries:
    • local-query-jobs-wait: Histogram of time in milliseconds that each query waited between getting any work done including exports
    • local-query-jobs-queue: Count queries currently queued or active on node including exports
    • local-query-segments-queue-exports-part: Count of elements in queue as number of segments currently queued for query for exports
    • local-query-jobs-queue-exports-part: Count queries currently queued or active on node for exports

1.14.1

Bug fixes

Release Date: 2020-09-08
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes

Changelog

  • Improve performance when processing streaming queries.
  • Remove restriction on length of group names from LDAP.
  • Remove restriction on expire time when creating emergency user through the emergency user API. See Emergency Access.

1.14.0

Free text search, Load balancing of queries and TLS support.

Release Date: 2020-08-26
Minimum previous Humio version: 1.12.0
Requires data migrations: true
Has changes to configuration: true

This release promotes the latest 1.13 release from preview to stable.

Free text search now searches all fields rather than only the @rawstring field.

Load balancing of queries

Humio can now balance and reuse existing queries internally in the cluster. Load balancer configuration to achieve this is no longer needed. See Reverse proxy configuration and Humio Configuration.

TLS support

TLS Encrypt communication using TLS to/from Zookeeper, Kafka, and other Humio nodes.

Iplocation database management changed

The database used as data source for the ipLocation() query function must be updated within 30 days when a new version of the database is made public by MaxMind. To comply with this, the database is no longer shipped as part of the Humio artifacts but will either:

  • Be fetched automatically by Humio provided that Humio is allowed to connect to the db update service hosted by Humio. This is the default behaviour.
  • Have to be updated manually (See ipLocation())

If the database cannot be automatically updated and no database is provided manually, the ipLocation() query function will no longer work.

Configuration change: Controlling what nodes to use as query coordinators

Due to the load balancing in Humio, customers that previously relied on load balancing to control which nodes are query coordinators now need to set QUERY_COORDINATOR to false on nodes they do not want to become query coordinators. See Reverse proxy configuration and Humio Configuration.

To see more details, go through the individual 1.13.x release notes (links in the changelog).

Changelog

  • Major changes: 1.13.0
  • Other changes: 1.13.1
  • Other changes: 1.13.2
  • Other changes: 1.13.3
  • Other changes: 1.13.4
  • Other changes: 1.13.5
  • Improved handling of query restarts to avoid unnecessary restarts in some scenarios.
  • Handling of digest in the case where a node has been offline for a long time has been improved. As an example, running a Humio cluster with a replication factor of 2 and having one node go offline for a long time would leave some ingested data to only reside on one Humio node (and on the ingest queue in Kafka). But this data would not be regarded as properly replicated until the second node returned. If the only node that was left handling a digest partition did a failover, Humio would end up going far back on the Kafka ingest queue to reread data. This has been changed. Now another node from the set of digest nodes will take over if a node goes offline, to keep the replication factor as desired. This means that other hosts, than those specified for a given digest partition on the cluster management page, can actually be handling the digest data for that partition. Only digest nodes will be selected as hosts.

1.12.7

Bug fix and additional metrics

Release Date: 2020-09-17
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Bug fix and additional metrics

Changelog

  • New metrics for scheduling of queries:
    • local-query-jobs-wait: Histogram of time in milliseconds that each query waited between getting any work done including exports
    • local-query-jobs-queue: Count queries currently queued or active on node including exports
    • local-query-segments-queue-exports-part: Count of elements in queue as number of segments currently queued for query for exports
    • local-query-jobs-queue-exports-part: Count queries currently queued or active on node for exports
  • Fixed a race condition when cleaning up datasources

1.12.6

Bug fixes

Release Date: 2020-09-03
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes

Changelog

  • Improved handling of query restarts to avoid unnecessary restarts in some scenarios.
  • Remove restriction on length of group names from LDAP.

1.12.5

Security and bug fixes

Release Date: 2020-08-12
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Security and bug fixes

Changelog

  • This release fixes a security issue. More information will follow when Humio customers have had time to upgrade. See: Humio Security Disclosures.
  • Bugfix: missing migration of non-default groups would result in alerts failing until the user backing the alert logs in again.
  • Bugfix: avoid forbidden access error on shared dashboard links by ensuring correct use of time stamps.
  • Fix issue where a node with no digest assignment could fail to delete local segment copies in some cases.

1.12.4

Security fix

Release Date: 2020-08-05
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Security fix

Changelog

1.12.3

Security fix

Release Date: 2020-08-04
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Security fix

Changelog

1.12.2

Bug fixes and improved search speeds for many-core systems

Release Date: 2020-07-03
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes and improved search speeds for many-core systems

Changelog

  • Improved query scheduling on machines with many cores. This can improve search speeds significantly.
  • Support for a new storage format for segment files that will be introduced in a later release (to support rollback)
  • Bugfix: S3Archiving could write events twice in a special case (When a merge happens where all inputs have been archived, write in global that the merge-result was archived too).
  • Bugfix: Bucket storage in GCP could did not clean up all tmp files

1.12.1

Bug fixes - Safari freeze, SAML, bucket storage cleanup, regex and field-aliasing

Release Date: 2020-06-24
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Bug fixes - Safari freeze, SAML, bucket storage cleanup, regex and field-aliasing

Changelog

  • Fixed an issue with CSP that could cause the Humio UI to freeze on Safari browsers
  • Fixed an issue that prevented deletion of unused objects in bucket storage, if the bucket contained 100 millions of objects or more
  • Fixed an issue with SAML IDPs requiring query parameters to be passed via the configuration SAML_IDP_SIGN_ON_URL
  • Fixed an issue where queries using lookahead in regex would fail to parse - “invalid or unsupported Perl syntax”
  • Fixed an issue where events could be skipped even though they should not, for queries containing field-aliasing (e.g., a:=b) and using subsequent checks on the aliasing field.

1.12.0

Export to bucket, findTimestamp, selfjoin, Emergency user subsystem

Release Date: 2020-06-09
Minimum previous Humio version: 1.10.0
Requires data migrations: true
Has changes to configuration: true

This release promotes the 1.11 releases from preview to stable.

SelfJoin

selfJoin query function allows selecting log lines that share an identifier; for which there exists (separate) log lines that match a certain filtering criteria; such as “all log lines with a given userid for which there exists a successful and an unsuccessful login”.

findTimestamp

findTimestamp query function will try to find and parse timestamps in incoming data. The function should be used in parsers and support automatic detection of timestamps. It can be used instead of making regular expressions specifying where to find the timestamp and parsing it with parseTimestamp. Checkout the documentation for details.

Export to bucket storage/S3

As an alternative to downloading streaming queries directly, Humio can now upload them to an S3 or GCS bucket from which the user can download the data. See docs

Emergency user subsystem

If there are issues with the identity provider that Humio is configured to use, it might not be possible to log in to Humio. To mitigate this, Humio now provides emergency users that can be created locally within the Humio cluster. See docs

Elastic Bulk API change - Fluent Bit users might need to change the Fluent Bit configuration

To ensure compatability with the newest Beats clients, the Elastic Bulk API has been changed to always return the full set of status information for all operations, as it is done in the official Elastic API.

This can however cause problems when using Fluent Bit to ingest data into Humio.

Fluent Bit in default configuration uses a small buffer (4KB) for responses from the Elastic Bulk API, which causes problems when enough operations are bulked together. The response will then be larger than the response buffer as it contains the status for each individual operation. Make sure the response buffer is large enough, otherwise Fluent Bit will stop shipping data. See: https://github.com/fluent/fluent-bit/issues/2156 and https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch

To see more details go through the individual 1.11.x release notes (links in the changelog).

Changelog

1.10.9

Security fix

Release Date: 2020-08-05
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Security fix

Changelog

1.10.8

Security fix

Release Date: 2020-08-04
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false

Security fix

Changelog

1.10.7

Bug fixes and improved search speeds for many-core systems

Release Date: 2020-07-03
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false

Bug fixes and improved search speeds for many-core systems

Changelog

  • Improved query scheduling on machines with many cores. This can improve search speeds significantly.
  • Support for a new storage format for segment files that will be introduced in a later release (to support rollback)
  • Bugfix: S3Archiving could write events twice in a special case (When a merge happens where all inputs have been archived, write in global that the merge-result was archived too).
  • Bugfix: Bucket storage in GCP could did not clean up all tmp files

1.10.6

Bug fixes - Safari freeze, SAML and bucket storage cleanup

Release Date: 2020-06-24
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false

Bug fixes - Safari freeze, SAML and bucket storage cleanup

Changelog

  • Fixed an issue with CSP that could cause the Humio UI to freeze on Safari browsers
  • Fixed an issue that prevented deletion of unused objects in bucket storage, if the bucket contained 100 millions of objects or more
  • Fixed an issue with SAML IDPs requiring query parameters to be passed via the configuration SAML_IDP_SIGN_ON_URL

1.10.5

Bug fixes - humio-search-all and query timeouts

Release Date: 2020-06-09
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false

Bug fixes - humio-search-all and query timeouts

Changelog

  • Fixed a number of issues with export and alerts in the humio-search-all repository
  • Fixed an issue where long running queries started as part of an export, or by calls to the /query API would time out
  • Fixed an issue where a query could get a “Result is partial” warning when the query took more then 15 minutes to complete while a merge of segments addressed by the query happened in the background

1.10.4

Bug fixes for long-running queries

Release Date: 2020-05-29
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false

Bug fixes for long-running queries

Changelog

  • Fixed a number of bugs that would cause long-running queries using join, selfJoin or selfJoinFilter to timeout or fail

1.10.3

Bug fixes.

Release Date: 2020-05-20
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false

Bug fixes.

Changelog

  • Bugfix: An issue could result in malformed messages being put into the ingest queue. This version is able to read and skip such messages. The issue causing such malformed messages has been fixed.

1.10.2

Optimizations, improved Humio health insights and bug fixes.

Release Date: 2020-05-19
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false

Optimizations, improved Humio health insights and bug fixes.

Changelog

  • Bugfix: A couple of memory leaks have been found and fixed.
  • Bugfix: Autocreate users on login when synchronizing groups with external provider.
  • Bugfix: Humio search all repo interaction with alerts and notifiers.
  • Improvements made to speed of frontpage loading. Noticeable for customers with many repositories and groups.
  • Paging in UI. administration/Users & Permissions.
  • Better sorting when computing query prefixes in order to reuse queries.

1.10.1

Optimizations, improved Humio health insights and bug fixes.

Release Date: 2020-05-04
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false

Optimizations, improved Humio health insights and bug fixes.

Changelog

  • This release fixes a security issue. For more information see: Humio Security Disclosures.
  • New metric: “query-delta-cost”: 30s delta cost on queries per repo, for the entire cluster.
  • New internal jobs logging system stats: Search for #type=humio | NonSensitive | groupby(kind) to see them.
  • Thread pools have been reorganized to require fewer threads and threads have been given new names.
  • Memory requirements set using -XX:MaxDirectMemorySize is much lower now. Suggested value is ((#vCpu+3)/4) GB.
  • Improved protocol within cluster for submitting queries to allow faster start of queries on huge repositories.

1.10.0

UI for Role Based Access Control (RBAC), Health Check API, Kafka version update, Vega charts

Release Date: 2020-04-27
Minimum previous Humio version: 1.8.5
Requires data migrations: true
Has changes to configuration: true

RBAC, Health Check API, Kafka, Vega

This release promotes the 1.9 releases from preview to stable. The main new additions are:

Security fixes

Kafka version update

  • Updated Humio to use Kafka 2.4. Humio can still use versions of Kafka down through 1.1.
  • Be aware that updating Kafka also requires you to update Zookeeper to 3.5.6. There is a migration involved in updating Zookeeper. See Zookeeper’s migration FAQ here. Use the migration approach using an empty snapshot. The other proposed solution can loose data.
  • Updated Kafka and Zookeeper Docker images to use Kafka 2.4. Updating to Kafka 2.4 should be straightforward using Humio’s Kafka/Zookeeper Docker images. Zookeper image will handle migration. Stop all Kafka nodes. Stop all Zookeeper nodes. Start all Zookeeper nodes on the new version. Start all Kafka nodes on the new version. Before updating Kafka/Zookeeper, we recommend backing up the Zookeeper data directory. Then, add the Zookeeper properties described below. If you are deploying Kafka/Zookeeper using other tools, for example Ansible scripts, be aware there is a migration involved in updating Zookeeper.
  • When updating Kafka/Zookeeper we recommend setting these Zookeeper properties
    # Do not start the new admin server. Default port 8080 conflicts with Humio port.
    admin.enableServer=false
    # purge old snapshot files
    autopurge.purgeInterval=1
    # Allow 4 letter commands. Used by Humio to get info about the Zookeeper cluster
    4lw.commands.whitelist=*
    

New features

  • Several improvements to Query Functions
  • NetFlow support extended to also support IPFIX.
  • Added humio Health Check APIs
  • Chart styling support (Pie, Bar)
  • Time Chart series roll-up
  • Replaces chart library with Vega, can be disabled using the ENABLE_VEGA_CHARTS=false flag.
  • Linear interpolation now default. New interpolation type: Basis
  • Control widget stylying directly from dashboards
  • Support for controlling color and title in widgets
  • Add Role Based Access Control (RBAC) to the Humio UI
  • New line interpolation options
  • Dealing with missing data points in timecharts

To see more details go through the individual 1.9.x release notes (links in the changelog).

Note: This release is identical to 1.9.3 apart from the version string.

Changelog

1.8.9

Security fixes

Release Date: 2020-03-25
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false

Security fixes.

Changelog

  • Security: [critical] Fixed a security vulnerability discovered through proactive penetration testing (more information will be forthcoming).

1.8.8

Security fixes

Release Date: 2020-03-23
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false

Security fixes.

Changelog

  • Fix security problem. This is a critical update. On-prem system with access for non-trusted users should upgrade. We follow up with more details when this update has been rolled out.

1.8.7

Bug fixes

Release Date: 2020-03-12
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false

Bug fixes.

Changelog

  • Bug fix: Alerts and exports now work on the special view “humio-search-all”.
  • Bug fix: When a merge of segment files fails, delete the tmp-file that was created.
  • Bug fix: The Kafka and Zookeeper images tagged with “1.8.6” were partially upgraded to Kafka 2.4.0.

1.8.6

Bug fixes

Release Date: 2020-03-09
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false

Note! Do not install the Kafka, Zookeeper or “single” Docker images of this build. Install 1.8.7 or later.

Changelog

  • Note! Do not install the Kafka, Zookeeper or “single” Docker images of this build. Install 1.8.7 or later.
  • Bug fix: Assigning ingest tokens to parsers in sandbox repos.

1.8.5

Bug fixes

Release Date: 2020-02-28
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false

Bug fixes.

Changelog

  • Bug fix: “Export” queries could hit an internal limit and fail for large datasets.
  • Lower ingest queue timeout threshold from 90 to 30 seconds.
  • Bug fix: TCP socket ingest listener would spend a lot of CPU when connected but not receiving any data.
  • Bug fix: Fixed a race in upload of segment files for systems set up using ephemeral disks.

1.8.4

UI Scroll bugfix for Chrome 80 (again)

Release Date: 2020-02-19
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false

This release is purely a fix for the Humio UI. After upgrading to Chrome 80, people have been experiencing issues with scrolling in some of Humio’s widgets. We did not find all the problems in the previous release.

Changelog

  • Bug fix: Fix more scrolling issues in Chrome 80 and above.

1.8.3

UI Scroll bugfix for Chrome 80

Release Date: 2020-02-13
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false

This release is purely a fix for the Humio UI. After upgrading to Chrome 80 people have been experiencing issues with scrolling on the Search page - specifically when the “Field” panel is visible.

Changelog

  • Bug fix: Fix scrolling issue in Chrome 80 on the Search Page.

1.8.2

Bug fixes

Release Date: 2020-02-10
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: true

This is a bug fix release.

Changelog

  • Bug fix: The new feature for ephemeral servers using Zookeeper to UUID did not properly reconnect when the network failed.
  • Bug fix: Bucket storage download could report “download completed” also in case of problems fetching the file.
  • Bug fix: When a node was missing for an extended period of time the remaining nodes would create smaller segment files than they should.

1.8.1

Bug fixes

Release Date: 2020-02-03
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: true

This is a bug fix release.

Changelog

  • New feature for ephemeral servers: Let Zookeeper assign the UUID that in turn assigns the node ID in the cluster. This is turned on by setting the config option ZOOKEEPER_URL_FOR_NODE_UUID to the set of Zookeepers to use for this. The option ZOOKEEPER_PREFIX_FOR_NODE_UUID (default “/humio_autouuid_") sets the prefix to allow rack awareness. Note: Do not turn this on for an existing cluster. Do not turn on if running older 1.7.x or 1.8.x builds.
  • Bug fix: Fix edge case errors in the regex engine. Some case insensitive searches for some Unicode characters were not supported correctly.
  • Bug fix: Avoid calling fallocate on platforms that do not support this (for example, ZFS).

1.8.0

Joins, Bucket Storage Backend, Query Quotas, UI Improvements

Release Date: 2020-01-27
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: true

This release promotes the 1.7 releases from preview to stable. The main new additions are:

To see more details go through the individual 1.7.x release notes (links in the changelog).

Note: This release is identical to 1.7.4 apart from the version string.

Changelog

1.6.11

Bug fixes

Release Date: 2020-01-06
Minimum previous Humio version: 1.5.19
Requires data migrations: false
Has changes to configuration: false

Handle large global snapshot file

Changelog

  • Bug fix: Handle large global snapshot files (larger than 2 G).

1.6.10

Bug fixes

Release Date: 2019-12-12
Minimum previous Humio version: 1.5.19
Requires data migrations: false
Has changes to configuration: yes - see changes

Bug fixes and LDAP improvements.

Changelog

  • Username/email is treated case-insensitive in Humio. This is more expected behavior of usernames as emails addresses are often used. In some rare occasions duplicate accounts might have been created with difference in casing and this change can trigger the otherwise dormant account to be chosen when logging in the next time. If this happens, use the administrations page to delete the unwanted user account and let the user log in again.
  • LDAP: It is now possible to specify an attribute within the LDAP record to use for the username rather than the default (an email address). This is only the case when using ldap-search method by specifying the LDAP_USERNAME_ATTRIBUTE in the environment. Group names when using LDAP have historically been the distinguished name (DN) for that group, it is now possible to specify and attribute in the group record for the name by setting LDAP_GROUPNAME_ATTRIBUTE. These changes necessitated a breaking change in the ldap-search code path in cases where users of Humio authenticate with a username (e.g. user) rather than an email address (e.g. user@example.com). To elicit the same behavior as previous versions of Humio simply specify the LDAP_SEARCH_DOMAIN_NAME which in the past would default to the value of LDAP_DOMAIN_NAME but no longer does.
  • Add LDAP_USERNAME_ATTRIBUTE and LDAP_GROUPNAME_ATTRIBUTE configuration settings to enable more control over names carried from LDAP into Humio.
  • Require setting LDAP_SEARCH_DOMAIN_NAME explicitly when using ldap-search authentication method.
  • Bugfix: Query sessions were not properly cleaned up after becoming unused. This lead to a leak causing high amount of chatter between nodes.

1.6.9

Bug fixes

Release Date: 2019-11-25
Minimum previous Humio version: 1.5.19
Requires data migrations: false
Has changes to configuration: no - but see changes to backup in 1.6.6

Bug fixes and a new background job that reduces number of small files on disk.

Changelog

  • New background job: Find segments that are too small compared to the desired sizes (from current config) and merge them into larger files. For COMPRESSION_TYPE=high this will recompress the inputs while combining them. This job runs by default and may be turned off by MERGE_UNDERSIZED_SEGMENTS_ENABLED=false.
  • Detect when event ingested are more than MAX_HOURS_SEGMENT_OPEN (24h by default) old and add the tag humioBackfill to them in that case to keep “old” events from getting mixed with current “live” events.
  • Improved memory usage from having large global.