Humio Server 1.20.0 Stable (2021-01-28)
|Version||Type||Release Date||End of Support||Upgrades From||Data Migration||Config. Changes|
Important Information about Upgrading
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.
A new function called
test() has been added
for convenience. What used to be done like:
<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
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 Application. Read more about the details internal logging.
To see more details, go through the individual 1.19.x release notes (links in the changelog).
Fixed an issue causing the secondary storage transfer job to plan more segments for transfer than necessary.
Segment download timeout raised from 120s to 1.0s. 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)
Major changes (see version 1.19.0 release notes)