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.
Release Date: 2021-04-19
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
Release Date: 2021-04-12
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
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.
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.
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.
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.
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.
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.
QUERY_QUOTA_EXCEEDED_PENALTYconfig (introduced in 1.19.0).
Release Date: 2021-03-02
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
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.
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.
In this version the UI has been given a complete makeover.
To see more details, go through the individual 1.21.x release notes (links in the changelog).
Release Date: 2021-02-22
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
Release Date: 2021-02-16
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
Release Date: 2021-02-11
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
"").
Release Date: 2021-02-01
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
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.
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.
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.
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.
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)
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.
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
To see more details, go through the individual 1.19.x release notes (links in the changelog).
Release Date: 2021-01-25
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
Release Date: 2021-01-20
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
Release Date: 2021-01-08
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
Release Date: 2020-12-17
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: false
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.
@timestamp=x where x was a timestamp with the current search interval could failtop([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.to parameter to unit:convert would cause internal server errors instead of validation errors.
Release Date: 2020-11-26
Minimum previous Humio version: 1.16.0
Requires data migrations: false
Has changes to configuration: true
This release promotes the latest 1.17 release from preview to stable.
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.
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.
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.
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.
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).
To see more details, go through the individual 1.17.x release notes (links in the changelog).
IDLE_POLL_TIME_BEFORE_DASHBOARD_QUERY_IS_CANCELLED_MINUTES. Queries on dashboards now have the same life cycle as other queries.ZONE is set to the empty string. It is now considered the same as omitting ZONE.
Release Date: 2020-11-26
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
join expressions.sort/head/tail to work incorrectly after other aggregating functions.join etc. not to see events with an @ingesttimestamp occurring later than the search time interval.{events_html} message template was formatted as raw HTML in alert emails.datasource-count from counting datasources correctly.
Release Date: 2020-11-10
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-10-30
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-10-21
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
GroupBy.jvm-hiccup for measuring stalls/pauses in the JVM.
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.
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.
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.
It is now possible to configure an alert notifier that will log all events to a Humio repository. See docs.
It is now possible to use the Slack notifier to notify multiple Slack channels at once. See docs.
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.
It is now possible to configure an alert notifier to not use the HTTP proxy configured in Humio. See docs.
Redesigned signup/login pages. For cloud, we have have split the behavior so users have to explicitly either login or signup.
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.
It is now possible to configure Humio to not use the globally configured HTTP proxy for communcation with S3. See docs.
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.
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.
To see more details, go through the individual 1.15.x release notes (links in the changelog).
KAFKA_MANAGED_BY_HUMIO was true.
Release Date: 2020-10-30
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-10-21
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
KAFKA_MANAGED_BY_HUMIO was true.jvm-hiccup for measuring stalls/pauses in the JVM.
Release Date: 2020-10-09
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-09-24
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
join().
Release Date: 2020-09-17
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-09-08
Minimum previous Humio version: 1.12.0
Requires data migrations: false
Has changes to configuration: false
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.
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 Encrypt communication using TLS to/from Zookeeper, Kafka, and other Humio nodes.
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:
If the database cannot be automatically updated and no database is provided manually, the ipLocation() query function will no longer work.
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).
Release Date: 2020-09-17
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-09-03
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-08-12
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-08-05
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-08-04
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-07-03
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-06-24
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
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 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 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.
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
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
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).
Release Date: 2020-08-05
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-08-04
Minimum previous Humio version: 1.10.0
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-07-03
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-06-24
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-06-09
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-05-29
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-05-20
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-05-19
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-05-04
Minimum previous Humio version: 1.8.5
Requires data migrations: false
Has changes to configuration: false
#type=humio | NonSensitive | groupby(kind) to see them.-XX:MaxDirectMemorySize is much lower now. Suggested value is ((#vCpu+3)/4) GB.
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:
# 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=*
ENABLE_VEGA_CHARTS=false flag.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.
Release Date: 2020-03-25
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-03-23
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-03-12
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-03-09
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-02-28
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-02-19
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-02-13
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: false
Release Date: 2020-02-10
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: true
Release Date: 2020-02-03
Minimum previous Humio version: 1.6.10
Requires data migrations: false
Has changes to configuration: true
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.
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:
join search functionTo 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.
Release Date: 2020-01-06
Minimum previous Humio version: 1.5.19
Requires data migrations: false
Has changes to configuration: false
Release Date: 2019-12-12
Minimum previous Humio version: 1.5.19
Requires data migrations: false
Has changes to configuration: yes - see changes
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.LDAP_USERNAME_ATTRIBUTE and LDAP_GROUPNAME_ATTRIBUTE configuration settings to enable more control over names carried from LDAP into Humio.LDAP_SEARCH_DOMAIN_NAME explicitly when using ldap-search authentication method.
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
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.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.