All Release Notes

Below is a compilation of all notes for Humio software releases.

Humio 1.31.0

Scheduled search out of beta

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.31.0

Preview

2021-09-27

Next Stable Version

1.16.0

No

Yes

JAR Checksum

Value

MD5

4b4b4411d930d00275bc3a412c0c5c50

SHA1

ca22652ca303a162f81711f43977e14e528f6e85

SHA256

908a907b5c1ffbdce667b932daea0aab46a8ece4e164072f5bae0eb77d3bdd6f

SHA512

bbc65ea8641ac3d9910da4a9dcda0c1817d2a8acc2e81491a389d2671af7e57c12f019ad71af7309d4ad68b67997a6cbd3b0fba3a2048f07b7c7567abd05b8ae

Humio tarball

We now distribute Humio as a tarball in addition to the fat jar format we’ve previously used. We will continue to distribute the fat jar for the time being. The tarball includes a launcher script, which will set a number of JVM arguments for users automatically. We believe this will help users configure Humio for good performance out of the box.

Search performance via hashfilter-first on segments in buckets

Some searches, including regex and literal string matches, now allow searching without fetching the actual segment files from the bucket, in case the segment is only present in the bucket and not on any local disk. Humio now fetches the hash filter file and uses that to decide if the segment file may have a match before downloading the segment file in this case.

Packages are more powerful

Humio packages can now carry scheduled searches, all types of actions, and files with lookup data (either CSV or JSON formatted). Additionally, we have improved the UI for managing packages, to make it easier to find the package you are looking for. This also marks the point where packages are brought out of beta.

Change Log

  • Amended an internal limit on how many segments can be fetched from bucket storage concurrently. The old limit was based on the number of running queries. The new limit is 32.

  • Cloning an asset now redirects you to the edit page for the asset for all assets.

  • Creating a new dashboard now opens it after creation.

  • Fixed a bug causing the disk space job to use an expensive code path even when a cheaper one was available.

  • Fixed a bug on queries that triggered an error while executing due to the input (such as a regex that exceeds limits on execution time) could result in the client getting 404 as status on poll, where it should get 400.

  • Fixed a bug where a 404 Not Found status on an internal endpoint would be incorrectly reported as an 401 Unauthorized.

  • Fixed a bug where a hidden field named “#humioAutoShard” would sometimes show up in the field list.

  • Fixed a bug which potentially have caused alerts to not re-fire after the throttle period for field-based throttling had passed.

  • Fixed an issue that caused some errors to be hidden behind a message about “internal error”.

  • Fixed an issue that caused some metrics of type gauge to be reported with a wrong value.

  • Fixed an issue that could cause UploadedFileSyncJob to crash if an uploaded file went missing.

  • Fixed an issue that could cause cluster nodes to crash when growing the number of digest partitions.

  • Fixed an issue where Humio attempted to fetch global from other nodes before TLS was initialized.

  • Fixed an issue where Humio would create a broken hash file for the merge result when merging minisegments that did not originally have hash files.

  • Fixed an issue where Humio would create auxiliary files (hash files) for segments unnecessarily when moving segments between nodes.

  • Fixed an issue where Shift+Enter would select the current completion rather than adding a newline.

  • Fixed an issue where certain problems highlighted the first word in a query, not the location of the problem.

  • Fixed an issue where it was possible to submit queries to the Delete Events API that were not valid for that API. Only pure filtering queries are allowed.

  • Fixed an issue where metrics of type gauge with a double value were not reported to the humio-metrics repository, but only to the humio repository.

  • Fixed an issue where new groups added to a repository got a query prefix that disallowed search. The default is now to allow search with the queryprefix *.

  • Fixed an issue where the DiskSpaceJob could continue tracking segments if they were deleted from global, but the files were still present locally.

  • Fixed an issue where the DiskSpaceJob could mark segments accessed slightly out of order during boot.

  • Fixed an issue where the {time_zone} message template for actions would show a full description of the scheduled search instead of only the time zone.

  • Fixed an issue where the global consistency check job would fail to perform the consistency check, instead logging lines like “Global dump requested but global had expired”. This line can still occur, but only when the consistency check takes too long.

  • Fixed an issue where the job responsible for deleting segment files off nodes was not deleting as many segments as it should.

  • Fixed an issue where the job responsible for deleting segment files off nodes was not running as often as expected.

  • Fixed an issue where the query scheduler would spend too much time “shelving” queries, and not enough on getting them executed, leading to little progress on queries.

  • Fixed an issue where top() with max= can yield the same key multiple times (ei. …| top([queryId, query], max=totalSize)).

  • Fixed an issue where, looking at GraphiQL, the dropdown from the navigation menu was partially hidden.

  • Fixed an issue with the split() function which caused incorrect (usually, too few) query results in some cases where the output fields were refered to later in the query.

  • Fixed thread safety for a variable involved in fetching from bucket storage for queries.

  • Global snapshots are now uploaded to bucket storage more often when there are a lot of updates to it, leading to shorter replay times on startup.

  • Introduced a check for compatibility for packages and humio versions.

  • Removed an old Cloud Signups page. The page is not necessary since organizations were implemented for the Cloud environments.

  • Reworded a confusing error message when using the top() function with a limit parameter exceeding the limits configured with TOP_K_MAX_MAP_SIZE_HISTORICAL or TOP_K_MAX_MAP_SIZE_LIVE.

  • Security when viewing installed packages and packages on the marketplace are now less strict. Permissions are still required for installing and uninstalling packages.

  • Split package export page into dialog with multiple steps.

  • The DiskSpaceJob no longer initializes based off of the segment last-modified timestamp, this only happens if no access order snapshot is stored locally. If a snapshot is present, we trust that.

  • The DiskSpaceJob now removes newly written backfilled segments off the local disk before it chooses to remove non-backfilled segments.

  • The simple and advanced permission model has been merged, thus allowing users who were using the simple permission model to create their own permission roles and groups, create groups with default roles, and all other features that were previously only available in advanced permissions mode.

  • Truncate long user names on the Users page.

  • Updated Elastic ingest endpoint to accept ‘create’ operations in addition to ‘index’ operations. Both operation types result in the same ingest behavior. This update was added as Fluent-Bit v1.8.3 began using the ‘create’ operation rather than ‘index’ for ingest.

  • Updated Slack action for messaging multiple channels, so it propogates errors when triggered. Previously errors were ignored.

  • Updated dependencies with security fixes.

  • Updated the examples on how to use the Query Function match() query function in the inline documentation.

  • Updated the new asset dialog button text so that it will say ‘Continue’ when an asset will not be created directly.

  • When a search is able to filter out segments based on the hash filter files, and a segment file is not present locally on any node, fetch only the hash filter at first, evaluate that, and only if required, fetch the segment file. This speeds up searches that target segments only present in bucket storage and that have search filters that generate hash filter checks, such as regex and literal text comparisons.

  • When accessing Humio through a URL with either a repository or view name in it and using an ingest token, it is now checked that the view on the token matches the repository or view in the URL, and a 403 Forbidden status is returned, if not.

Improvements

  • Added loading and error states to the page where user selects to create a new repository or view.

  • Added Dark Mode for Query Monitor page.

  • Added a Data subprocessors page under account.

  • Added explicit distribution information for elastic bulk API for elasticsearch API compatibility.

  • Added focus states to text field, selection and text area components.

  • Added maximum width to tabs on the Group page, so they do not keep expanding forever.

  • Added support for importing packages with CSV and JSON files. Exporting packages with files is not fully supported yet, but will be in a future release.

  • Added support for including dashboard and alert labels when exporting a package.

  • Allow launching using JDK-16.

  • Humio docker images is now based on the Alpine linux.

  • Improved audit log for organization creation.

  • Improved handling of local disk space relative to LOCAL_STORAGE_MIN_AGE_DAYS: When the local disk would overflow by respecting that config, Humio can now delete the oldest local segments that are present in bucket storage, even when they are within that time range.

  • Improved search for users page.

  • Improved performance in IP database lookups for the functions ipLocation(), asn() and worldMap().

  • Package installation error messages are now much more readable.

  • You can now export and import packages containing any of the action types: Webhook, Email, Humio Repo, Pager Duty, Slack, Slack multi channel, Ops Genie and Victor Ops.

GraphQL API Changes

  • Added a GraphQL mutation “cancelDeleteEvents” that allows cancelling a previously submitted deletion. Cancellation is best-effort, and events that have already been deleted will not be restored.

  • Added information about the use of preview fields in the result from calling the GraphQL API. The information will be in the field extensions.preview and will be a list of objects with a name and reason field.

  • Extended ‘Relative’ field type for schema files to include support for the value ‘now’.

  • Deprecates the copyFile GraphQL mutation, as it is no longer used. If you use this mutation, please let us know.

  • Deprecates the installPackageFromRegistry and updatePackageFromRegistry GraphQL mutations in favor of installPackageFromRegistryV2 and updatePackageFromRegistryV2.

  • Deprecates the package field on the SearchDomain GraphQL type, in favor of packageV2. The new field has a simpler and more correct return type.

  • Deprecates the two GraphQL fields id and contentHash on the File type. The two fields are considered unused, so no alternatives are provided. If you rely on them, please let us know.

  • The GraphQL DateTime type now supports non-UTC time. Timestamps like 2021-07-18T14:13:09.517+02:00 are now legal, and will be converted to UTC time internally.

  • The fileName, displayName, and location GraphQL fields on the UploadedFileSnapshot type are deprecated in favor of the new nameAndPath field.

  • The name, displayName, and location GraphQL fields on the File type are deprecated in favor of the new nameAndPath field.

  • When using the GraphQL field allowedViewActions, the two previously deprecated actions ChangeAlertsAndNotifiers and ReadEvents are no longer returned. Look for their replacements ChangeTriggersAndActions and ReadContents instead.

Configuration Changes

  • Added compatibility mode for using IBM Cloud Object Storage as bucket storage via S3_STORAGE_IBM_COMPAT

  • The Scheduled Searches feature is no longer in beta and can be used by all users without enabling it first

  • On a node configured as USING_EPHEMERAL_DISKS=true allow the local disk management deleting files even if a query may need them later, as the system is able to re-fetch the files from bucket storage when required. This improves the situation when there are active queries that in total have requested access to more segments than the local disk can hold.

UI Changes

  • Breadcrumbs are aligned across all pages and show the package name with a link when viewing or editing an asset from a package.

  • Cluster management pages style updates.

  • Fixed some styling issue on Query Quotas page.

  • Identity provider pages style update.

  • Removed the pop-up link to edit an alert or scheduled search when on the form page. This link is only relevant when creating an entity from the search page via a dialog.

  • The left navigation menu hides, and can be opened again, for mobile devices, on organization settings pages and repository settings pages.

  • The signup path was removed, together with the corresponding pages.

  • Updated design for Package Marketplace and Installed Packages to make them easier to use and more consistent.

  • Updated the style of the email action template and made the wording used dependent on whether an alert or scheduled search was triggered.

Scheduled search

  • Fixed an issue with using the browser back button while “advanced editing” the query text of a scheduled search or an alert would hide the blue bar that allows saving the query.

  • Improved error handling when running scheduled searches, so that a failed schedules search will be retried as long as it is within the [backfill limit](https://library.humio.com/preview/docs/automated/scheduled-search/#backfill-limit).

  • Warnings when running scheduled searches now show up as errors in the scheduled search overview page if [SCHEDULED_SEARCH_DESPITE_WARNINGS](https://library.humio.com/preview/reference/environment-variables/#var-scheduled-search-despite-warnings) is set to ‘false’ (the default).

  • Scheduled search “schedule” field is now validated, showing accurate help for each part of the crontab expression.

  • Scheduled search “schedule” is explained using human readable text such as “At 9.30 on Tuesdays”.

  • The test action functionality no longer uses alert terminology, as actions can be invoked from both alerts and scheduled searches. Also, it is now possible to also test the scheduled search specific message templates using it.

  • When selecting actions for alerts or scheduled searches, the actions are now grouped by the package they were imported from.

Humio 1.30.0

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.30.0

Stable

2021-09-17

2022-09-17

1.16.0

No

Yes

JAR Checksum

Value

MD5

c8989abb219663a61ae54be021fcd367

SHA1

44e1d48d09ca3ae8fd59a185e77b3c9a55a6de8f

SHA256

25a880f34a0fef72ab3cb4bf93f92eae2fdac0022d116485bed1013b3f6683b4

SHA512

53b8055035bfcdd7176fa4369e607874ca9d5ee84de4a3beb964e3f0caba9578b3c46c04c10cb68657be34d8a165fa1089f1679716ecd4896ff57822d0b1e851

Indicator of Compromise

As a new feature Humio now includes an IOC (indicator of compromise) database from CrowdStrike to enable lookup of IP addresses, URLs and domains for malicious activity. This database is updated hourly. This is described in more detail at ioc:lookup()

Change Log

  • Major changes: 1.29.0

  • Minor fixes: 1.29.2

  • Minor fixes: 1.29.3

  • Minor fixes: 1.29.4

  • Fixed an issue where the UI page for new parser could have overflow in some browsers.

  • Fixed an issue where offsets from one Kafka partition could be used when deciding where to start consuming for another partition, in the case where there are too many datasources in the repo. This led to a crash loop when the affected node was restarted.

  • Fixed an issue where the query scheduler would spend too much time “shelving” queries, and not enough on getting them executed, leading to little progress on queries.

Humio 1.29.4

Minor bug fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.29.4

Preview

2021-09-09

2021-09-17

1.16.0

No

No

JAR Checksum

Value

MD5

8145f9ddc7804a44efe1e46cd71f5c17

SHA1

8db4079f580357162891d0153a70668b4f29d642

SHA256

32adde840164668a96be651ede6052dbef3cf046ec9f83f39f62925d26e14104

SHA512

cadcd2eb07e949f052bd51ecc272d79f7decfec0f3b7613dfdf712aa1ff287471060d25443c5be1b06744aefa43194fb2e78e223c362005cea62a5917a93b62e

Minor bug fixes

  • Added a GraphQL mutation cancelDeleteEvents that allows cancelling a previously submitted deletion. Cancellation is best-effort, and events that have already been deleted will not be restored.

  • Fixed an issue where it was possible to submit queries to the Delete Events API that were not valid for that API. Only purely filtering queries are allowed.

Humio 1.29.3

Minor bug fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.29.3

Preview

2021-09-07

2021-09-17

1.16.0

No

No

JAR Checksum

Value

MD5

96b4a0ff0c02a2dce2bb5ee467bdb9dd

SHA1

b2a1ef55259f6c49ee7bf7de6efecc0f743d1bfa

SHA256

95d9b52d6213d0af43dfc43cb66c878f1f584f446e4ba890137c5fd9923db1a4

SHA512

392489e94b1e6f6799a6340df78e7bdb7d9547b97ba1844cfbf3c525e1e418fd2221543378f2b759acf46d5c02d99627f9b98650447d7c1c32ba599157718bf8

Minor bug fixes

  • Fixed an issue where the error TooManyTagValueCombination would prevent Humio from starting

  • Remove limit on search interval on cloud sandboxes

Humio 1.29.2

Minor bug fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.29.2

Preview

2021-09-02

2021-09-17

1.16.0

No

No

JAR Checksum

Value

MD5

0b32f9520b7a5ec3f1af3321ce7f1dfe

SHA1

4ae2567f9b3348d115819eefd5b9c078d6c2c6ad

SHA256

0383277fd91b8933dfcdb94783e03d151975b01ee62dcc74515cbfb2d3299cdc

SHA512

bbfb1f343f0567394128976ecddc6ad3b74f2996b0dc51e2fe0f9c5e0b60cbd7a935fc709b2ffc3b6a811a0e6a1c2fcc09e4e1552e5c7f87dd3670f07cf33b31

Minor bug fixes

  • Fixed an issue where, looking at GraphQL, the dropdown from the navigation menu was partially hidden.

  • Fixed an issue that could cause UploadedFileSyncJob to crash, if an uploaded file went missing

  • Fixed an issue where if a package failed to be installed, and it contained an action, the failed installation might not be cleaned up properly.

  • Fixed an issue where new groups added to a repository got a query prefix that disallowed search. The default is now to allow search with the query prefix * (wildcard).

Humio 1.29.1

Indicator of Compromise

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.29.1

Preview

2021-07-12

2021-09-17

1.16.0

No

Yes

JAR Checksum

Value

MD5

6cea304226bb9eb096785375bb8f834f

SHA1

77d7b92df1884b8ec457246d602cc276e46ee032

SHA256

e48d6a5c80e6979621b817c1ac53f778eae170185180ab9e70c295692dd1a7bc

SHA512

c9e8019067a9ae1bd0b62215ee458ecabcee2b3a971688c6f66c58dc1009d498cdd560d4733f64f31e6d4204bebb6c8bc0934354ab04aaa008b3e21ef8bc7dee

Indicator of Compromise

Fixes an issue in the 1.29.0 release that made it appear as though ingest tokens had no associated parser.

Humio 1.29.0

Indicator of Compromise

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.29.0

Preview

2021-07-09

2021-09-17

1.16.0

No

Yes

Indicator of Compromise

Warning

This release has been revoked as it contained a known bug fixed in 1.29.1.

As a new feature Humio now includes an IOC (indicator of compromise) database from CrowdStrike to enable lookup of IP addresses, URLs and domains for malicious activity. This database is updated hourly. This is described in more detail at ioc:lookup()

Change Log

  • Avoiding a costly corner case in some uses of glob-patterns.

  • Address edge cases where QueryScheduler could throw exceptions with messages similar to “Requirement failed on activeMapperCount=-36”

  • When testing a Parser and more events are returned in a test an info message is now displayed conveying that only the first event is shown.

  • Fixed bugs in the test parser UI, so that it should now always produce a result and be able to handle parsers that either drop events or produce multiple events per input event.

  • Fixed a bug where word wrapping in the event list was not always working for log messages with syntax highlighting (e.g. JSON or XML messages)

  • Fixed a bug in the Search View. After editing and saving a saved query in the Search View, the notification message would disappear in an instant, making it impossible to read and to click the link therein.

  • Fixed a bug causing match() to let an empty key field match a table with no rows.

  • Fixed a bug in the blocklist which caused “exact pattern” query patterns to be interpreted as glob patterns.

  • Fixed race condition that could cause event forwarding rules to not update correctly in rare cases

  • Fixed race condition that could cause parsers to not update correctly in rare cases

  • Fixed an issue with “show in context” feature of the event list did not quote the field names in the produced query string.

  • Fixed an issue where exporting a saved query did not include the options for the visualization, e.g. column layout on the event list.

  • Fixed an issue where the axis titles on the timechart were not showing up in dark mode

  • Fixed an issue related to validation of integer arguments. Large integer arguments would be silently truncated and

    lower limits weren’t checked, which led to unspecified behavior. Range errors are now reported in the following functions: - bucket() - concatArray() - formatDuration() - geohash() - hashmatch() - hashrewrite() - head() - json:prettyPrint() - parseInt() - regex() - sort() - splitString() - subnet() - tail() - transpose() - window()

Improvements

  • Scheduled searches are now allowed to run once every minute instead of only once every hour.

  • Added dark mode support to Identity provider pages.

  • Enabled dark mode for cluster administration pages.

  • The “Save Search as Dashboard” Widget dialog now gives user feedback about missing input in a manner consistent with other forms.

  • Integrates the editing of alert searches and scheduled searches better with the search page

  • Return the responder’s vhost in the metadata json.

  • In thread dumps include the job and query names in separate fields rather than as part of the thread name.

  • Created a new Dropdown component, and replaced some uses of the old component with the new.

  • Organization pages refactoring.

  • Previously, the server could report that a user was allowed to update parsers for a view, even though parsers cannot be used on views, only repositories. Now the server will always say the user cannot change parsers on views.

  • When editing a query, Enter no longer accepts a suggestion. Use Tab instead. The Enter key conflicted with the “Run” button for running the query.

  • Speed up the SecondaryStorageTransferJob. The job will now delete primary copies much earlier after moving them to the secondary volume.

  • Make GlobalConsistencyCheckerJob shut down more cleanly, it could previously log some ugly exceptions during shutdown.

  • Improved global snapshot selection in cases where a Kafka reset has been performed

  • Packages now support Webhook actions and references between these and alerts in the Alert schema.

  • Internal change to parsers adding an id, where previously they only had a name as key.

GraphQL API Changes

  • Removed the argument includeUsageView from the graphql mutation createOrganizationsViews which breaks backwards compatibility for this internal utility method.

  • Removed the Usage feature flag which is now always enabled. This breaks backwards compatibility for internal graphql feature flag mutations and queries.

  • Deprecated argument repositoryName was removed from Mutation.updateParser field

  • Deprecated argument name was removed from Mutation.updateParser field

  • Field addIngestToken was deprecated in Mutation type, use addIngestTokenV2 instead

  • Field assignIngestToken was deprecated in Mutation type, use assignParserToIngestToken instead

  • Field copyParser was deprecated in Mutation type, use cloneParser instead

  • Field createIngestListener was deprecated in Mutation type, use createIngestListenerV2 instead

  • Field updateIngestListener was deprecated in Mutation type, use updateIngestListenerV2 instead

Configuration Changes

  • Allow the internal profiler to be configured via an environment variable. See Environment Variables

  • Add a soft limit on the primary disk based on PRIMARY_STORAGE_PERCENTAGE and PRIMARY_STORAGE_MAX_FILL_PERCENTAGE (roughly the average of the two values). When the soft limit is hit and secondary storage is configured, the segment mover will prefer moving segments to secondary storage right away, instead of fetching them to primary and waiting for the secondary storage transfer job to move them.

  • Humio nodes will now pick a UUID for themselves using the ZOOKEEPER_PREFIX_FOR_NODE_UUID prefix, even if Zookeeper is not used. This should make it easier to enable Zookeeper id management in existing clusters going forward.

Humio 1.28.1

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.28.1

Stable

2021-08-24

2022-06-15

1.16.0

No

No

JAR Checksum

Value

MD5

1a2b8d3acc15ac6789534f7624265ecb

SHA1

3cf96a324147967c1bc7753a7f9d94cbed8cd843

SHA256

8a355f8bbab9a74422ee3456f9bfe93302734a69197b7e12c254f7c0fd9905de

SHA512

e572352be7e71403f52fe0767567232a198861a60f100b7e9e32475e8e2720285902daf6493b62b79052ca71aa6550abe173d5ae5246e14e5ac30bda0883667c

Change Log

  • The signup path was removed, together with the corresponding pages. Before, anyone could sign up for the Humio SaaS solution. However, with stricter policies, this became obsolete and had to be removed. The new process redirecta a potential customer to Humio’s official website, where they have to fill in a form in order to be vetted. Once the vetting process is complete, Humio support creates an organization for the customer.

  • Fixed an issue that could cause cluster nodes to crash when growing the number of digest partitions.

  • Fixed an issue that could cause UploadedFileSyncJob to crash if an uploaded file went missing

Humio 1.28.0

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.28.0

Stable

2021-06-15

2022-06-15

1.16.0

No

Yes

JAR Checksum

Value

MD5

1a2b8d3acc15ac6789534f7624265ecb

SHA1

3cf96a324147967c1bc7753a7f9d94cbed8cd843

SHA256

8a355f8bbab9a74422ee3456f9bfe93302734a69197b7e12c254f7c0fd9905de

SHA512

e572352be7e71403f52fe0767567232a198861a60f100b7e9e32475e8e2720285902daf6493b62b79052ca71aa6550abe173d5ae5246e14e5ac30bda0883667c

Change Log

  • Major changes: 1.27.0

  • Major changes: 1.27.1

  • Humio trial installations now require a trial license. To request a trial license go to Getting Started.

  • All users (including existing users) need to accept the privacy notice and terms and conditions before using Humio.

  • Backfilled data gets lower priority on local disk when in over-commit mode using bucket storage.

  • When searching through files in a dashboard parameter, users with CSV files greater than 50.000 records could see incomplete results.

  • Humio will now try to upload more segments concurrently during a shutdown than during normal operation.

  • While waiting for the upload of files to bucket to complete during shutdown, the threaddumping will continue running, and the node will report as alive as seen from the other nodes.

  • Fixed a bug that caused previous 1.27.x but not earlier versions to add “host xyz is slow” warnings to query results also when that was not the case.

Humio 1.27.1

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.27.1

Preview

2021-06-15

2021-06-15

1.16.0

No

Yes

JAR Checksum

Value

MD5

d45c8b1dd900bfaaae7ab6d7173f122a

SHA1

9602b62cab67ca3f1d35fd888303bc642c024518

SHA256

ec2db12be413b83e52fb2f1cefa04bc9634e7c17657349c4e6b9c71c26a804f9

SHA512

6179ff0307e3cd804cb4dfcf56a98d30b67cebf51eb2673accde437a308a2d16fd433db983e2948a06768dfac8fa71aa302a357524ed78b675ccbb8491844f6e

Change Log

  • Updated dependencies with security fixes.

  • Fixed issue where certain queries would cause NullPointerException in OneForOneStrategy.

  • Fixed an issue where Humio could prematurely clean up local copies of segments involved in queries, causing queries to fail with a “Did not query segment” warning.

Humio 1.27.0

Improvements & Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.27.0

Preview

2021-06-14

2021-06-15

1.16.0

No

Yes

JAR Checksum

Value

MD5

cce0478c744d183db8491e338949bdfe

SHA1

6dd0bf5c8e0d4ca1f74116e31f28f8cfa7b58323

SHA256

a3425e6141358cbc1115ab3c2691768c64d62f84cea3e018eb7b6debcb05f803

SHA512

ca63e89946e4a12422124adb052b59f8da30ca026b5c34b0bfe1ddcc35cf7546fedd4127d46def6c36b3e0f7278675cf4fe47362fe5070a6d7b29ffbcbd0bc49

Change Log

  • Humio trial installations now require a trial license. To request a trial license go to getting-started

  • All users (including existing users) need to accept the privacy notice and terms and conditions <https://www.crowdstrike.com/terms-conditions/humio-self-hosted> before using Humio.

Improvements

  • In the time selector, you can now write “24” in the time-of-day field to denote the end of the day.

  • Debug logs which relate to the invocation of an action now contain an actionInvocationId. This trace id is the same for all logs generated by the same action invocation.

  • The event distribution chart would sometimes show a bucket span reported in milliseconds instead of a more appropriate unit, when those milliseconds did not add up cleanly (e.g. “1h”). Now the bucket span can be reported with multiple units (e.g. “1h 30m”)

  • The list of recent queries on the search page now has headers with the date the query was run.

  • The UI now consistently marks required field with a red asterisk across a number of dialogs.

  • The New Action dialog validates user input in a more indulgent fashion and provides all validation errors consistently.

  • Added button to delete the organization from the Organization Overview page

  • Automatically reduce the precision of world maps when they exceed a certain size limit

  • Inviting users on cloud now requires the invited user to accept the invitation before assigning permissions to him. Moreover, it is possible to invite users who are in another organization on cloud.

  • Reduced memory usage for groupBy() function, etc.; worst-case in particular but also average-case to some degree.

  • The Humio frontend no longer sends the Humio-Query-Session header to the backend, since it is no longer used.

  • Changed implementation of cluster host alive stats to attempt to reduce thread contention when threads are checking for host liveness.

  • Changed implementation of cluster host alive stats to trigger updates in the in-memory state based on changes in global, rather than running periodic updates.

  • Add a bit more debug logging to DataSnapshotLoader, for visibility around choice of global snapshot during boot

  • Slightly improve performance of id lookups in global

  • Reimplement several part of Humio to use a safer mechanism for listening to changes from global. This should eliminate a class of race condition that could cause nodes to ignore updates received during the boot process.

  • Improve thread safety of updates to global Hosts entities during bootup

  • Add a label to the empty option for default queries on the repository settings page.

  • Users with read repository permissions can now access and see files.

  • Working on merging of advanced and simple permission models, so that the roles can be added directly to users.

  • Added ability to set organization usage limits manually for cases where automatic synchronization is not possible.

  • The Alert and Scheduled Search dialogs have gotten a makeover.

  • Started internal work on memory quotas on queries’ aggregation states. This should not have any user-visible impact yet.

  • When assigning a role, all the user which need a new role are choosen, and then the same role is assigned to them all.

  • Improved styling of header on organization overview page

  • Added frontend validation on welcome page and invitation page fields

  • Removed requirement that SAML Id needs to be an URL (Now, only requirement is that the field is not empty)

  • Included both ws and wss in csp header

  • Added a quickfix feature for reserved keywords

  • Improved error messages when exporting invalid dashboards as templates

  • Updated the interactive tutorial with better descriptions

  • When looking at the details of an event, long field values will now extend beyond the viewport by default. Word wrapping can be enabled to stop it from extending outside the viewport.

  • With worldmap() function, you can now see the magnitude value by hovering marks on the map.

Configuration Changes

  • Limit how many times we’ll repeat a repeating regexp. The default max number of repetitions is 100 but the value is configurable between 50 and 500 by setting the MAX_REGEX_REPETITIONS env variable.

  • Removed the log4j2-stdout-json.xml configuration file. The replacement log4j2-json-stdout.xml has been available for a while, and we want everyone to move to the new configuration, as the old configuration produces logs incompatible with the Humio Insights package.

GraphQL

  • Deprecated GraphQL mutation setRecentQueries, use addRecentQuery in future. The mutation will be removed after 2021-10-01. While setRecentQueries will remain in the API to not break existing clients, it will not modify the set of recent queries.

  • Deprecated GraphQL field SearchDomain.recentQueries in favor of SearchDomain.recentQueriesV2.

Fixes

  • Fixed various bugs for the worldmap widget. The bug fixes may cause your world map marks to look different that previously, but should now work as intended and correcting it should be as simple as tweeking the style parameters.

  • Fixed an issue in timeChart() where the horizontal line did not showing up.

  • Fixed an issue in the Query State Cache that could fail a query on time intervals with a fixed timestamp as start and now as end.

  • Fixed an issue where it was possible to create an alert with an empty time interval or a blank name or throttle field.

  • Fixed a rare issue that could fail to trigger a JVM shutdown if the Kafka digest leader loop thread became nonfunctional.

  • Fixed an issue which caused queries to crash when “beta:repeating()” was used with a time interval ending before “now”.

  • Fixed a problem when some user-defined styles weren’t being applied to a chart after a page refresh or when exported to a dashboard widget

  • Fixed a problem where the global consistency check would report spurious inconsistencies because of trivial differences in the underlying JSON data

  • Fixed an issue where UI stalled on the “Data Sources” page

  • Fixed an issue for Firefox 78.10.1 ESR where the event list and event distribution chart would not be scrollable and resize incorrectly.

  • Fixed an issue where worldmap widgets would revert to event list widgets when changing styling options.

  • Fixed an OIDC group synchronization issue where users where denied access even though their group membership gave them access.

  • Fixed an issue with AuthenticationMethod.SetByProxy where the search page would constantly reload.

  • Fixed an issue where optimizeAndSaveQueryCoordinationPartitions could attempt to save a partitioning table to global with gaps in the partition list. This caused queries to fail, and repeated logging of a validation error.

Humio 1.26.3

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.26.3

Stable

2021-06-17

2022-05-20

1.16.0

No

No

JAR Checksum

Value

MD5

8c880514f42787b5e5f85607bca347de

SHA1

e97e3ea8ebc5de0076186e6daa7aa16d4ca48c8c

SHA256

d906d0938e8c2283ab91dc999cac4f6a966591e3ee0089e309378123d13cd637

SHA512

826aea0625a8daac1801f11f12429a6bcb3b8ee58f4b536172d4602fc5f09252fe0be0afd72a5300520980c962a9caa99aeb4ee6c9ada79544963b4c9687b972

Change Log

  • Updated dependencies with security fixes.

  • Fixed an issue for Firefox 78.10.1 ESR where the event list and event distribution chart would not be scrollable and resize incorrectly.

  • Fixed an issue where worldmap widgets would revert to event list widgets when changing styling options.

  • Fixed an issue where Humio could prematurely clean up local copies of segments involved in queries, causing queries to fail with a “Did not query segment” warning.

Humio 1.26.2

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.26.2

Stable

2021-06-07

2022-05-20

1.16.0

No

No

JAR Checksum

Value

MD5

1ebc3d89c531e0ea11be7378e2f1d27c

SHA1

4ac77b9dd3532d6e1f3bce39a72a2f337c300ccc

SHA256

6d06e3734f6a5f30715754d210092b31f4225a42d97495d8e0c8a3d6eea53bfa

SHA512

d5c6e9b1b08ed10b5549359306e35734a28557088d3efa98d30ccc0080700ba053a8f83d694790686a6333c54734392e8199127cbaf1719a841979e5e9188e27

Change Log

  • Fixes issue where the world map widget would misbehave in different ways.

  • Fixes an issue in Timechart with horizontal line not showing up.

  • Fixes an OIDC group synchronization issue where users where denied access even though their group membership gave them access.

  • Humio trial installations requires a trial license from this version, to request a trial license go to getting-started <https://www.humio.com/getting-started/>

  • All users (including existing users) need to accept the privacy notice and terms and conditions before using Humio.

  • Fix a number of cases where Humio could attempt to write a message to global larger than permitted.

  • Update the minimum Humio version for Hosts in global when downgrading a node

Humio 1.26.1

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.26.1

Stable

2021-05-31

2022-05-20

1.16.0

No

No

JAR Checksum

Value

MD5

8322d138b790cb9839e44c96e0cb4ba8

SHA1

d4f47c97d3faa5ae5d014b5c47ec0221d24b4496

SHA256

bb3fde18139e575a053709c042322604e8e01188f096a764bca9f4338286118e

SHA512

44e699237aca10e0e3c5c219a06260e8715b16d8da6fa8a6e5e878f2c66ad9c639ba0d69ecc5aef8d2afb91c42b7a36fe0b7969d3b36d3b2ace21c6bb2c512c2

Change Log

  • Fix an issue where data was not visible on the world map until the opacity setting had been changed

  • Fixes an issue when some user-defined styles weren’t being applied to a chart after a page refresh or when exported to a dashboard widget

  • Fixes an issue where optimizeAndSaveQueryCoordinationPartitions could attempt to save a partitioning table to global with gaps in the partition list. This caused queries to fail, and repeated logging of a validation error.

Humio 1.26.0

Dark Mode

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.26.0

Stable

2021-05-20

2022-05-20

1.16.0

No

No

JAR Checksum

Value

MD5

5f8abd037b3f73eaac8d5882fa58e4ec

SHA1

85971d1f18228a81f46f6f6334196fd918647438

SHA256

4e0ad70a2c9275742aee8a0181eee2e20c6496ba16b8f6fb93490b84b5031b5e

SHA512

425cacd3de3f54c2813dd3915ad35aed67de2f11a80d9c2fbf96055b030158b5d60c31686e121e613df855e6f0bdaad9d02f1c9e61a4df24b8f69cfd3193f56d

Breaking Change

The HEC ingest endpoint will no longer implicitly parse logs using the built-in kv parser. Previously, a log ingested using this endpoint would implicitly be parsed with the kv parser when the supplied event field was given as a string. For instance, this log:

json
{
 "time" : 1537537729.0,
 "event" : "Fri, 21 Sep 2018 13:48:49 GMT - system started name=webserver",
 "source" : "/var/log/application.log",
 "sourcetype" : "applog",
 "fields" : { "#env" : "prod" }
}

Would be parsed, so that the resulting Humio event would contain the field name=webserver.

If you don’t wish this behavior to change, you will have to perform this parsing operation explicitly.

When ingesting into the HEC endpoint, you are using an ingest token to authenticate with Humio. If that token does not have an associated parser, all you need to do is assign the kv parser to the token.

If your ingest token already has an assigned parser, you will need to prepend the code of that parser with this code snippet:

humio
kvParse(@rawstring) | findTimestamp(addErrors=false) |

Dark Mode

Dark Mode is a new visual theme throughout Humio (except some settings pages) that is tailored to offer great readability in dark environments, to not brighten the entire room when used on dashboards, and offer a unique visual style that some users prefer simply for its aesthetics. In 1.25 users are going to see a modal dialogue that asks what mode users would like to have; dark mode, light mode or follow the OS theme. This setting can later be changed in the settings menu.

Known Issues

A regression can cause 1.26.0 to repeatedly error log and fail to start queries in cases where the list of hosts in the cluster is not fixed. This is particularly likely to affect clusters running with ephemeral disks. The regression is fixed in 1.26.1.

Change Log

Humio 1.25.3

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.25.3

Preview

2021-05-10

2021-05-20

1.16.0

No

No

JAR Checksum

Value

MD5

08d8b9bfd9692b992a0f564426041717

SHA1

463df975e2f50c3ae3de888b454a2d1a7285f148

SHA256

06167df8dabc6211a26edc4aede8d2461ded183e7bb6f1ef527f1b8a441f52b0

SHA512

dbbed239b977af08889433e9f020bbdcb02b5f9496ab2a7eb410d967eb72ef7a4dcfde93374d36a3fe8c5798b35527f2594c025b6c68a3517c20e6f32e5d4ad9

Change Log

  • Minor bug fixes and improvements.

  • Removes error logs from the alert job when running alerts on a sandbox repository.

Humio 1.25.2

Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.25.2

Preview

2021-05-06

2021-05-20

1.16.0

No

No

JAR Checksum

Value

MD5

29b0554b42990118d22fb674e0f6b397

SHA1

ce0ee5e134123fa5ccde8dc012fb1822722140ff

SHA256

9374d762c00d5aa1884f163391fa13149e74f22e428ff849f15124ded001c033

SHA512

52b14b36db509515fb1d25e2e346b3a920493cdfd7f4862ebdee892014d14394d19e2324da60ec7d1f7137b1eef50c9716499e174e1f910f7a33f437aee1c053

Change Log

  • Fixes problem where having many nodes and a large global could lead to deadlocks in the global consistency check.

Humio 1.25.1

Dark Mode

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.25.1

Preview

2021-05-04

2021-05-20

1.16.0

No

No

JAR Checksum

Value

MD5

7e4477532960f4662ee7f3c11681d640

SHA1

8f7d79294eb27af73333252b2177e3b1467fa01e

SHA256

44b0be0f312c747f1b4f32ca34613bccdc47330100d3d74381731e556e2da999

SHA512

b3624257bd69d0d0e123e7af5010da3d49680f0d286c1ad4daae50f75bfc8ea0cea35836c8e233c09c1f3ee4e5c02ecbc91850c0a0af30afb59e26206c0de125

Known Issues

There is a serious issue affecting larger clusters in this release. The global inconsistency checker job can cause the thread responsible for reading changes from global to hang. It is possible to work around this by disabling the job using RUN_GLOBAL_CONSISTENCY_CHECKER_JOB=false. This is fixed in 1.25.2.

Change Log

  • Makes disabled items in the main menu look disabled in dark mode

Humio 1.25.0

Dark Mode

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.25.0

Preview

2021-04-29

2021-05-20

1.16.0

No

No

JAR Checksum

Value

MD5

aa7d71e3617d71ec800f1e5e898cb328

SHA1

8e815fd8c1d6a0bc1c22e096e8f82d08d40ea172

SHA256

7f26e858df2f1e16a64f44c6ac72948267eb317d884ad1db72b3799adcc95696

SHA512

1f447d204ecb3e60c80835e02a4fe8e6c7984728df5b31827b23f2278e00a0862a78dabe8ef01a2295f925a351693bdbb1d649c83465bf0951b040eab466fbad

Known Issues

There is a serious issue affecting larger clusters in this release. The global inconsistency checker job can cause the thread responsible for reading changes from global to hang. It is possible to work around this by disabling the job using RUN_GLOBAL_CONSISTENCY_CHECKER_JOB=false. This is fixed in 1.25.2 (and 1.26.0).

Breaking Change

The HEC ingest endpoint will no longer implicitly parse logs using the built-in kv parser. Previously, a log ingested using this endpoint would implicitly be parsed with the kv parser when the supplied event field was given as a string. For instance, this log:

json
{
 "time" : 1537537729.0,
 "event" : "Fri, 21 Sep 2018 13:48:49 GMT - system started name=webserver",
 "source" : "/var/log/application.log",
 "sourcetype" : "applog",
 "fields" : { "#env" : "prod" }
}

Would be parsed, so that the resulting Humio event would contain the field name=webserver.

If you don’t wish this behavior to change, you will have to perform this parsing operation explicitly.

When ingesting into the HEC endpoint, you are using an ingest token to authenticate with Humio. If that token does not have an associated parser, all you need to do is assign the kv parser to the token.

If your ingest token already has an assigned parser, you will need to prepend the code of that parser with this code snippet:

humio
kvParse(@rawstring) | findTimestamp(addErrors=false) |

Dark Mode

Dark Mode is a new visual theme throughout Humio (except some settings pages) that is tailored to offer great readability in dark environments, to not brighten the entire room when used on dashboards, and offer a unique visual style that some users prefer simply for its aesthetics. In 1.25 users are going to see a modal dialogue that asks what mode users would like to have; dark mode, light mode or follow the OS theme. This setting can later be changed in the settings menu.

Change Log

  • The HEC ingest endpoint is no longer implicitly running Query Function kvParse(). This used to be the case when ingesting events of the form "event" : "Log line...". If the ingested data is to be key-value parsed, add kvParse() to the relevant parser for the input data.

  • When a query is cancelled, a reason for canceling the query is now always logged. Previously, this was only done if the query was cancelled due to an internal exception. Look for log lines starting with query is cancelled.

  • Allow user groups to be represented as a json string and not only as an array when logging in with oauth.

  • Reworked initialization of Humio’s async listener infrastructure, to ensure that listeners do not miss any updates. This fixes a number of flakiness issues that could arise when a node was rebooted.

  • When running alerts and scheduled searches, all logging related to a specific alert or scheduled search will now be logged to the humio-activity repository, instead of the humio repository. Error logs will still be logged to the humio repository as well.

  • Changed the built-in audit-log parser so that null values are stored as an empty string value. Previously, they were stored as the string “null”. The defaults are consistent with the old behavior, so that null values become a “null” string and empty string values are kept.

  • Query poll responses meta data now include Query Quota spent for current user across queries. The cost so far of the current query was there already.

  • Optimized the splitstring() function.

  • Improved error logging for event forwarding

  • Some minor performance improvements in the ingest pipeline

  • Added a new query function: base64Decode()

  • Added audit logging when assigning a parser to an ingest token or unassigning a parser from an ingest token. Added the parser name to all audit logs for ingest tokens.

  • Added new parameters handleNull and excludeEmpty to parseJson() to control how null and empty string values are handled.

  • Added a warning to the Cluster Nodes page that warns you if not all Humio servers are running the same Humio version.

  • Added IP ASN Database license information to the Cluster Administration page

  • Added documentation link to autocomplete description in the Humio search field

  • Bumped minimum supported versions of Chrome and Chromium from 60 to 69 due to updated dependencies

  • Refreshing actions while creating alerts and scheduled searches now happens automatically, but can also be triggered manually using a button.

Configuration Changes

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

  • New config: SEGMENTMOVER_EXECUTOR_CORES allows tuning number of concurrent fetches of segments from other nodes to this node. Defaults to vCPU/8, must be at least 2.

  • New config: S3_ARCHIVING_IBM_COMPAT for compatility with S3 archiving to IBM Cloud Object Storage.

  • Removed the QUERY_QUOTA_EXCEEDED_PENALTY configuration.

GraphQL

  • Deprecates GraphQL fields UserSettings.isEventListOrderChangedMessageDismissed, UserSettings.isNewRepoHelpDismissed, and UserSettings.settings since they are not used for anything anymore, and will be removed in a future release.

  • The updateSettings GraphQL mutation has been marked as unstable, as it can control unstable and ephemeral settings.

  • The SearchDomain.queries GraphQL field has been deprecated. Use SearchDomain.savedQueries instead.

  • The SearchDomain.viewerCanChangeConnections GraphQL field has been deprecated. Use SearchDomain.isActionAllowed instead.

  • Removes the deprecated Repository.isFreemium GraphQL field.

Fixes

  • Made it possible to delete a parser overriding a built-in parser, even though it is used in an ingest token.

  • Make the parseleef() function more robust and optimize its memory usage.

  • When installing an application package, you sometimes had to refresh the page to get the assets in the package linked to their installed counter parts.

  • Rework how Humio caches data from global. This fixes a number of data races, where Humio nodes could temporarily get an incorrect view of global.

  • Fixed a bug where a scheduled search would be executed repeatedly, as long as at least one out of multiple actions was failing. Now, execution is only repeated if all actions are failing.

  • Fixed a bug that made it possible to rename a parser to an existing name and thereby overwriting the existing parser.

  • Fixed a bug that made it impossible to copy a parser to override a built-in parser.

  • Fixed a bug where cidr() did not respect the include parameter

  • Fixed a bug which could cause head(), tail(), sort() within either bucket() or a live query to return too few results in certain cases.

  • Fixed an issue where clicking the label of a parser rerouted erroneously

Humio 1.24.4

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.24.4

Stable

2021-05-31

2022-04-06

1.16.0

No

No

JAR Checksum

Value

MD5

83588b8570c97dc8a89b46524ea8d92a

SHA1

15958a097eaba9689a43c557e1d6d14e2d566d6d

SHA256

cafca561035aec00f5971a15cf283b757794c8a2706829518a05ce089f92ea88

SHA512

15352a96bb6b4ed27ef1c7b238cf97142c36cfefe17be25bf671a706bd6afcf0c8ad8951a325838e259eeb52e643f3950b8f47f3186ecea049f34fc81e066eed

Change Log

  • Fix a stackoverflow that could occur during startup in larger clusters.

  • Minor bug fixes and improvements.

Humio 1.24.3

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.24.3

Stable

2021-05-10

2022-04-06

1.16.0

No

No

JAR Checksum

Value

MD5

adb3c4827d86d476d104ab2ba8ec3171

SHA1

06a25ba15bf28659900807a8505860f5b32a65d6

SHA256

bae28e700dc6806496fd351ffb865a80420f0757613546076b4a2e9aae719d8d

SHA512

aff4adf71e1140ffdbeebfef7eae451d0bbff41f5af1753dee13d1287635644228336da0de300208fe1e667ae151198c74b74fdf10d830d37ae9b072f136a7a4

Change Log

  • Minor bug fixes and improvements.

Humio 1.24.2

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.24.2

Stable

2021-04-19

2022-04-06

1.16.0

No

No

JAR Checksum

Value

MD5

69a6ef22d7f295f807ceef46c8c0c6d1

SHA1

6284ee05bd7c583044f6620f385864a3be3bab84

SHA256

cc648f1c4efe01d20e9f93a77b1892291077ae76339d1b5dcbc0e504f9975e25

SHA512

54c60624a5c0ef19c12fcda05b4fecbe8ddf626246c3160d90f29cc76143dfbe4b07f7d884616699486848f0e7b8c519c0e1d5f5dd3e2be3e8b0a6f49fe960c5

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.

Change Log

  • 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

Humio 1.24.1

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.24.1

Stable

2021-04-12

2022-04-06

1.16.0

No

No

JAR Checksum

Value

MD5

b7fec8d3a5c0b521a371dbeb6e56d8b2

SHA1

fbabef325eaaf1bd0a3052f51497f00779efad5f

SHA256

223e48fe647fc681456b47cad81d0fca5936d6283791b2a41fa4c8dc199c1c76

SHA512

51663220d67bb25f67b7e44837e84c87c36c3f24da69918b1a6978fc751543a2f1f25f49f166681def7a0276881907b284a52bb302fa6d745d7b16859d3f7d96

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.

Change Log

  • 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

Humio 1.24.0

Humio Activity Log and GraphQL API Policy

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.24.0

Stable

2021-04-06

2022-04-06

1.16.0

No

No

JAR Checksum

Value

MD5

cbee15b1c1af8d13984fbd938e9f9488

SHA1

8562af8753aca033d6b4966311787c2a681116dc

SHA256

7cda1dd2188ec2ed5899c5a4c26cf45c2f2d4199439342da64819194475b5cf2

SHA512

ad9e05ed84cd08f8774b5bbec44b8075ebb9e2cd7898f7d6f88fc445a5e1476284b86b1d3d5536ecdf1609b7c8b4e05d3ad27302dd79e41f95094140c12ce002

Important Information about Upgrading

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.

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 the Internal Logging documentation.

GraphQL API Policy

Humio has decided to adopt an evolutionary 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:

humio
{
  "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.

Change Log

  • Major changes: 1.23.0 and 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_PENALTY config (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.

Humio 1.23.1

Humio Activity Log and GraphQL API Policy

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.23.1

Stable

2021-03-24

2021-04-06

1.16.0

No

No

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

Change Log

  • Allow users group to be represented as a json string and not only array when logging in with oauth.

  • New config: S3_ARCHIVING_IBM_COMPAT for compatibility with S3 archiving to IBM Cloud Object Storage.

Humio 1.23.0

Humio Activity Log and GraphQL API Policy

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.23.0

Preview

2021-03-18

2021-04-06

1.16.0

No

No

JAR Checksum

Value

MD5

882c77cb19e867084fbb26dc80c079d8

SHA1

053d49648f03fd49f0766aa9df64f66921c72638

SHA256

898f1670010d25866f9fb27e054509a2ade615dbae612cdc70ce34371e03ac59

SHA512

eba333bfec11983f6140ca4e64ec725c91c0d724f245c0250f2264a9221036a7d9e89aace2bf096ce7b5ecca72b4c24659348feba7098d89a5a4035359d8b8d3

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.23.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.23.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 Internal Logging documentation.

GraphQL API policy

Humio has decided to adopt an evolutionary 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:

humio
{
  "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.

Change Log

  • Added IP Filter for readonly dashboard links, and started to audit log readonly dashboard access. In this initial version. The readonly ip filter can be configured with the graphql mutation:

    humio
    mutation {
      updateReadonlyDashboardIPFilter(ipFilter: "FILTER")
    }
    

    The FILTER is expected in this format: ip-filter. From Humio 1.25 this can be configured in the configuration UI.

  • Added GraphQL queries and mutations for alerts and actions, which correspond to the deprecated REST endpoints for those entities.

  • Added GraphQL mutations addAlertLabelV2, removeAlertLabelV2, addStarToAlertV2 and removeStarFromAlertV2.

  • Added an option to make it easier to diagnose problems by detecting inconsistencies between globals in different Humio instances. Each Humio instance has its own copy of the global state which must all be identical. It has happened that they were not, so now we check and if there is a difference we report an error and dump the global state into a file.

  • Added a new introduction message to empty repositories.

  • Added mode parameter to match(), allowing different ways to match the key.

  • Added support for CIDR matching on match() using mode=cidr.

  • Improved performance when using match() with mode=cidr compared to using cidr() with file().

  • Negated, non-strict match() or lookup() is no longer allowed.

  • Deprecated glob parameter on match(), use mode=glob instead.

  • Deprecated file and column parameter on cidr(). Use match() with mode=cidr instead.

  • Deprecated the ReadEvents enum variant from the ViewAction enum in GraphQL. Use the ReadContents variant instead, which has the same semantics, but a more accurate name. ReadEvents will be removed in a future release.

  • Deprecated the REST endpoints for alerts and actions.

  • Deprecated GraphQL mutations addAlertLabel, removeAlertLabel, addStarToAlert and removeStarFromAlert as they did not follow the standard for mutation input.

  • The GraphQL API Explorer is now available from inside Humio. You can access it using the Help->API Explorer menu.

  • The GraphQL API Explorer has been upgraded to a newer version. The new version includes a history of the queries that have been run.

  • The SearchDomain.queries GraphQL field has been deprecated, and will be removed in a future release. Use SearchDomain.savedQueries instead.

  • The SearchDomain.viewerCanChangeConnections GraphQL field has been deprecated, and will be removed in a future release. Use SearchDomain.isActionAllowed instead.

  • Allow turning encryption of files stored in bucket storage off by explicitly setting S3_STORAGE_ENCRYPTION_KEY=off (similar for GCP_ )

  • Removed the deprecated Repository.isFreemium GraphQL field.

  • Removed support for shorthand IPv4 CIDR notation in cidr(). See section “Removed support for CIDR shorthand”.

  • Changed the URL of the Kafka cluster page in the settings.

  • Implemented toggle button for dark mode.

  • UI enhancements for the new repository Access Permissions page.

  • Mark required fields on the Accept Terms and Conditions page.

  • Enforce accepting terms and conditions.

  • Enforce permissions to enter Organization Settings page.

  • Enforce permissions to enter creating new repository page.

  • Refactor All Organizations page.

  • Refactor Organization Overview page.

  • Refactor client side action cache of allowed permissions.

  • Refactor how the width of the repository name in the main navigation bar is calculated.

  • It is again possible to sort the events on the test parser page.

  • Made the S3 archiving save button work again.

  • Restyled the alert dialogue.

  • Improved memory use for certain numerical aggregrating functions

  • Improved performance of free-text search using regular expressions

  • Fixed the requirement condition for the time retention on a repository.

  • Fixed an issue which caused ingest-to-multiple-repos to break, when the parser used copyEvent to duplicate the input events into multiple repositories

  • Fixed an issue causing undersized segment merging to repeatedly fetch the same segments, in cases where the merger job took too long to finish.

  • Fixed an issue where regular expressions too large to handle would sometimes cause the query to hang. Now we report an error.

  • Fixed an issue with the Missing Segments API that caused missing segments to not appear in the missing segments list if they had a replacement segment.

  • Fixed an issue where changes to files would not propagate to parsers or event forwarders.

  • Fixed an issue where Prometheus metrics always reported 0.0 for humio_primary_disk_usage

  • Fixed a bug in event forwarding that made start(), end() and now() return the time at which the event forwarding rule was cached. Instead, now() will return the time at which the event forwarding rule was run. start() and end() were never meant to be used in an event forwarding rule and will return 0, which means Unix Epoch.

  • Fixes a bug where events deleted with the delete-event API would appear deleted at first, but then resurface again after 24h. If user applying delete did not have permission to search the events being deleted.

  • Fixed a bug which caused in() with values=[] to give incorrect results

  • Fixed a bug which caused match() to give incorrect results in certain cases due to incorrect caching

  • Fixed a bug which caused glob-patterns in match() to not match newline characters

  • Fixed a bug which caused tag-filters in anonymous functions to not work in certain cases (causing to many events to be let through)

  • Fixed a bug where the same regex pattern occurring multiple times in a query could cause incorrect results

Humio 1.22.1

Minor Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.22.1

Stable

2021-03-02

2022-03-02

1.16.0

No

No

JAR Checksum

Value

MD5

7d2fb4c0736d1c7f03197fba78a33c13

SHA1

36c3c2b7ffe3485fb9f87a75b515cb7b9efc5efc

SHA256

bc3122c71e8c1bdf57fc044912c660b86933c871758818fb93a8d609c9bc340d

SHA512

54e1da57da87480a2b1b0cc577eb731b734b8fe7af0e2ac3afcd406d28f29ffa5b834d836b283dc5e730b10bba43d55484cd8579746c800bd26a26280a088200

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.

Change Log

  • Fixes problem where alertpages have no height in Safari.

  • Fixes parserlist having no height on Safari.

  • Fixes overflowing editor bug.

Humio 1.22.0

Complete UI Revamp

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.22.0

Stable

2021-03-02

2022-03-02

1.16.0

No

Yes

JAR Checksum

Value

MD5

115532e6c7c321a1fe737bdde5731f4b

SHA1

8a42ec6f7ba168939c60d521d30eba202479173e

SHA256

4cff315346b9edb1ba625f48fe36105666dc9b95e711190578ff62752fa763e4

SHA512

0173d8b48f8612198cb4a20146b15d23769cacee4fac12a7c710a93ef2f17a30140ccee8e09c8f7c5262815cbb2e03876fe30986f276a9d36155832c4e03a233

Important Information about Upgrading

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.

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

Change Log

  • Major changes: (see version 1.21.0 and 1.21.1 release notes)

  • 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

Humio 1.21.1

Minor Bug Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.21.1

Preview

2021-02-23

2021-03-02

1.16.0

No

No

JAR Checksum

Value

MD5

3f2b7ae5265ab8e81d339ebbd260b802

SHA1

e406e539b9d3474a25accc82d49efdbcc94c7f4d

SHA256

0ec0db6bfaa232c30d1e0056442f58e5d2c20d9b7716ba136b8350d2c5c05bdd

SHA512

01383adbe54ceb73679aece980b0a7752b07478a40ac3f811a3aadbf9fb55077ebf08842cb2442628af1200e677d0db289a6007b3706794c79377787ef56e898

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

Change Log

  • Improve performance of “decrypt step” in downloads from bucket storage

  • New “prefetch from bucket” job. When a node starts with an empty disk it will download a relevant subset of segment files from the bucket in order to have them present locally for queries.

  • Server: header in responses from from Humio HTTP server now includes (Vhost, NodeRole) after the version string.

Humio 1.21.0

Complete UI Revamp

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.21.0

Preview

2021-02-22

2021-03-02

1.16.0

No

No

JAR Checksum

Value

MD5

3175d041a4c0a6948d5e23993b7a3bcd

SHA1

1356a57098602623b5cab8511f530aab3b04a080

SHA256

8f576aca2a00533180ed3710971bd9c4c419e275d618c4c745d004b9a5ad9987

SHA512

475c72b5655744be0a900269478d930942cd7aae9ec8acf0e38c1eff2a4c7ec243c91293996ad8288ec2ed9c72b896436bb8e12b67f44b999fc03d1f43db4a2d

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

Change Log

  • The default parser kv has been changed from using the parseTimestamp() function to use the findTimestamp() function. This will make it able to parse more timestamp formats. It will still only parse timestamps with a timezone. It also no longer adds a timezone field with the extracted timestamp string. This was only done for parsing the timestamp and not meant for storing on the event. To keep the old functionality, clone the kv parser in the relevant repositories and store the cloned parser with the name kv. This can be done before upgrading to this release. See Built-In kv Parser.

  • kvParse() now unescapes backslashes when they’re inside (' or ") quotes.

  • kvParse() now only unescapes quotes and backslashes that are inside a quoted string.

  • kvParse() now also unescapes single quotes. (')

  • The findTimestamp() function has been changed, so that it no longer has a default value for the timezone parameter. Previously, the default was UTC. If no timezone argument is supplied to the function, it will not parse timestamps that do not contain a timezone. To get the old functionality, simply add timezone=UTC to the function. This can be done before upgrading to this release.

  • The deprecated built-in parser json-for-notifier has been deleted. It has been replaced by the parser json-for-action.

  • The deprecated built-in parser bro-json has been deleted. It has been replaced by the parser zeek-json.

  • The split() function no longer adds a @display field to the event it outputs.

  • Make the thread dump job run on a dedicated thread, rather than running on the thread pool shared with other jobs.

  • Added support for disaster recovery of a cluster where all nodes including Kafka has been lost, restoring the state present in bucket storage as a fresh cluster using the old bucket as read-only, and forming a fresh cluster from that. New Configs: S3_RECOVER_FROM_REPLACE_REGION and S3_RECOVER_FROM_REPLACE_BUCKET to allow modifying names of region/bucket while recovering to allow running on a replica, specifying read-only source using S3_RECOVER_FROM_* for all the bucket storage target parameters otherwise named S3_STORAGE_*

  • Improve hit rate of query state cache by allowing similar but not identical queries to share cache when the entry in the cache can form the basis for both. The cache format is incompatible with previous versions, this is handled internally by handling incompatible cache entries as cache misses.

  • Improve performance of writeJson() a bit.

  • Improve number formatting in certain places by being better at removing trailing zeros.

  • Change handling of groupBy() in live-queries which should in many cases reduce memory cost.

  • The experimental function moment has been removed.

  • subnet() now reports an error if its argument bits is outside the range 0 to 32.

  • The transpose function now reports an error if the arguments header or column is provided together with the argument pivot.

  • The replace() function now reports an error if the arguments replacement and with are provided at the same time.

  • The replace() function now reports an error if an unsupported flag is provided in the flags argument.

  • The functions worldMap() and geohash() now errors if requested precision is greater than 12.

  • When on ephemeral disks, nodes being replaced with new ones on empty disks no longer download most of the segments they had before being replaced, but instead schedule downloads based on is being searched.

  • The Auth0 login page will no longer load a local version of the Auth-Lock library, but instead load a login script hosted on Auth0’s CDN. This may require opening access to https://cdn.auth0.com/ if hosting Humio behind a firewall.

  • Lowered the severity level for some loggings for running alerts.

  • Made loggings for running alerts more consistent and more structured. All loggings regarding a specific alert will contain the keys alertId, alertName and viewId. Loggings regarding the alert query will always contain the key externalQueryId and sometimes also the keys queryId with the internal id and query with the actual query string. If there are problems with the run-as-user, the id of that user is logged with the key user.

  • Made loggings for running scheduled searches more consistent and more structured. All loggings regarding a specific alert will contain the keys scheduledSearchId, scheduledSearchName and viewId. Loggings regarding the alert query will always contain the key externalQueryId and sometimes also the keys queryId with the internal id and query with the actual query string. If there are problems with the run-as-user, the id of that user is logged with the key user.

  • Prevent Humio from booting when Zookeeper has been reset but Kafka has not.

  • Create, update and delete of an alert, scheduled search or action is now recorded in the audit log.

  • Running test of a parser is no longer recorded in the audit log, and irrelevant fields are no longer recorded upon parser deletion.

  • When using filters on dashboards, you can now easily reset the filter, either removing it completely, or using the default filter if one is present.

  • Made sure the humio view humio default parser is only installed when missing, instead of overwriting it every time humio starts.

  • When exporting a package, you now get a preview of the icon you’ve added for the package.

  • Packages can now be updated with the same version but new content. This makes iterating over a package before finalizing it easier.

  • Humio insights package installed if missing on the humio view when humio is started.

  • Raised the parser test character length limit to 20000.

  • Raised the note widget text length limit to 20000.

  • Fixed a performance and a robustness problem with the function unit:convert(). The formatting of the numbers in its output may in some cases be different now.

  • Fixed a number of potential concurrency issues.

  • Fixed a memory leak in rdns() in cases where many different name servers are used.

  • Fixed a bug in parseJson which resulted in failed JSON parsing if an object contained an empty key ("").

  • Fixed a bug which caused eventInternals() to crash if used late in the pipeline.

  • Fixed a bug which caused validation to miss rejecting window() inside window() and session().

  • Fixed a bug which could cause saving of query state cache to take a rather long time.

  • Fixed a bug which could potentially cause a query state cache file to be read in an incomplete state.

  • 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 analysis of a regex could consume extreme amounts of memory.

  • Fixed a bug in lowercase() which caused the case lowercase(field="\*", include="values") to not process all fields but only the field named "\*".

  • Fixed a bug where referenced saved queries were not referenced correctly after exporting them as part of a package.

  • Fixed bugs in format() which caused output from ‘%e’/’%g’ to be incorrect in certain cases.

  • Fixed an issue causing Humio to crash when attempting to delete an idle empty datasource right as the datasource receives new data.

  • Fixed an issue with the validation of the query prefix set on a view for each repository within the view: Invoking macros is not allowed and was correctly rejected when creating a view, but was not rejected when editing an existing connection.

  • Fixed an issue where merge of segments were reported as failed due to input files being deleted while merging. This is not an error, and is no longer reported as such.

  • Fixed an issue where the segment mover might schedule too many segments for transfer at a time.

  • Fixed an issue with lack of escaping in filename when downloading.

  • Fixed an issue causing segment tombstones to potentially be deleted too early if bucket storage is enabled, causing an error log.

  • Fixed an issue causing event redirection to break when using copyEvent to get the same events ingested into multiple repositories.

  • Fixed an issue where repeating queries would not validate in alerts.

  • Fixed an issue where cancelled queries could be cached.

Humio 1.20.4

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.20.4

Stable

2021-02-22

2022-01-28

1.16.0

No

No

JAR Checksum

Value

MD5

e84da693a3ca628775ca56a33f27db91

SHA1

fd2a37750456d861a92ee41840701c2040b71d79

SHA256

0fc7d2b010abbc263ef97ae4cb019994804133ff858f23de03e0bce69760011a

SHA512

9af984c0a5896046cf0f3febd3b64aef7af501404df75a612c04452140aa9cd9c97f4ed2a5a95fe241ac227db3f3bbbe072ddaa2bed058053b6cfeafcbc388e5

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.

Change Log

  • Fixed an issue causing event redirection to break when using copyEvent() function 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() functions.

  • New “prefetch from bucket” job - When a node starts with an empty disk it will download a relevant subset of segment files from the bucket in order to have them present locally for queries.

Humio 1.20.3

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.20.3

Stable

2021-02-11

2022-01-28

1.16.0

No

No

JAR Checksum

Value

MD5

eb0a1ddfb3bd3440206fc7ce95fedd74

SHA1

0eedbdc67554a9efbb0fcc5f667a99c899ae43bc

SHA256

ecdcb4a299eb3668ed6d5435c97469b4f7b1423f239f4e0a4b95a88d9b8fd566

SHA512

53dd06169c01eaccc6766f53f6a7c71910c131d7600bfdcdb3f9796d61e7ccdcfa801d8b2a2b9ed4b205fa7c3e567dc2a9a3b6879c94e10f408892cd0d57d77d

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.

Change Log

  • Improve auto completion suggestions.

Humio 1.20.2

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.20.2

Stable

2021-02-11

2022-01-28

1.16.0

No

No

JAR Checksum

Value

MD5

c8369fd679e4ef4fb1ddad2a632156e1

SHA1

7dc7214d24c3314fa9e60128106aed4078b2c7c9

SHA256

e1c8188fd7e0dc92c648a675514627c4a9ae0f52658aac748d35a0105347c4ba

SHA512

fea474b22bebcbe7c5ad1e142fbf157f495b58726951e8b52820475fdda5eb48503a76bef7e2178ac3aeddcc6087d6bdd66c3ab5c67dbcf721da1ebc4bd671fa

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.

Change Log

  • 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() functions 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.

Humio 1.20.1

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.20.1

Stable

2021-02-01

2022-01-28

1.16.0

No

No

JAR Checksum

Value

MD5

5f2ccaea9f97572ec047be936d7ff0de

SHA1

5e434cc0df8b437a3974be645e80c3f2c56ec78a

SHA256

74f2fcf3d5d2bc5b1e5830d98a03512395ac7beb6456bf754e69e48e89e1d7cf

SHA512

16a58326069b3dd9e401688627e62e825249654501f63c939d245c6b501bd683c7682a634f9cb0265c17029ac8b7cdf038e57daa27a57478980115bce18c53ce

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.

Change Log

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

Humio 1.20.0

New Query Editor, Packages (in beta)

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.20.0

Stable

2021-01-28

2022-01-28

1.16.0

No

Yes

JAR Checksum

Value

MD5

095aa44f1cbaf9cdffc9753286206248

SHA1

fd4eb8cc488d18e7fedff3af212a9919d399b256

SHA256

79868d79d893ebb3114208e5e7f64d20ded44b76f4342b3b2d932df6288c927e

SHA512

9b91b51b21654ec1961ee9ba31193ad5511850cdb3623d82403356191535a74febeb51a49fb711438408898fe4222f2522f3c37b33c81c75091b6a415c2f0924

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.

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.

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

Change Log

  • Major changes (see version 1.19.0 release notes)

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

Humio 1.19.2

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.19.2

Preview

2021-01-25

2021-01-28

1.16.0

No

No

JAR Checksum

Value

MD5

01e72a42b56685f50111466e91475e9b

SHA1

7d09c09579a2c00cb2cc0a38c421969861f9c6a0

SHA256

83e7efdf3bd38eb806b30c81603e4eefe5ee17f88fa9c6440fd56d11c86d2869

SHA512

3ccc62d52899ecad9fd7626bb15f90b05bcabaf761d997c4aa63849f93702c6caf32d1f6ed191c981054c1df853ec6fbcdbd07fba0e76e289d4f71d39b542d9b

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.19.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 to minimum 1.16.0 before trying to upgrade to 1.19.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.

Change Log

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

  • Fixed automatic installation of Humio Insights package to the humio repository

Humio 1.19.1

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.19.1

Preview

2021-01-19

2021-01-28

1.16.0

No

No

JAR Checksum

Value

MD5

7ba0f9e286f6933cb19b49be72df8078

SHA1

489be0b931419cd128d5a03e2b2fbce819095257

SHA256

2f8a22da0e6f85c4cd4479367635ad9c0a0586f2fc69df55533e349e3ea29bab

SHA512

b306f424ae1425145a382be5847e46f6f56d91777202ef94117c755be5f713dab787ae6da2a4acd0091d04d07d75b3b4154185eab5327f8db558071d1b4d301f

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

Change Log

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

  • Fixed bug in a saved query in the Humio Insights package

  • Fixed an issue - Do not delete datasource before the segments have been deleted also in bucket storage if present there.

Humio 1.19.0

New Query Editor, Packages (Beta)

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.19.0

Preview

2021-01-14

2021-01-28

1.16.0

No

Yes

JAR Checksum

Value

MD5

63d03b5a7d362d1d9a5dfcb5a7d6fcea

SHA1

7ed7776a690ff76afd4ff77ac585a28ef7ee1b2c

SHA256

532dd54bc612b6f771a142899277430469a85c3a431a7824105c1ab69d21974e

SHA512

9edc286d2409cdf36496cc9a7c69ab525ac3207006f1ce3aa194bd17e59e4601f676dbdec0c71cfecd197364b45d83398e5566cebbed82e0a10e1d19ae2e91eb

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.19.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.19.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 Packages documentation.

Humio Insights Application

With the introduction of Humio packages we have created the Humio Insights Application. 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.

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

Read more about the details of internal logging.

Change Log

  • Introduced humio insights package that is installed per default on startup on the humio repository

  • Raised the limit for note widget text length to 20000

  • Raised the parser test character length to 20000.

  • No longer overwrite the humio parser in the humio repository on startup.

  • Improved app loading logic.

  • Kafka client inside Humio has been bumped from 2.4.1 to 2.6.0.

  • Improve handling of broken local cache files

  • New config QUERY_QUOTA_EXCEEDED_PENALTY with value 50 by default. When set >= 1.0 then this throttles queries from users that are over their quota by this factor rather than stopping their queries. Set to 0 to disable and revert to stopping queries.

  • For ingest using a URL with a repository name in it, Humio now fails ingest if the repository in the URL does not match the repository of the ingest token. Previously, it would just use the repository of the ingest token.

  • “Notifiers” have been renamed to “actions” throughout the UI and in log statements. The REST APIs have not been changed and all message templates can still be used.

  • In the GraphQL API, on the Alert type, the notifiers field has been deprecated and will be removed in a later release. It has been replaced by the actions field.

  • In the GraphQL API, the value ChangeAlertsAndNotifiers on the Permission enum has been deprecated and will be removed in a later release. It has been replaced by the ChangeTriggersAndActions value. The same is true for the ViewAction enum. On the ViewPermissionsType type, the administerAlerts``field has been deprecated and will be removed in a later release. It has been replaced by the ``administerTriggersAndActions field.

  • The built-in json-for-notifier parser used by the Humio Repository action (formerly notifier) is deprecated and will be removed in a later release. It has been replaced by an identical parser with the name json-for-action, see documentation.

  • The built-in bro-json parser is deprecated and will be removed in a later release. It has been replaced by an identical parser with the name zeek-json, see zeek-json.

  • The configuration option IP_FILTER_NOTIFIERS has been renamed to IP_FILTER_ACTIONS. The old name will continue to work.

  • The configuration option HTTP_PROXY_ALLOW_NOTIFIERS_NOT_USE has been renamed to HTTP_PROXY_ALLOW_ACTIONS_NOT_USE. The old name will continue to work.

  • New feature “Scheduled Searches” making it possible to run queries on a schedule and trigger actions (formerly notifiers) upon query results. See documentation.

  • New feature “Event forwarding” making it possible to forward events during ingest out of Humio to a Kafka server. See Event Forwarding documentation. Currently only available for on-prem customers.

  • The Humio Repository action (formerly notifier) now replaces a prefix ‘#’ character in field names with @tag. so that #source becomes @tag.source. This is done to make them searchable in Humio. You can change the name by creating a custom parser. See related documentation for more details.

  • The names of the metadata fields added by the Humio Repository action (formerly notifier) has been changed to accomodate that it can now also be used from scheduled searches. See related documentation for more details.

  • New filter function test( <boolean expression> ) makes it convenient to test complex expressions.

  • New ingest endpoint /api/v1/ingest/raw for ingesting singular webcalls as events. See Ingest API - Raw Data documentation.

  • API Changes (Non-Documented API): getFileContent has been moved to a field on the SearchDomain type.

  • API Changes (Non-Documented API): Queries and Mutations for Parser now expects an id field in place of a name field, when fetching and updating parsers.

  • API Changes (Non-Documented API): Getting Alert by ID has been moved to a field on the SearchDomain type.

  • New feature: “stateless Ingest-only nodes”: A node that the rest of the cluster does not know exists, but is capable of ingesting events into the ingest queue. Enable using NODE_ROLES=ingestonly.

  • unit on timechart (and bucket) now works also when the function within uses nesting and anonymous pipelines.

  • New feature “Custom ingest tokens” making it possible for root users to create ingest tokens with a custom string.

  • The function parseCEF() now deals with extension fields with labels, i.e. cs1=Value cs1Label=Key becomes cef.label.Key=Value.

  • Added asn function for retrieving the ASN number for a given IP address, see asn() reference page.

  • New config AUTO_UPDATE_MAXMIND for enabling/disabling updating of all maxmind databases. Deprecates AUTO_UPDATE_IP_LOCATION_DB, but old config will continue to work.

  • New config MAXMIND_IP_LOCATION_EDITION_ID for selecting the maxmind edition of the IP location database. Deprecates MAXMIND_EDITION_ID, but old config will continue to work.

  • New function hash for computing hashes of fields. See hash() reference page.

  • Renamed LOG4J_CONFIGURATION environment variable to HUMIO_LOG4J_CONFIGURATION. See Configuration reference pages. The old variable will no longer work.

  • New validation when creating an ingest token using the API that the parser, if specified, actually exists in the repository.

  • Humio no longer deletes an existing humio-search-all view if the CREATE_HUMIO_SEARCH_ALL environment variable is false. The view instead becomes deleteable via the admin page.

  • When a host dies and Humio reassigns digest, it will warn if a fallback host is picked that is in the same zone as existing replicas. Eliminate warning if falling back to a host in the null zone.

  • Reduced the number of writes to global on restart, due to merge targets not being properly reused.

  • Cluster management stats now shows segments as underreplicated if they are replicated to enough hosts, but are not present on all configured hosts.

  • Add an error message to the event if the user is trying to redirect it to another repo using #repo, and the target repo is invalid.

  • Make the query functions window() and series() be enabled by default. They can be disabled by setting the configuration options WINDOW_ENABLED and SERIES_ENABLED to false, respectively.

  • The transfer job will delete primary copies shortly after transferring the segments to secondary storage. The copies would previously only be deleted once a full bulk had been moved.

  • Added config option for Auth0 based sign on method: AUTH_ALLOW_SIGNUP defaults to true. The config is forwarded to the auth0 configuration for the lock widget setting: allowSignUp

  • Reduce contention on the query scheduler input queue. It was previously possible for large queries to prevent each other from starting, leading to timeouts.

  • Made cluster nodes log their own version as well as the versions of all other nodes. This makes it easier to tell which versions are running in the cluster.

  • Introduction of the new log file humio-requests.log. Also the log format for the files humio-metrics.log and humio-nonsensitive.log has changed as described above. The guide for sending Humio logs to another Humio cluster has been updated.

  • Custom made saved queries, alerts and dashboards in the humio repository searching for events of the kinds metrics, requests or nonsensitive may need to be modified. This is described in more detail in the Internal Logging documentation.

  • Upgraded Log4j2 from 2.13.3 to 2.14.0.

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

  • Updated the permission checks when polling queries. This will results in dashboard links “created by users who are either deleted or lost permissions to the view” to get unauthorized. To list all dashboard links, run this graphql query as root: query { searchDomains {dashboards { readOnlyTokens { createdBy name token } } } }

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

  • Added timeout for TCP ingest listeners. By default the connection is closed if no data is received after 5 minutes. This can be changed by setting TCP_INGEST_MAX_TIMEOUT_SECONDS. See Ingest Listeners documentation.

  • Humio will only allow using Zookeeper for node id assignment (ZOOKEEPER_URL_FOR_NODE_UUID) when configured for ephemeral disks (USING_EPHEMERAL_DISKS). When using persistent disks, there is no need for the extra complexity added by Zookeeper.

  • Fixed a rare issue where a node that was previously assigned digest could write a segment to global, even though it was no longer assigned the associated partition.

  • Fixed an rare issue where the digest coordinator would assign digest fewer hosts than configured.

  • Fixed an issue which caused free-text-search to not work correctly for large (>64KB) events.

  • Fixed crash in CleanupDatasourceFilesJob when examining a file size fails due to that file being deleted concurrently.

  • Fixed an issue where the segment rewrite job handling event deletion might rewrite segments sooner than configured.

  • Fixed an issue where canceling queries could produce a spurious error log.

  • Fixed an issue with the cidr function that would make some IPv4 subnets accept IPv6 addresses and some strings that were not valid IP addresses.

  • Fixed an issue that could cause node id assignment to fail when running on ephemeral disks and using Zookeeper for node id assignment. Nodes in this configuration will now try to pick a new id if their old id has been acquired by another node.

  • Fixed an issue causing Humio to retain deleted minisegments in global for longer than expected.

  • Fixed an issue where unit-conversion (by timechart) did not take effect through groupBy() and window().

  • Fixed an issue causing queries using kvParse() to filter out too much in specific circumstances when filtering on a field assigned before kvParse().

  • Fixed an issue causing queries using kvParse() to be executed incorrectly in certain circumstances when kvParse() assigned fields starting with a non-alphanumeric character.

  • Fixed an issue causing the secondary storage transfer job to select and queue too many segments for transfer at once. The job will now stop and recalculate the bulk to transfer periodically.

  • Fixed an issue with updating user profile, in some situations save failed.

  • Fixed an issue where the filter and groupBy buttons on the search page would not restart the search automatically

  • Fixed logic for when the organization owner panel should be shown in the User’s Danger zone.

  • Fixed an issue where segment merge occasionally reported BrokenSegmentException when merging, while the segments where not broken.

  • Fixed timeout issue in S3 Archiving

  • Fixed bug where repeating queries would not validate in alerts.

  • Fixed a bug where fullscreen mode could end up blank

Humio 1.18.4

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.18.4

Stable

2021-01-25

2021-11-26

1.16.0

No

No

JAR Checksum

Value

MD5

d6d2999c1640e0b922b79163c9ec83b5

SHA1

a0452151aaa9437a2d4f772f23d3f817080d015c

SHA256

b786cb7edf1d2b8729a44ff73ce8239688aefd2431940d283a15537b3be01b37

SHA512

cfce44d51dce08213bfc26f5bd74cf3596185bc15e87518f63cf9b601f0e8118923d61afa17770827cd1fae6547a5d11decdacc9cffb57f95f0f3b351151632d

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.

Change Log

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

Humio 1.18.3

Important Information about Upgrading

Beginning with version 1.17.0, if your current version of Humio is not directly able to upgrade to the new version, you will get an error if you attempt to start up the incompatible version. The 1.18.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.

Change Log

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

Humio 1.18.2

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.18.2

Stable

2021-01-08

2021-11-26

1.16.0

No

No

JAR Checksum

Value

MD5

325cfefc1a6eef3b4f9d1e6beeb5a53a

SHA1

a8af4a4a70c93cb6ff945c999bd0e6ea579d1a2a

SHA256

f2201aab5190ec92b540bc8be9b6ea59c2e840fece63b2d87891aff9d7fc284a

SHA512

8a1e56622041d45db967e6aa003da14fb78143fc63d3dfb936e318d385761f8a10a57823040d68b8f200048fc28006df1d281e74baad1bcdef080334a8634af5

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.

Change Log

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

Humio 1.18.1

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.18.1

Stable

2020-12-17

2021-11-26

1.16.0

No

No

JAR Checksum

Value

MD5

23a1b98323ea040221d9314e181f5048

SHA1

2364af27ee4d0e12ff3732252e31aceaa12534a9

SHA256

9f83caa9a0aa483087c28e083fb10e2d418c9f66c109abe0b7464dd312d3e873

SHA512

682242210795e8b72f82589a01a3933072c7b744a8abdc54adca3964d08c32f02504e86abd44639278cf104d79587f8b0d0b89b807fc3ba321e04c3644c6dfab

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.

Change Log

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

Humio 1.18.0

Repeating Queries, Search Result Caching and New Query Functions

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.18.0

Stable

2020-11-26

2021-11-26

1.16.0

No

Yes

JAR Checksum

Value

MD5

0525cf2284207efde5655fd9174c411f

SHA1

9d28fc3e60a033c27746584ac10fd5abedb2af69

SHA256

5f2a5cfa60bc13c859caa2e07a1dbd3a907d15483cc7d5829d02646f8350d61c

SHA512

be22b5126137fa75d0d5ac5a870c716fadee85155bb58822d710397e633de9acbb060c7500f46031a3996e826c5d3b3ee5c0b0c1d572b3944f1be5ebc05cffca

Important Information about Upgrading

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.

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 beta:repeating() reference page 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.

The function 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 series() reference page 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).

Change Log

  • Major changes (see 1.17.0 release notes)

  • 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

Humio 1.17.0

Repeating Queries, Search Result Caching and New Query Functions

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.17.0

Preview

2020-11-18

2020-11-26

1.16.0

No

Yes

JAR Checksum

Value

MD5

9c47009810132eb67177966d10471544

SHA1

341a2607265420b1a2d461ad111c88aca06419ed

SHA256

59001d9a738930f8774c11864ce3c36b3b4b4003f8cad0d4b36af13275ceefa9

SHA512

ee8e2837a8fba2b28aab8d18b16269f452f19a5c80ad9826ecbeb73eaa062236acdf2191cc448e60d81390f1a2881374637adce7603ebf9f0861ca6246f6c82f

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.17.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.17.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 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 beta:repeating() reference page 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.

The function 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 series() reference page 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).

Change Log

  • New config option IP_FILTER_NOTIFIERS, to set up IP filters for Alert Notifications, see IP Filter reference page.

  • New config option ENABLE_ALERTS makes it possible to disable alerts from running (enabled by default).

  • New config option ALERT_DESPITE_WARNINGS makes it possible to trigger alerts even when warnings occur.

  • New config option DEFAULT_MAX_NUMBER_OF_GLOBALDATA_DUMPS_TO_KEEP.

  • New query function parameter to parseJson, removePrefixes, see parseJson() reference page.

  • New query function concatArray, see concatArray() reference apge.

  • New query function parseCEF used to parse events which are formatted according to the Common Event Format(CEF), see parseCEF().

  • New experimental query function beta:repeating(), see beta:repeating() reference page.

  • New experimental query function series(), enabled by config option SERIES_ENABLED=true, see series() reference page.

  • New experimental query function window(), enabled by config option WINDOW_ENABLED=true, see window() reference page.

  • The {events_html} notifier template will now respect the field order from the query.

  • It is again possible to override a built-in parser in a repository by creating a parser with the same name.

  • Periodically release object pools used by mapper pipeline, to avoid a possible source of memory leaks.

  • Fix negating join expressions.

  • Fixes a bug where join function in some circumstances would fetch subquery results from other cluster nodes more than once.

  • Setting the default query for a view in the UI has been moved from the “Save as Query” to the View’s “Settings” tab.

  • The notifier list is sorted when selecting notifiers for an alert.

  • Improved wording of diagnostics regarding function arguments.

  • Tweaked location of diagnostics regarding missing function arguments.

  • API Changes (Non-Documented API): Saved Query REST API has been replaced by GraphQL.

  • API Changes (Non-Documented API): View Settings REST API has been replaced by GraphQL.

  • Allow running Humio on JDK-14 and JDK-15 to allow testing these new builds.

  • Free-text search has been fixed to behave more in line with the specification.

  • Refuse to boot if the global topic in Kafka does not contain the expected starting offset.

  • Crash the node if an exception occurs while reading from the global Kafka topic, rather than trying to recover.

  • Reduce the max fetch size for Kafka requests, as the previous size would sometimes lead to request timeouts.

  • Improve logic attempting to ensure other live nodes can act as substitutes in case the preferred digest nodes are not available when writing new segments.

  • Fixes the case where datasources receiving data might not be marked idle, causing Humio to retain too much ingest data in Kafka.

  • Fixes the case where Humio would consider local node state when deciding which ingest data was safe to delete from Kafka.

  • Fix several cases where Humio might attempt to write a message to Kafka larger than what Kafka will allow.

  • Fixes the issue where Humio could behave incompatibly with Kafka versions prior to 2.3.0 if KAFKA_MANAGED_BY_HUMIO was true.

  • Refuse to boot if the booting node would cause violations of the “Minimum previous Humio version” as listed in the release notes.

  • Fixes an issue which caused free-text-search to not work correctly for large (>64KB) events.

  • Fixes a bug where unit:convert couldn’t handle numbers in scientific notation.

  • Rename a few scheduler threads so they reflect whether they’re associated with streaming queries (“streaming-scheduler”) or not (“normal-scheduler”)

  • Fixes an issue where Humio might try to get admin access to Kafka when KAFKA_MANAGED_BY_HUMIO was false.

  • If KAFKA_MANAGED_BY_HUMIO is true, Humio will ensure unclean leader election is disabled on the global-events topic.

  • The Humio-search-all view will no longer be removed if CREATE_HUMIO_SEARCH_ALL is set to false. The view will instead become possible to delete manually via the admin UI.

  • Reduce the number of merge target updates Humio will write to global on digest leader reassignment or reboot.

  • Fixes a bug causing join() to not work after an aggregating function.

  • Fixes a bug causing sort()/head()/tail() to work incorrectly after other aggregating functions.

  • Fixes a bug causing the sub-queries of join() etc. to not see events with an @ingesttimestamp occurring later than the search time interval.

  • Fixes an issue causing Humio to fail to upload files to bucket storage in rare cases.

  • Switch from JDK to BouncyCastle provider for AES decrypt to reduce memory usage.

  • Changed default TLS ciphers and protocols accepted by Humio, see TLS Configuration reference page.

Humio 1.16.4

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.16.4

Stable

2020-11-26

2021-10-09

1.12.0

No

No

JAR Checksum

Value

MD5

d83c60916b9cb3c12501c541253b5aee

SHA1

fa164160b4874f1f1524ff61d49584a62c471868

SHA256

362d0640d4673b985c6ad9fcdcac7404dc127a65d33d0d423d15e20a5478c642

SHA512

1803bf4fa4cd533e7fd569584cd9d5ae86d649dfccbf92fdd6cf3eae6155fee9baf40ab7d252681e84ea4045264b5408cc9144fa0d6ef3b0a8a9b631cfdce45c

Change Log

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

Humio 1.16.3

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.16.3

Stable

2020-11-10

2021-10-09

1.12.0

No

No

JAR Checksum

Value

MD5

294a84c0d1a54ccb83045af2a59a711e

SHA1

74088d0dcce3e2e853d236e00d18af18ad06c0e6

SHA256

8bd243f29dbafa1ece847aff22ce9754b3ec3fd6fe8726d1517ed5462c5653fe

SHA512

ad95a600b21990508e9e174273726b8c2514b2a0f688bf45422394971375c0ad8821626ca6ca7672faffd41e4b2f80a62c357e581cdc6b34f4c482ddb5389410

Change Log

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

Humio 1.16.2

Email and Global Database Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.16.2

Stable

2020-10-30

2021-10-09

1.12.0

No

No

JAR Checksum

Value

MD5

625e7c2ab7d9ae2ad61c6b5a6847e0ec

SHA1

092049bbc1604af6fd2e0a6b8f6f53fe7f6132ae

SHA256

3850217dcbda7666178a475fcf135b3c94715ef83a4b66236921b3bb2ee4c2f9

SHA512

d7aec9e4c0bdd6102ce56df5dbac36cb896182c987b1cb8c84d1065610ed78e9e519bce7ef94b784412fa8946b63bfe51f6ef78071b60e59e955588c22ccf6d4

Change Log

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

Humio 1.16.1

Bug Fixes and Stability Enhancements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.16.1

Stable

2020-10-21

2021-10-09

1.12.0

No

No

JAR Checksum

Value

MD5

f5a2ac232db869d279159781ba5cdf57

SHA1

e165eff2f323df2702e8eb697602739ad8e71af8

SHA256

eda9a02789d70732451e0bdd01a329ca878a39dc160c95c3902acc5db693f22b

SHA512

aa13e65ce4b6896aaecfeb8dcb3996681d7014bacde126045c01d230c8f3b75a34a594653b9b7785ee8c4417a71df1908263c2931c8806893db30293780e1bf4

Change Log

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

Humio 1.16.0

Improved Alerts and Added Ingest Timestamps

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.16.0

Stable

2020-10-09

2021-10-09

1.12.0

No

No

JAR Checksum

Value

MD5

41a3eb30f6d92f92b414661545f0c8bc

SHA1

31829cf2558430a4a6f170d4adf00573f7a7db08

SHA256

f04127a4195e8e1e576bc9a32e9b582b48ffb6eb3fdbc368b4f2c0e2fc22e1c6

SHA512

45e067a2b79618e979e9839cb987ce6bd76a27514a0d3da22dd3e9b5259f48b8b75c5c9730078ccba81f10516a456b733956bc48bdec6c9bd5adb9dd0de13363

Summary

This release promotes the latest 1.15 release from preview to stable. To see more details, go through the individual 1.15.x release notes (links in the changelog).

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.

Notifier logging to a Humio repository: It is now possible to configure an alert notifier that will log all events to a Humio repository.

Slack notifier upgrade to notify multiple Slack channels: It is now possible to use the Slack notifier to notify multiple Slack channels at once.

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.

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.

User Signup & Login Flow

Redesigned signup and 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.

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.

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 Configuration reference pages.

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.

Change Log

  • Major changes: (see 1.15.0 release notes)

  • Other changes: (see 1.15.1 release notes)

  • Other changes: (see 1.15.2 release notes)

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

Humio 1.15.2

Bug Fixes and Stability Enhancements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.15.2

Preview

2020-09-29

2020-10-09

1.12.0

No

No

JAR Checksum

Value

MD5

682ce1370121f12351ade4d22aac9d59

SHA1

4b0a7d089cadc867582ab067e80ccbaa421d6869

SHA256

64179665b0993212736c526d4c9e5af57511d2225673646c6de9f54c6685e9f9

SHA512

3d63d22285b955637128bfaaf8223e4f59c32a92b66180997307b22cdda6d360c2436f0b63fb55ee57b52cdb34a0b0ddc2ad28f4db9d63ae62e10c8f0846dc80

Change Log

  • Generate ingest tokens in UUID format, replacing the current format for any new tokens being created.

  • In the dialog for saving a search as an alert, the save button is no longer always grey and boring, but can actually save alerts again.

  • Fixed a problem where the login link did not work in Safari and Firefox.

  • Fixed a problem with scrolling on the login page on screens with low resolution.

  • Made the login and sign up pages responsive to the device.

  • Fixed a bug in the partition table optimizer that lead to unbalanced layouts.

  • Fixed a bug causing an authentication error when trying to download a file when authenticating by proxy.

  • Fixed an issue showing duplicate entries when searching for users.

  • Fixed a memory leak when authenticating in AWS setups.

  • Avoid overloading kafka with updates for the global database by collecting operations in bulk.

  • Only consider fully replicated data when calculating which offsets can be pruned from Kafka.

  • Improved naming of threads to get more usable thread dumps.

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

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

  • Improved handling of sub-queries polling state from the main query when using join().

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

  • Added logging to detect issues when truncating finished files.

Humio 1.15.1

Bug Fixes and IP Location DB HTTP_PROXY Support

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.15.1

Preview

2020-09-22

2020-10-09

1.12.0

No

No

JAR Checksum

Value

MD5

ec66230819ad11297969c2f8d6641c6d

SHA1

f3b0201a632842dd67f104c325c241b201d246a6

SHA256

81de2fd8b1ccc692f30083f0461364155f83b96b893c0cdff4444fbbb97abf32

SHA512

2281a3fbf186bd96d56343a7ec46caefcd59fa6656ca8885f841af2ce16c32068739d510b7a0913e9c5db5670948fbf43e998595b8a535246299d7ecd418e21b

Change Log

  • The job for updating the IP location database now uses the configured HTTP proxy, if present.

  • Fixed a problem with AWS, where STS tokens would fail to authenticate.

  • Fixed a problem in the UI, where the wrong timestamp was displayed as @ingesttimestamp.

  • Revert login UI to same behavior as before 1.15.0.

Humio 1.15.0

Improved Alerts and Added Ingest Timestamps

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.15.0

Preview

2020-09-15

2020-10-09

1.12.0

Yes

Yes

JAR Checksum

Value

MD5

516ed995115eeaa9218bdbc96aec01b2

SHA1

79bd7daeaa49644e7d7bcc429862f43c5d028057

SHA256

26c95dacd1164ba20db16917dcc436cc8a8f5a86811b697917b6febfae9fbd61

SHA512

64841a7ddfcb7c9cff0e7636e78c05c8e52cd63f5c537c858f70795e6dfb5ff52efa8705cf9d3e3fccc1f2ca3901fbae25fb3920fe09f440813f2e587b367173

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.

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.

Notifier Logging to Humio Repository

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

Slack Notifier Upgrade

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

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

Configure Notifier Not to use Internet Proxy

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

Signup & Login

We introduce new signup/login pages for social login and 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.

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.

Configure Humio Not to use Internet Proxy for S3

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

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, STORAGE_REPLICATION_FACTOR configurations). See Configuration reference pages.

Change Log

  • Bug Fix: CSV files can no longer contain unnamed columns and also trailing commas are disallowed. Queries based on such files will now fail with an error.

  • Improved error handling when a parser cannot be loaded. Before, this resulted in Humio returning an error to the log shipper. Now, data is ingested without being parsed, but marked with an error as described in Parser Errors.

  • If automatically creating users upon login and syncing their groups from the authentication mechanims, the configuration ONLY_CREATE_USER_IF_SYNCED_GROUPS_HAVE_ACCESS now controls whether users should only be created if the synced groups have access to a repository or view. The default is false.

  • Humio will set the field @ingesttimestamp on all events.

  • S3 communication can be configured to not use an HTTP proxy.

  • Upgrade to AWS SDK v2. When using Java system properties for configuring Humio bucket storage, use aws.secretAccessKey instead of aws.secretKey.

  • New explicit signup and login pages for social login.

  • Newly added users will by default get an email.

  • Alert notifiers can be configured to not use an HTTP proxy.

  • Field based throttling on alerts.

  • New alert notifier type logging to a Humio repository.

  • New alert notifier template {events_html} formatting events as an HTML table.

  • Auto-balanced partition table suggestions. See ZONE, DIGEST_REPLICATION_FACTOR, STORAGE_REPLICATION_FACTOR in configuration. See Configuration reference pages.

Humio 1.14.6

Email Notification Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.14.6

Stable

2020-10-30

2021-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

d49223f102edc33a255dd9d7178d95f0

SHA1

70b446b461381e1e02d3a994deb88c5ba3e682f2

SHA256

17d82d593a4f290867819f8095a59d0367083c022d45d9db1c33417337d7a5b8

SHA512

1d7bcdd2bd5d8385af487b8cd5a1b6da11d6a1893ade5ac5b06d44817f57e48e2679df13e9fe0f99e73723b2c306e282807fdfde9650176c19ef461c646c39fc

Summary

Email Notification Improvements

Change Log

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

Humio 1.14.5

Bug Fixes and New Metric

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.14.5

Stable

2020-10-21

2021-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

097c33aba188611a3157a00cdb7366af

SHA1

3ac3a1722ff46530ebdf6cf1a2e977437a8917e9

SHA256

cb4aa5b17dba7ca6a79494401cfaaa3e1aefce77fb029b33e24a551e9fab9a22

SHA512

e737fa3bddab0c236a37b0725f2210efd4d761977646581addb29833c31081f0cc6e84f5c514be7e860dc4e848afeae5a77ab0b3536347a1d6757ba4b1547be7

Summary

Bug Fixes and New Metric

Change Log

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

Humio 1.14.4

Bug Fixes and Stability Enhancements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.14.4

Stable

2020-10-09

2021-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

1a728a2eee16db13d2c5114ada74382c

SHA1

ec61329a161dce7a387976343babf7d3ff44527b

SHA256

2b49f98b2b112e54ec310ffb08013debcf9005af35bf97eca36cb69e438f1366

SHA512

61e0628975aee35f01b9b6d63770c307b0a2f47fe41623bef56a0bdc2f6758ec3fe3145ed1e2b4118a482c5cd0f65b1d8fc4dbf881cc63e53a724b271f4634a7

Summary

Bug Fixes and Stability Enhancements

Change Log

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

Humio 1.14.3

Bug Fixes and Improved Query Scheduling

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.14.3

Stable

2020-09-24

2021-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

98d17b3fcca4f158e5cfe0c7d95d0ac7

SHA1

57dd7e54bc414213de946119b102d6612cd0f7a1

SHA256

661b21efd3128da29f20d987cd6d9e89541bdfacd8e0391a99bef5ba3255d7ba

SHA512

7ccf6574c4da5a92975029236e762713be319c09032f066d28473ded25462d39e446ed402fa6463f8172077e05f9d91cd224c6d3a9ad3de5876fdd472bae8c0d

Summary

Bug Fixes and Improved Query Scheduling

Change Log

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

Humio 1.14.2

Bug Fixes, HEC Endpoint Validation and New Metrics

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.14.2

Stable

2020-09-17

2021-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

c3eb561c270dce0fe7468c34cbd4322f

SHA1

85c1c0e16507fa152c7adbba5844aed2c83c0e03

SHA256

5f4e382586a6069c5ebde1d1a620ab3d1f8f1c532e9ecce972a348ab669b2c2d

SHA512

f3be7379941c9f3ae677b351dc65f90da71aaf43fdc78e93eca99d3b8dfc4fd28618c9fd4d22bf4657cdc0d9b9f80d59589c3984860958aefff61f0a769251a7

Summary

Bug Fixes, HEC Endpoint Validation and New Metrics

Change Log

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

  • Added log rotation for humio-non-sensitive logs.

  • The job for updating the IP location database now uses the configured HTTP proxy, if present.

  • 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

Humio 1.14.1

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.14.1

Stable

2020-09-08

2021-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

b57e75be1b07018a158585f04cdcb9d8

SHA1

6e1754ba60abeb35233a728dcb78ae11f0986d8a

SHA256

5939bb412601b4356ccc431d87e3e8290a48db967a0739f638b0ea587e1a9eb7

SHA512

a90b03b4081cd8ee73d06c0f925705740c769ff405b09cb1c06a51b8566775d7e2540bd6275ae1f8f7e4e0a65d241d7f1f195d26c6c3474894639d6b19b7d3d3

Summary

Bug Fixes

Change Log

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

Humio 1.14.0

Free Text Search, Load Balancing of Queries and TLS Support

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.14.0

Stable

2020-08-26

2021-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

d0ede2c5d1075119507701bff7a04b29

SHA1

b4fc3f50fabe0abdea5db2a2b502c0b2b0b71aa7

SHA256

e9ddafa574576eb890cf22d241e0307caf613cc5b1bd9fdc84e50e975a40d67b

SHA512

16506530541f87579660b630265171c137b8de787b5c5d11b145fc1d18ff04038514b91469b040212dbd27bddc2cee4cb5cca0054f547917624137fedb23ba20

Summary

Free Text Search, Load Balancing of Queries and TLS Support. This release promotes the latest 1.13 release from preview to stable. To see more details, go through the individual 1.13.x release notes (links in the changelog).

Free Text Search

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 Cluster documentation and Configuration reference pages.

TLS Support

TLS encrypts 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() reference page).

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 Cluster documentation and Configuration reference pages.

Change Log

  • Major changes: (see 1.13.0 release notes)

  • Other changes: (see 1.13.1 release notes)

  • Other changes: (see 1.13.2 release notes)

  • Other changes: (see 1.13.3 release notes)

  • Other changes: (see 1.13.4 release notes)

  • Other changes: (see 1.13.5 release notes)

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

Humio 1.13.5

Security and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.13.5

Preview

2020-08-12

2020-08-26

1.12.0

No

Yes

JAR Checksum

Value

MD5

0e9345ea59cb8f76a14cf84c7889de19

SHA1

6e27b7e2ec68090ad2c6019e0b3dea56d03d4059

SHA256

3f9e0865df1c28dc69d45f764c65c39aeccfacfadeb0ec04165655ef423c7fff

SHA512

256ba3cbd99245327176569cdfde8d8cee3f8c15c2f60c0c2e02115e8fd6eefec0be3cd3dac5592d4fd2b6d5e2a609e414a963af2c6ead317171228cc001666b

Summary

Security and Bug Fixes

Change Log

  • This release fixes a security issue. More information will follow when Humio customers have had time to upgrade. See: Humio Security Disclosures.

  • Bug Fix: export to file now allows for fieldnames with special characters.

  • Bug Fix: export to file can now include query parameters

  • Bug Fix: missing migration of non-default groups would result in alerts failing until the user backing the alert logs in again.

Humio 1.13.4

Security and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.13.4

Preview

2020-08-05

2020-08-26

1.12.0

No

Yes

JAR Checksum

Value

MD5

56dd1acc53af27871de4260ff14c03f2

SHA1

10e4f5ad2079fb9c85f5fbf7f970a40a3951910c

SHA256

256b45cb00097da6ff219713d8ed4d5bf8c4dc5b1094f856de3586c2a9f7618f

SHA512

411a0f5aa3b6c96eb72dd7680d9fa94ea51e3da927c318bac0df37a2c7dee0cac9714e9807473a10417f11a3106f65107982669f9c3e29f2ac7a7a1a901a93df

Summary

Security and Bug Fixes

Change Log

  • This release fixes a security issue. For more information see: Humio Security Disclosures.

  • Fix issue where a query could fail to search all segments if digest reassignment was occurring at the same time as the query.

  • Fix issue where a node with no digest assignment could fail to delete local segment copies in some cases.

Humio 1.13.3

Security and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.13.3

Preview

2020-08-04

2020-08-26

1.12.0

No

Yes

JAR Checksum

Value

MD5

93a48eb23b149780fac8e065d28e3bc1

SHA1

6f78a25d48e79482c6e98cf2dc2125208d3c906f

SHA256

d526f5d0d1b9f1d1061b93e0a5c1c66d5ecd2a88cf732318d6f8fe8fcee9df30

SHA512

a7fed48de308a679b5907a485ac7dc54008d9dfee32a08d41c23df2f3bc2ff7f3184a0283cf211562eaf4a9b7cc926e70ef22243ba8e3d3ed463dc872b3662bd

Summary

Security and Bug Fix

Change Log

  • This release fixes a security issue. For more information see: Humio Security Disclosures.

  • Bug Fix: avoid forbidden access error on shared dashboard links by ensuring correct use of time stamps

Humio 1.13.2

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.13.2

Preview

2020-08-03

2020-08-26

1.12.0

No

Yes

JAR Checksum

Value

MD5

32b80ba726b370fc740ba7960d537ccc

SHA1

fc8a67b2fad623b0806405f9409b6e2d94d713a6

SHA256

fcdac4812ef43784c3dc575e8970ecdc2d45f954773867a2b43bde97c9176142

SHA512

4a0e86276d19da61b795bd937ecb0145bcfdb59a9678a5d1ed93045964db7b61d937ec69d1bd13bc79447ef74555f9de925bc416388b6cb742765191f79cb08e

Summary

Bug Fixes

Change Log

  • Bug Fix: all ingest methods now support the ALLOW_CHANGE_REPO_ON_EVENTS configuration parameter

  • Bug Fix: avoid saving invalid bucket storage configurations

  • Bug Fix: export to file no longer fails/timeouts on heavy sub queries

  • Bug Fix: joins will now propagate limit warnings from sub queries to the main query

  • Bug Fix: make sure join-subqueries gets canceled when the main query is canceled

  • Default groups added

Humio 1.13.1

Bug Fixes and Improved Search Speeds for Many-Core Systems

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.13.1

Preview

2020-07-03

2020-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

f097c9c95c06f12ec55c008b9963f9ee

SHA1

8acc122717d30f5a3333175a172e4c26a3c20569

SHA256

9dd7736569cc823182140ffd7ed91609cdafb97f99586d0d91def412a37bd548

SHA512

eaceff5d2ffc55c18f6175f519ecd0c97a684cb2a1d46c3e242513181bf29217331deb934eba45ba7d55f795a1cccd0ae25cf76b685dd484ed681a2f66791f01

Summary

Bug Fixes and Improved Search Speeds for Many-Core Systems

Change Log

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

  • Bug Fix: 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).

  • Bug Fix: Bucket storage in GCP could did not clean up all tmp files

Humio 1.13.0

Free Text Search, Load Balancing, & TLS

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.13.0

Preview

2020-06-24

2020-08-26

1.12.0

No

No

JAR Checksum

Value

MD5

c9dca247bec107fa41c6ec1fe5bb5d3b

SHA1

51e898057d10d80e6a50ab86ab5bedf71d348f5b

SHA256

b5c21c0028f1d61104821e5d4749b15cea7e208aa9bfb9307a9b10e077f6f7b6

SHA512

5b148d8d8fd8680fd61c642bda45f7dba2cb0aa21efeb2752b02a6467a7063036f1b31ea347816ecdcba676cf1d9d199e409620bd6b1acd2cc2fdeff78767375

Free Text Search

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

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 the Configuration reference pages and Cluster documentation.

TLS Support

TLS encrypts 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() reference page).

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 the Configuration reference pages and Cluster documentation.

Change Log

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

  • Humio can now balance and reuse existing queries internally in the cluster. See Configuration reference pages

  • Internal communication in a Humio installation can now be encrypted using TLS. See the TLS Configuration reference page.

  • Added support for WebIdentityTokenCredentialsProvider on AWS.

  • The data source for the ipLocation() query function is no longer shipped with humio but installed/updated separately.

  • Introduced a new ChangeViewOrRepositoryDescription permission for editing the description of a view or repository. This was previously tied to ConnectView and any user with that permission will now have the new permission as well.

Humio 1.12.7

Bug Fix and Additional Metrics

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.12.7

Stable

2020-09-17

2021-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

438fc3f94d9e252184cbeaee2dacc740

SHA1

08254ec21b51d6522a0336b92548943d9fe0b140

SHA256

814d522ef2aef4f3a81ab8380c5ad746ef9d13f302124bc0c13c64378ef4feec

SHA512

e2e936e1d20a6e60e312e995d1557085976531cfa2c50daa19cd0ce474ff398acdda3cf2431ab4a0aa33625ee45dc798685e6e485d282281f668c2c587bf69be

Summary

Bug Fix and Additional Metrics

Change Log

  • 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

Humio 1.12.6

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.12.6

Stable

2020-09-03

2021-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

43c5c6e2a7de76e73d63002c04f8693c

SHA1

dfff8f766cedca6a7b1888e2d060b07fba035b61

SHA256

3928f42354195c4217d60a86d4df70307477af81fa4ca2d87d29c921dbc1ae5a

SHA512

32e8e1b008b945545159b87d183ab1ef76d649a8a96ac92f54799446c345e205a1e13953f43a8feac264596ee69de7e10e57e2a532bb860bef062559c60442a6

Summary

Bug Fixes

Change Log

  • Improved handling of query restarts to avoid unnecessary restarts in some scenarios.

  • Remove restriction on length of group names from LDAP.

Humio 1.12.5

Security and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.12.5

Stable

2020-08-12

2021-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

99fc31c507d0a6193c0257b3a1a1e708

SHA1

d0c7fa652713473d04923d1c5921374144a38aed

SHA256

94c3f8cbb84dfe6870bdcfa4771f46a124ba8bca5d85332f0a0150a3e6f54a49

SHA512

1b25c775757af29f65597dbb3d5504637485a75f2fc5b29412ea646527aebee31b4f0b96f732c70e7ed9e0d4e1c48776c4c893398e3da3222c9ccce8d762676c

Summary

Security and Bug Fixes

Change Log

  • This release fixes a security issue. More information will follow when Humio customers have had time to upgrade. See Humio Security Disclosures.

  • Bug Fix: missing migration of non-default groups would result in alerts failing until the user backing the alert logs in again.

  • Bug Fix: 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.

Humio 1.12.4

Security Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.12.4

Stable

2020-08-05

2021-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

33fe0d36c64e58ff875496facf68e65a

SHA1

7122a470bf146e40ddce711349007dd1a4f7961c

SHA256

4cd4fa7b21fbdd14b095cb20e7d5d6af0c78bccc0bbc152c7417149db5d0d194

SHA512

879822ef357dbb1dcdd969ba053bd09cabaf42b4748495543b72b63f43f8c9c6b0feb25911446f07ae37468ec663e7b278c752dc441a52136762d429c18a7f5b

Summary

Security Fix

Change Log

Humio 1.12.3

Security Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.12.3

Stable

2020-08-04

2021-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

b6de082e67d662de761d5b79915152b8

SHA1

78cf6419a7a092e7d2a8200000ada4535f2f5b5c

SHA256

cec300a428f0f5998bbd13d56283fb54dbe47f1205d97115b23dfabf4f3dcbc7

SHA512

0704b189c70073e304ce115808441e6b44b6aa267df66fe9cac3998a80adc340fe5692829469c99dfceae3cb60e6bcc152ba7f77d509331d50d9621cfc7a1bfc

Summary

Security Fix

Change Log

Humio 1.12.2

Bug Fixes and Improved Search Speeds for Many-Core Systems

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.12.2

Stable

2020-07-03

2021-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

33890ac97e42a107f8f8618312029ca0

SHA1

0a097631134aa0078e0aea54f32cf58c0be8066b

SHA256

446acdcd64f3c33cdffd886e530201576e75c781184708da30af2dfc7b4bcd14

SHA512

1931cf27039d17b5aeb4c6fe4022b88a263d41464cb304ba4d30dd936a9cb6202af36dd6c97a5c3e183dd60042def96538e62de3ee86a3204e1108b60a9d9852

Summary

Bug Fixes and Improved Search Speeds for Many-Core Systems

Change Log

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

  • Bug Fix: 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).

  • Bug Fix: Bucket storage in GCP could did not clean up all tmp files

Humio 1.12.1

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.12.1

Stable

2020-06-24

2021-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

d6a8a2fa268c92a46024af8e8ba7b27a

SHA1

20660ae440fdcaf818c3919f4b3d467f71da37ce

SHA256

16c96f36554425939b78c5df889cc689368f598a3b14ce336e3a28ad1dc1abbd

SHA512

e518b4778b7c6c50861fbaa25a2d95fc3f639e1dfcbb526c0a7727aefe650177d6975ee50caa51d8ccfd636eacdb6fba2ee3cd3a7d1f150eae09147a06c3e2f4

Summary

Bug Fixes: Safari Freeze, SAML, Bucket Storage Clean-Up, Regex and Field-Aliasing

Change Log

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

Humio 1.12.0

Export to Bucket, findTimestamp(), selfjoin(), Emergency User Sub-System

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.12.0

Stable

2020-06-09

2021-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

73a3fc77b4b603df3d492a3c8f740cb2

SHA1

0e70382492ca4a59b3139fad1ee22344f0b257e8

SHA256

dbf34321f44a4e60726a10d67d1a73db7915c94d7e786ad332d5832f34a81c81

SHA512

4f2840a8b552395735006481107c55567dbbd865025fb0fbfdf5d590938eafb541a780b4065a4ed4419b12e7e894c9a768902ea8f5c21ed7debc3368e6a7e528

Summary

Export to Bucket, findTimestamp(), selfjoin(), Emergency User Sub-System This release promotes the 1.11 releases from preview to stable. To see more details go through the individual 1.11.x release notes (links in the changelog).

SelfJoin() Query Function

The 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

The 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 findTimestamp() 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 Cluster Management - Storage.

Emergency User Sub-System

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

Elastic Bulk API Change

Fluent Bit users might need to change the Fluent Bit configuration. To ensure compatibility 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

Change Log

  • Major changes: (see 1.11.0 release notes)

  • Other changes: (see 1.11.1 release notes)

Humio 1.11.1

Bug Fixes and Memory Optimizations

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.11.1

Preview

2020-05-28

2020-06-09

1.10.0

No

No

JAR Checksum

Value

MD5

5cb65fb38f5882c86e170fc19932bc2c

SHA1

d8639e7541b0de1b2ef5c3909f88d864b18faf63

SHA256

63e5264b32fc02774e1f4dd3a7dbd1ddbb124158e915d5df219b355faaf278d0

SHA512

7c7832559a5a1f43f87d7cf12bbb63b5a7ea6c0922a4c917b652caba08fe77375b49517f2675f819f9fdf0519e90310e572bee1cee8e72bade531605ddd14942

Summary

Bug Fixes and Memory Optimizations

Elastic Bulk API Change

Fluent Bit users might need to change the Fluent Bit configuration. To ensure compatibility 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

Change Log

  • Elastic Bulk API change

  • Several improvements to memory handling

  • Several improvements to query error handling

  • Dashboard widgets now display an error if data is not compatible with the widget

Humio 1.11.0

Export to Bucket, findTimestamp(), selfjoin(), Emergency User Sub-System

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.11.0

Preview

2020-05-19

2020-06-09

1.10.0

Yes

Yes

JAR Checksum

Value

MD5

70406b0710c9c999ec5293357e03b05a

SHA1

f50294f5d0267d582d7207f7df33e16eee2744af

SHA256

c1a79a8f1ca41e14158992ba5dfff0a05ce39292b5ed5bfa8d5507973d054fdb

SHA512

f0f210d24aac849457839588202d662294911bf095e0f5a791093c61c435969b300f0a303d457a0e8cdbb13d742a81b3d09c6e11fad28f927ee9782153d05fc8

Summary

Export to Bucket, findTimestamp(), selfjoin(), Emergency User Sub-System

SelfJoin() Query Function

The 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

The 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(). See the findTimestamp() reference page 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 Bucket Storage documentation.

Emergency User Sub-System

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

Change Log

Humio 1.10.9

Security Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.9

Stable

2020-08-05

2021-04-27

1.10.0

No

No

JAR Checksum

Value

MD5

a9fc2ea12707d4b1c581151e0026f1b9

SHA1

d4f374af166c4138a1c5ef715ae7e6299fc4a51f

SHA256

b2f676c80a61a444b799295f6ca5e3284209aa1d4611182503e78c4b4ca64623

SHA512

146baf45e4181694b327849665771cc859a4757e32e0b982990da80171f144b12a01a47fcba2bdb728a4c10fede2a1ff0ff25c7b5bbf8be3a80caf6a982af9e2

Summary

Security Fix

Change Log

Humio 1.10.8

Security Fix

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.8

Stable

2020-08-04

2021-04-27

1.10.0

No

No

JAR Checksum

Value

MD5

ebc006bf64fc1f310f6c29a8854da2f7

SHA1

1461cd0e70f1ddb30b316cf9d0010a0840a11241

SHA256

7432902332b1a87f6899870e3bd47a18077a04980a63427896a0eac204300e2d

SHA512

c63714a10b7d06a869ab47bf4a84c31e88656f7e78c14281fdc9b78dc6139fc94b08f02dfd810352844bc0662838790227c18877a518b11cf67ad39c12e7ca0b

Summary

Security Fix

Change Log

Humio 1.10.7

Bug Fixes and Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.7

Stable

2020-07-03

2021-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

36d8bcdffeb41720006c2d07ae38669a

SHA1

83fda60fe22239101cf1e81fd41bec04071f5ae5

SHA256

4aa66055218f4f4d7ad65a7476e7f8b6ddd57f8187472e80e2bef1506aa3484f

SHA512

c34ae669043a70d4ebc760365bcb82477fbbbaadb0f3229083732b1549e646444ffbb42d2e1285b9f0ca8e1213e9fef42a14d587b66ba3adf883fedc8ba09c72

Summary

Bug Fixes and Improved Search Speeds for Many-Core Systems

Change Log

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

  • Bug Fix: 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).

  • Bug Fix: Bucket storage in GCP could did not clean up all tmp files

Humio 1.10.6

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.6

Stable

2020-06-24

2021-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

ff8b12b453b9e600ac6a5f917a799f8b

SHA1

c6bf4610bc284c7838d92e0c110461349511afeb

SHA256

04503cb6691db596b5237e65e9f639013caab3010c753796392d1d59a9e06413

SHA512

d6a8c3c898c4d93ac8dd564ec0394a5d5db4d06711bd498e38ce58a2b026bd8d6e1f2b664e30de92eb60afb7b452b34b4c17e0e6370331afdcc2030407f74674

Summary

Bug Fixes: Safari Freeze, SAML and Bucket Storage Clean-Up

Change Log

  • 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

Humio 1.10.5

Bug Fixes - humio-search-all and Query Timeouts

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.5

Stable

2020-06-09

2021-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

e26c8dcab38cf8ae70146af0c20de708

SHA1

38b4cd3f334845ebdc91d02b9f24cab628290805

SHA256

3234edd2ec5a01b67c07f8d87d57a967fb37a2e6b29a34317545a37796650a83

SHA512

281bfc2da26ef9f14c123c695943149499f43f7c67e20ff2150420bed7e745a7f6e2483b6073a366e453589f657a3717031071e6374b124657cb5b8c77542255

Summary

Bug Fixes: humio-search-all and Query Timeouts

Change Log

  • 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

Humio 1.10.4

Bug Fixes for Long-Running Queries

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.4

Stable

2020-05-29

2021-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

8fd134e50a88aa016037aff59bca7f70

SHA1

184f4c0d1b477eef81357e7efcbe2cafb2920fef

SHA256

3398a9e1cc4f3e2f70e952f0c6481fe3c31f447e68d1589904ee26e614cb9a30

SHA512

fab832e462afeaed828a55bc7a6b3d637317ace396ff0751fbf1813d4f0ce01f8cf11e4d3ed6cb6eda898e5521739de766b8ade609fcc98ca774a5d079f76509

Summary

Bug Fixes for Long-Running Queries

Change Log

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

Humio 1.10.3

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.3

Stable

2020-05-20

2021-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

b534f6427bbc73720246c88df097d962

SHA1

4fd7b762eefcd241c14a0dcc74642ab5f96066a3

SHA256

03fbcdfffbd4e730ab6ac97ce1e0c88dfa2b2c544de01767647ac9fc1a606c97

SHA512

cc1cd46e9e38cf9215e82da0246ba7cfd27b50becbe9b9a17c0c3c88427649b93339b6cffc6780bc241c2bd152d8f781b7f6d421dcd641def3cef66a8290841f

Summary

Bug Fixes

Change Log

  • Bug Fix: 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.

Humio 1.10.2

Optimizations, Improved Humio Health Insights & Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.2

Stable

2020-05-19

2021-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

34618e12957e3394f06dd86d7b283bb7

SHA1

b9e75509bbec4093019a475cc3660c28295bd1c4

SHA256

c4868bd4067833744cceaa44dac29a5af2b450d112c34f3dfd8d46906cf115f8

SHA512

5789415e8c6d748c7a724f702606e96ba48f7595517787d76b7e7581766e23c1de7af1eec5b66cc22d73241d61fb4866f3b12a88d73ee6ca453c8bab255fb331

Summary

Optimizations, Improved Humio Health Insights and Bug Fixes

Change Log

  • Bug Fix: A couple of memory leaks have been found and fixed.

  • Bug Fix: Autocreate users on login when synchronizing groups with external provider.

  • Bug Fix: 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.

Humio 1.10.1

Optimizations, Improved Humio Health Insights & Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.1

Stable

2020-05-04

2021-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

abca8999c6542ff0a4d60b897eb5acf3

SHA1

176e416e63d13200dee21a509fa9ae2401b8a0ca

SHA256

8a1a419c3bd664a006918ee0b957ed2f1fbdea20dda2ea8114ab4db7b039425a

SHA512

93a8d7a1c86e646f9e7fb26f8feeb05f5bf22774cd69e2b0ac113c48f7736242554ddeb0065ff19ab9723546aa75a064af4e7f7779a8d2efa91651aa7f61f630

Summary

Optimizations, Improved Humio Health Insights and Bug Fixes

Change Log

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

Humio 1.10.0

RBAC, Health Check API, Kafka, Vega

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.10.0

Stable

2020-04-27

2021-04-27

1.8.5

Yes

Yes

JAR Checksum

Value

MD5

4f1ed6fa41cb1f96c7a68b4242ff7280

SHA1

5e334e72d7a2e59ece26062007fd3baa6361cfb6

SHA256

36245d9e2d93650455dd2e69f7ad4b48f625c482334d9742674a9e4edfed17d4

SHA512

fce509692d77f483a919e5e5abbe82b5c58edbeec05afd25add03cb5500603e741ef66fdb886b85bfe3db535d3ce41d43e57bbb31e72c5cd4517bfb7321c941e

Summary

UI for Role Based Access Control (RBAC), Health Check API, Kafka Version Update, Vega Charts. This release promotes the 1.9 releases from preview to stable. This release is identical to 1.9.3 apart from the version string. To see more details go through the individual 1.9.x release notes (links in the changelog).

Security Fixes

This release fixes a number of security issues. For more information see: Humio Security Disclosures.

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

humio
# 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 styling 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

Change Log

  • Major changes: (see 1.9.0 release notes)

  • Other changes: (see 1.9.1. 1.9.2, and 1.9.3 release notes)

Humio 1.9.3

Security Fixes, Bug Fixes, and timechart() Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.9.3

Preview

2020-04-22

2020-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

e2a84e14721946391ec9dddf66412723

SHA1

4b439142bf46d49c9e1b9c9685a2beacb921ef18

SHA256

646c3069015b1516dae2ef577d827a30d0deb62a393360fead05074a37edc670

SHA512

bf673036d37ec539d1abeb04b9388e87f8c6ddfc781602d67bb7e28a5beda6195b827bba61bc9f769836f4a764330d93a33ae4788700758ca23cd7f8ecb88ae4

Summary

Security Fixes, Bug Fixes, and timechart() Improvements

Security Fixes

A few security vulnerabilities have been discovered as part of a proactive penetration test. None are known to have been exploited. More information will be forthcoming.

Deal with Missing Data Points in Timecharts

This release improves the handling of missing data points in time charts. Previously you could either interpolate missing data points based on the surrounding data, or leave gaps in the charts. With the introduction of the new charts in 1.9.0 the gaps became more apparent than previously, and we have added new options to deal with missing data points. These replace the previous option “Allow Gaps”, with four new options:

  • Do Nothing - This will leave gaps in your data

  • Linear Interpolation - Impute values using linear interpolation based on the nearest known data points.

  • Replace by Mean Value - Replace missing values with the mean value of the series.

  • Replace by Zero - Replace missing values with zeros.

New Line Interpolation Options

The release also introduces new options for line interpolation.

  • Monotone

  • Natural

  • Cardinal

  • Catmull-Rom

  • Bundle

The latter three are impacted by the ‘tension’ setting in the timechart Style editor.

Change Log

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

  • New query function fieldstats().

  • More efficient “collect” function implementation.

  • Allow more concurrent processing to take place in “export” query processing.

  • Styling improvements in the “Style” panel for widgets.

  • New Time Chart interpolation options.

  • New options for dealing with missing data in Time Charts.

  • Improves responsiveness of the recent queries dropdown, and limits the number of stored recent queries to 100 per user per repository.

  • Allow dots in tagged field names.

  • If at startup the global-snapshot.json file is missing, then try loading the “.1” backup copy.

  • Bug fix: The segment queue length metric was not correct when segments got fetched from bucket storage by a query.

  • Bug fix: the query metric only measured time for streaming queries, now it includes non-streaming as well.

  • Bug fix: api-explorer not working due to CSP inline script.

  • Improve disk space monitoring when using bucket storage.

Humio 1.9.2

Security and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.9.2

Preview

2020-03-25

2020-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

f457859662db92bd00c282aa3daa1393

SHA1

a7d40e09f6a2e09a90fd2e3a2fc53618ac96a57f

SHA256

b33d955d51ddbc2b067b4539f1a447f4e6268e3944ead92dd7e03e56e754d95f

SHA512

e24b7f6b31c42b6e2b138eaa23bc6a1760dfff18b53bed6c16d1dcca79c31aabf01bbe913eee7cbe3629f410491754af77415bee14a81220099a7c4c8d1bb316

Summary

Security Fix and Bug Fixes

Change Log

  • Added API to the list and deleted missing segments from global.

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

Humio 1.9.1

Security and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.9.1

Preview

2020-03-23

2020-04-27

1.8.5

No

No

JAR Checksum

Value

MD5

a3fb1c5f2be309f2fca630f151522bc9

SHA1

c9bee3ec060d2b0cc75fba8fd085769c66224dcb

SHA256

4ae4ed141342c8daa193d61351919832bf63f07b02b103c2d97eac18888b61e7

SHA512

6e43adfff7e5bf9a6078060ec2660fb23e799b97b45b3f895eacf95bf344fc4b5acef9562018db133460ff97f8bd7dd883d1c9284b6e34cd1462a257597e37b9

Summary

Security Fix and Bug Fixes

Change Log

  • This is a critical update. Self-hosted systems with access for non-trusted users should upgrade immediately. We will follow up with more details when this update has been rolled out.

  • Bug fix: the health-check failed-http-status-check would get stuff in warn state, this has now been fixed

Humio 1.9.0

RBAC, Health Check API, Kafka, Vega

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.9.0

Preview

2020-03-12

2020-04-27

1.8.5

Yes

Yes

JAR Checksum

Value

MD5

81a34e3166d583b2a3479b7a4d82f64c

SHA1

3f6646fc133c955d2c51977081da118f5b9b3fac

SHA256

f0877cc533ed58c3ca9630989b6848c79ba69f5217ee2dc6278909d4e586d076

SHA512

e932eacb43d25cd10a95ad59ce07a0e7b68e7859e6b5ccf1d463cb9a23ddbf8cd0d186776a538a59ab3dcd57f1048f8dc9e6fe020ca907334f195ea22f3acdf8

Summary

UI for Role Based Access Control (RBAC), Health Check API, Kafka Version Update, Vega Charts

Change Log

## Role Based Access Control

Role Based Access Control (RBAC) through the UI is now the only permission model in Humio. Please see the Authorization documentation for more information.

## 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. Zookeeper 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=*

## Query Function updates

  • New caseSensitive option added to the parseTimestamp query function.

  • Queries involving join can now be with ‘used export to file’ and the /query HTTP endpoint.

  • New selectLast function, which is like select but aggregate.

  • Improved (reduced) memory consumption for live groupby, and for groupby involving many distinct keys.

## Health Check APIs

The overall health of a Humio system is determined by a set of individual health checks. For more information about individual checks see the Health Check page and the Health Check API page.

## IPFIX

Humio’s NetFlow support has been extended to also support IPFIX. See Humio’s documentation for NetFlow.

## Vega + chart series colors

This version replaces our chart library with Vega. The goal is to create a better, customizable, and more interactive charting experience in Humio. This first iteration is largely just a feature replacement for the existing functionality, with a few exceptions

### Support for controlling color and title in widgets

Each chart type now supports assigning colors to specific series. This will allow you to, for instance, assign red to errors and green to non-errors.

You can find the series configuration controls in the Style tab of the Search page.

### Control widget styling directly from dashboards

Now, you can click Edit Styling in the widget menu and modify styling directly from the dashboard view.

### Time Chart series roll-up

To prevent the charts from getting cluttered, you can adjust the maximum number of series that should be shown in the chart. Any series that are not part of the top-most series will be summed together and added to a new series called Other.

### Interpolation types

Linear interpolation is now the default, and we have added a new type of interpolation: Basis.

### Bar Chart styling support

You can now style your bar charts to control things like label position and colors.

### Pie Chart styling support

You can now style your pie charts, and they will default to having a center radius (actually making them donuts!).

### Disabling Vega

Since charts are such a central feature, we allow disabling the new implementation of widgets if you are experiencing issues with them. You can disable Vega charts globally using the ENABLE_VEGA_CHARTS=false flag.

Humio 1.8.9

Security Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.9

Stable

2020-03-25

2021-01-26

1.6.10

No

No

JAR Checksum

Value

MD5

f366932ccffe66883cbf84fc1ab7c9e0

SHA1

8a37d7255ec24d2c3fe85b7fcdcf5fe9020746d9

SHA256

fc42241e1f7dd2f928ddcf145eee85906764c004b765bf3509a65a33817a0f3a

SHA512

9c5d08fd844f1058b036c2e588120ac70c3d2abe5e98eddedbdb85f6674d57acf4f0425fc66d8b175953f98c312ed44a5943333083a4a6c45ecb4e7014ce2027

Summary

Security Fixes

Change Log

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

Humio 1.8.8

Security Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.8

Stable

2020-03-23

2021-01-26

1.6.10

No

No

JAR Checksum

Value

MD5

0c0359bdfe15cb2f8f14487038c8043e

SHA1

994919268e463ed643ff4977d9f131873833717b

SHA256

3918516569ff4a03f9ac1131658b8ac4046186f5f4d17333e0ec555227136f63

SHA512

c12b2e7630d97b618a7552290b942b443017005e607fa819459b0979b0e05e553b0bdd61fc5d508ce766247269e711ad370df7acb755b4928b54f7e25790ef5d

Summary

Security Fixes

Change Log

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

Humio 1.8.7

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.7

Stable

2020-03-12

2021-01-26

1.6.10

No

No

JAR Checksum

Value

MD5

7c6181f950bb99ca50c5b444dc072cd8

SHA1

0cf020232fb2b5621c288dded8d3d9d3626db521

SHA256

8c003212b861957529332ad8d62facf2796bdbe58a66107559eb691c44762dea

SHA512

c8e7acdd3812408fa87ad6afa29573c09a8b9ec7518b03a6f41e7caa8205f4e172f78fe7f0d146020cc68eb80b0519d1e11571675b340639e0a73aa666e0cf8f

Summary

Bug Fixes

Change Log

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

Humio 1.8.6

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.6

Stable

2020-03-09

2021-01-26

1.6.10

No

No

JAR Checksum

Value

MD5

59a11140391a8f7a47de89bb2c3cf932

SHA1

05cf1d4355af997b5591f1b77e517d0f703cc5db

SHA256

cfc9736d19dac1a9b2c1f3ce082bd28e900178b4aeb781d7aef350557778a215

SHA512

47dbe78aba22795cbdbea741099bb5abe2c03d491479a8a0795793c6605cbbcad2b62eca3953e87c7635cafe57f496341887fff1704725e9a2d2db4071865d6a

Summary

Bug Fixes

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

Change Log

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

Humio 1.8.5

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.5

Stable

2020-02-28

2021-01-26

1.6.10

No

No

JAR Checksum

Value

MD5

d9e4b78b03e7c5f53eba4bc0c75f865c

SHA1

56725db4c01ea082769143361c978d17cffb931e

SHA256

ec3fc0e337a01b5e772176b708620bbeca16a871d7a3fced6451704546b960be

SHA512

6ec7cfca8f64bd72e372540a0b375581e6b115e5e84108bdbd9f2606619887f940d8d0f213eba0011381a1a835b6ad3793ffe74741bd1fcd5571d11026149898

Summary

Bug Fixes

Change Log

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

Humio 1.8.4

UI Scroll Bug Fix for Chrome 80

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.4

Stable

2020-02-19

2021-01-26

1.6.10

No

No

JAR Checksum

Value

MD5

628055e8a489f8da436795da3b74c83b

SHA1

693c732a14ab780fd2160194bb909599ef016a0f

SHA256

cb784f6287b75195d624013005b2ac6db3dfc1d3d56ed777efaf6502cb00a629

SHA512

9a30326b010e8e09288f9112d34017fcb2d3a7d26c9f6bf85804abb2977dc99784d32146b2236989230360e0b5525c92b46282bc768f3f42787cbcd5b1af4246

Summary

UI Scroll Bug Fix for Chrome 80 (again). 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.

Change Log

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

Humio 1.8.3

UI Scroll Bug Fix for Chrome 80

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.3

Stable

2020-02-13

2021-01-26

1.6.10

No

No

JAR Checksum

Value

MD5

f975edf282bf83febc974c154906611c

SHA1

a1e49cd77ffeae0e95daf3380d3d4138ee6b4b04

SHA256

28dc5287957bdfcb414f0f1ecd71ea8721ff8b87e713d6f02b26922c5e44f97b

SHA512

a6f251ab388038d54e40efec2e51e967c6c276f320a615f95bcbc9f139134ba25182430208d0917496bb2228c1608f296f979a2d24e10b32ede3fe301c29d364

Summary

UI Scroll Bug Fix for Chrome 80. 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.

Change Log

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

Humio 1.8.2

Bug Fixes

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.2

Stable

2020-02-10

2021-01-26

1.6.10

No

Yes

JAR Checksum

Value

MD5

b3b553543c7db54d05b721550a4c9b3d

SHA1

7a24873c6485caaf99abfed3bac79d982056793e

SHA256

995787f60bcf744d6447b53282f48d547a89962202a81f3f4ba65dbf0dbe6398

SHA512

1814b6a443381fd0191f93bfdf49fa6c57b4bbf163500b56f742673780384a44d8a603121d5b0417b593ad24a4752edd82f8a3c965b56bfdb5d58de8f1014351

Summary

Bug Fixes

This is a bug fix release.

Change Log

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

Humio 1.8.1

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.1

Stable

2020-02-03

2021-01-26

1.6.10

No

Yes

JAR Checksum

Value

MD5

e99a4e6eb8ae5174416f3ba2ac6f975a

SHA1

c0ed5c06b6fc6d9f2bb6bc2c7d4afeb4aeabcd01

SHA256

156eadb8a285e688aecde7040505e6266407ab5ce6c58826ef9d6d12299fb5db

SHA512

86acc3eef2c2817ba7e5f83b030319bb70a63ca90568fd1a949210177653951cfa76687c22d23518626fdcc08719b9ff67c66c918842b0010860c56696b171a5

Summary

Bug Fixes

This is a bug fix release.

Change Log

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

Humio 1.8.0

Joins, Bucket Storage Backend, Query Quotas, UI Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.8.0

Stable

2020-01-27

2021-01-26

1.6.10

No

Yes

JAR Checksum

Value

MD5

323f7c8a332086ce7f5f0d9796d346f7

SHA1

4423ccb2afcfcc7f83fe9802ee494abe4085f314

SHA256

318d70019a0678d65b721dccff6643818bd151497d5b873a59d9e9cc95ad4f77

SHA512

a196b0f8cde842b395bf6e0401410ebc61d1052507d07aa37b78214acc0ba460cd0f926cb54c5be5530d8eb6d6e80998845bb2f0b1f148d683a3685c67c868e8

Summary

Joins, Bucket Storage Backend, Query Quotas, UI Improvements. This release promotes the 1.7 releases from preview to stable. The main new additions are:

  • Join search function

  • the ability to use See Bucket Storage providers such as S3 and Google Cloud Storage for data storage, and

  • Query Quotas - putting limits on the amount of resources a given user can spend. Besides those, there are a number of UI improvements, back-end improvements, and Bug Fixes.

To see more details go through the individual 1.7.x release notes (links in the changelog). This release is identical to 1.7.4 apart from the version string.

Change Log

  • Major changes: (see 1.7.0 release notes)

  • Other changes: (see 1.7.1, 1.7.2, 1.7.3, and 1.7.4 release notes)

Humio 1.7.4

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.7.4

Preview

2020-01-27

2020-01-27

1.6.10

No

No

JAR Checksum

Value

MD5

cdfb4241fdc8daa44f9f2e54cca1355e

SHA1

b5e01c98c21e4ffcbc115b8585ab28ec90bc79f7

SHA256

63a8945e903755bcfc430d1b404f3a64558e8b7e26728f4a2c10ca22f6c67347

SHA512

dedbf948de640e141ab246cdb431dbbcbfd190b1947dde2fe7896c0a3ad904e60ee7d2aaaffcf6efb63e8a65919a8554fab1fa5ea111b5ab2111b195d5d48fd3

Summary

Bug Fixes

Change Log

  • Add Chromium to the list of compatible browsers

  • Allow webhook notifiers to optionally not validate certificates.

  • Bug fix: join now accepts absolute timestamps in millis in start and end parameters.

  • Bug fix: Stabilized sync of uploaded files within a cluster in combination with bucket storage.

  • Bug fix: Allows “Force remove” of a node from a cluster.

Humio 1.7.3

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.7.3

Preview

2020-01-17

2020-01-27

1.6.10

No

No

JAR Checksum

Value

MD5

4265deddaccfa78f648a6426faa28ce6

SHA1

abc76135b365f4bb09793af9749a03b157b56176

SHA256

0becd94c687e07aa6a0ce116a96b2b6e7bace87e77e6fd7a4c01a5e837050c8f

SHA512

2b5606a0ae94e95d9c8271628b2c3fc4c56c9a74f27c9735e334957fb7baf8d5de5cc7cd50f8f2fb5ee3cea6e3323bfb645efb4bc083e3f65f4a3803c6811a8f

Summary

Bug Fixes

Change Log

  • New log output option for the LOG4J_CONFIGURATION configuration now allows the built-in: log4j2-stdout-json.xml to get the log in NDJSON format, one line for each event on stdout.

  • ERROR logs get output to stderr instead of stdout to avoid breaking the potential stdout format.

  • top() function allows limit up to 20,000 by default now. Used to be 1,000.

Humio 1.7.2

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.7.2

Preview

2020-01-16

2020-01-27

1.6.10

No

No

JAR Checksum

Value

MD5

b523d1cdac2d03b7f215379080eb9053

SHA1

3846dfc31446f7788c1ac6b86821073397b0d462

SHA256

7bed62c85e26ff73feb19554b4296d0d9590c6d65f45e9685b9b5ffb356963a3

SHA512

54192cfc366ba7b3626ae3b6e0e5fb47bdc8dffb828a68198e9fa1f1800b4c2763abe765c4da34533b5beb1906b79dc3e40aa1234be684e34c1b266ae348070b

Summary

Bug Fixes

Change Log

  • Change: When the system starts with no users at all, the first user to log get root privileges inside the system.

  • The “query monitor” and “query quota” new share the definition of “cost points”. The definition has changed in such a way that quotas saved by version up to 1.7.1 and earlier are disregarded by this (and later) versions.

  • New config: LIVEQUERY_STALE_CANCEL_TRIGGER_DELAY_MS and LIVEQUERY_STALE_CANCEL_COST_PERCENTAGE controls discard of live queries that have not been polled by a client for a while when the system experiences digest latency of more than the delay.

  • New config: LIVEQUERY_CANCEL_TRIGGER_DELAY_MS and LIVEQUERY_CANCEL_COST_PERCENTAGE controls canceling of live queries that have been consuming the most cost for the previous 30s when the system experiences digest latency of more than the delay. New metrics: livequeries-canceled-due-to-digest-delay`, `livequeries-rate-canceled-due-to-digest-delay and livequeries-rate

  • New config: USING_EPHEMERAL_DISKS allows running a cluster on disks that may be lost when the system restarts by assuming that only copies in Bucket Storage and the events in Kafka are preserved across restarts. If the filesystem remains during restart this is also okay in this mode and more efficient then fetching the files from the bucket.

  • New config: LOG4J_CONFIGURATION allows a custom log4j file. Or set to one of the built-in: log4j2-stdout.xml to get the log in plain text dumped on stdout, or log4j2-stdout-json.xml to get the log in NDJSON format, one line for each event on stdout.

  • New Utility inside the jar. Usage java -cp humio.jar com.humio.main.DecryptAESBucketStorageFile <secret string> <encrypted file> <decrypted file>. Allows decrypting a file that was uploaded using bucket storage outside the system.

  • Bug fix: The Zookeeper status page now shows a warning when the commands it needs for the status page to work are not whitelisted on the ZK server.

  • Bug fix: Restart of queries using lookup/match/cidr when the uploaded file changes only worked for top-level functions, not when nested inside another function.

  • Bug fix: Query of segments only present in a bucket now works even if disabling further uploads to bucket storage.

  • Bug fix: Bucket storage, GCP variant: Remove temporary files after download from GCP. Previous versions left a copy in the tmp dir.

  • Bug fix: Top(x, sum=y) now also support non-integer values of y (even though the internal state is still an integer value)

  • Bug fix: #repo=* never matched but should always match.

  • Bug fix: Retention could in fail to delete obsolete files in certain cases.

  • Bucket storage: Support download after switching provider from S3 to GCP or vice versa.

  • Bucket storage: Continue cleaning the old buckets after switching provider from S3 to GCP or vice versa.

  • Bucket storage: Also keep copies of the “metadata files” that you use for lookup and match functions in the bucket and restore from there when needed.

Humio 1.7.1

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.7.1

Preview

2020-01-06

2020-01-27

1.6.10

No

Yes

JAR Checksum

Value

MD5

df8268ca40d896676a0d771e40e84766

SHA1

f2826fed2741cc74128a07f5f67c2bed498d58bc

SHA256

6f29f7d3abb1df8547cc0be5470ec714469febfd2c8553ed58555e5936b27fbb

SHA512

14529ec3496dcafee383a2d6ef85d0862a8071f144e9b0ac59bd59f3b9742a8d1e46092f16e0db32e0ab071bdd2235754f319c4fc95007d470c34bb304c52ce9

Summary

Bug Fixes and Removal of Limitations

Change Log

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

  • Allow explicit auto as argument to the span parameter in bucket and timechart. This makes it easier to set span from a macro argument.

  • Remove 64 K restriction on individual fields to be parsed by parsers.

  • Bug fix: Reuse of live dashboard queries on the humio-search-all repository did not work correctly. As an effect the number of live queries could keep increasing.

  • Bug fix: Saved Queries/macros was not expanded when checking if a live dashboard query could reuse an existing query.

  • Bug fix: The Postmark integration was always assuming a humio.com from address. This has been fixed by introducing a new POSTMARK_FROM configuration parameter.

Humio 1.7.0

Join, Bucket Storage Backend, Query Quotas, UI Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.7.0

Preview

2019-12-17

2020-01-27

1.6.10

No

Yes

JAR Checksum

Value

MD5

949b46169cff1182c3da25c6f7f641f3

SHA1

9b9187c045ee4a4a8051ed233b7a8fdf056f514d

SHA256

aa53e3998b390863edb435a4658b5c51551d54c68f1b1983886063e297cd8cbc

SHA512

f3766baf64dbf62450970207cafabd65588a660cebceb8f447dd8d8d6baba8f5e26ac69e4873d8170a84c011264a5f16247d8beed28604e3fb91073af8435ba2

Summary

Join, Bucket Storage Backend, Query Quotas, UI Improvements

Joins

Humio now supports joins in the query language; the functionality is largely similar to what could previously be done by running a query, exporting it as a .csv, uploading said .csv file, and then using the match() function to filter/amend a query result. See Join search function.

Bucket Storage

Humio now supports storing segment files on Amazon S3 (and Google cloud storage) and compatible services to allow keeping more segment files than the local disks have room for and managing the local disk as a cache of these files. See Bucket Storage.

New Stable/Preview Release Versioning

Stable release will have an even Minor version. If Minor is an odd number (like in this release), it is a preview release. Critical fixes will be back ported to the most recent stable release.

Dashboard Improvements

To make it easier to integrate with external systems Humio dashboards, can now be passed URL parameters to set the dashboard’s global time interval. By passing query parameters ?time=<unix ms timestamp>&window=5m the dashboard will be opened with a 10m time window (5m before and after the the origin specified by time). The feature is not available for shared dashboards - since they do not support changing time intervals.

You can now also disable shared dashboards completely using the SHARED_DASHBOARDS_ENABLED=false configuration setting.

See the changelog for a more complete list of changes.

Change Log

  • Upgrading: After installing this version, it is not possible to roll back to a version lower than 1.6.10. Be on version 1.6.10 before upgrading to this version.

  • Top Feature: Bucket Storage with support for S3 and Google cloud storage, see See Bucket Storage.

  • Top Feature: Joins allowing subqueries and joining data from multiple repositories, see Join.

  • Top Feature: Query errors will now be highlighted as-you-type in on the search page.

  • Top Feature: The “Queries” page has been replaced with a dropdown on the Search page, that allows searching saved and recent queries.

  • Top Feature: Query quotas allowing limiting how many resources users can use when searching, see Query Quotas

  • UI: Improved Query Monitor in the administration section, making it much easier to find expensive queries. See Query Monitor

  • UI: Queries page removed, and delete and edit saved query functionality moved into “Queries” dropdown on search page.

  • UI: Add support for loading a specific time window when launching a dashboard, by setting time= and window= in the URL.

  • UI: Improve word-wrap and allow columns in the event list to be marked as ‘autosize’. Autosizing columns will adapt to the screen size when word-wrap is enabled.

  • UI: Word-wrap and event list orientation is now sticky in a session, meaning revisiting the search page will keep the previous selected options.

  • UI: Allow disabling automatically searching when entering a repository search page, on a per-repo basis.

  • UI: The time selector on dashboards now allow panning and zooming - like the one on the search page.

  • UI: Bug Fix - Don’t show “unexpected error” screen when Auth Token expires.

  • UI: Bug Fix - Ensure counts of fields and value occurrences on the event list are reliable.

  • Function: New function json:prettyPrint()

  • Function: New function xml:prettyPrint()

  • Function: New function callFunction, allows you to call a Humio function by name. This is useful if you for instance want a dashboard where you can control what statistics your widgets show based on a parameter, e.g. timechart(function=callFunction(?statistic, field=response_time))

  • Function: The function top has a new max=field argument, that can be used to make it work as a more efficient alias a groupby/sort combination, like top(field, max=value, limit=5) is equivalent (and much faster than) groupby(field, function=max(value)) | sort(limit=5).

  • Function: The implementation of the percentile function has been updated to be more precise (and faster).

  • Config: COMPRESSION_TYPE=high is now the default compression type. Clusters running with default configuration, will change to high compression unless the configuration COMPRESSION_TYPE=fast is set.

  • Config: Add SHARED_DASHBOARDS_ENABLED configuration setting which allows disabling access to the shared dashboards feature - if e.g. your organization has strict security policies.

  • Config: Autosharding can now bet set “sticky” which means fixed as set by user on a specific (input) datasource. The API also allows listing all autosharding rules, both system-manages and sticky.

  • New stable/preview release versioning scheme. See description.

  • Use case-insensitive comparison of usernames (historically an email address) when logging into Humio.

  • Java 13 is the recommended Java version. Docker images are now running Java 13.

Humio 1.6.11

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.11

Stable

2020-01-06

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

95b8814ef3035ec68887dd3605e10b1f

SHA1

42c2fbff389d6e75a05450abd326b3dd7da71bce

SHA256

fddbe1edb8b7501d277550e3a044f97d3448de6ccd0c3e02390d239841d3be2e

SHA512

8238028be9c1fb9ce1c027b7fcb21d4cea6b1db4e984d2aaf951c6e3a1ecf961285ce6d4ff41a373abe7c8a94f3d3cd7eca80284a126efa5e4bf90903a38e822

Summary

Handle Large Global Snapshot File

Change Log

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

Humio 1.6.10

Bug Fixes and LDAP Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.10

Stable

2019-12-12

2020-08-21

1.5.19

No

Yes

JAR Checksum

Value

MD5

c8cfd22a5be0456f5905247b6f2bab3b

SHA1

4c4b734217c5ac90bd9be5f6e2f34c4e182f8fa6

SHA256

2a2529e2b2bdbd54162075adb55b514d80bbe60ec1854b8044fb7cbea985c006

SHA512

883ee5a113ceeab99063d07d3b19b935e382dfdab598903fb896392d225d8dddc91716db56e29f4a92053d7b37e818806fcdad86126b9a5e2b68c17ad4f32c76

Summary

Bug Fixes and LDAP improvements. There are some changes to the configuration that will be required. See the change log below.

Change Log

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

  • Bug Fix: Query sessions were not properly cleaned up after becoming unused. This lead to a leak causing high amount of chatter between nodes.

Humio 1.6.9

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.9

Stable

2019-11-25

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

078266ac0716bd634fdc03fc7ef24ee7

SHA1

2457f4a35cef44b75351ed1ce794e32a253416b4

SHA256

26934b20ede90d7b4d4a855fe9fb2af749ec37a27bfbf44e79cb5d6c38c133d9

SHA512

dce9bdffddf89c9de819feb46bfbf59cd7bbc22da4d9131de588236a82306b131dacffbed3d6969f50e40a34e74b31d073cb31c814fa04a43e68e1063f89c435

Summary

Bug Fixes and a new background job that reduces number of small files on disk. No configuration changes required, but see changes to backup in 1.6.6.

Change Log

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

Humio 1.6.8

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.8

Stable

2019-11-19

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

002f3f8e6d2139542912f503d9a97b6c

SHA1

acf4b53e6363b85bb94ee7afff1961c712a3d21a

SHA256

e25243edf2fa906c18b61ce838b7114bf7cf03e787a638effc0881d645161227

SHA512

258b86a43f403caed0852903cdbcfd10664bbced66ea773f5a517bbca7c45143b07829a73bed4c92c12b29166cce3a22d5314b633ef8e091f8480d122432dae6

Summary

Bug Fixes

No configuration changes required, but see changes to backup in 1.6.6.

Change Log

  • Support for “sticky autosharding” and listing of current autosharding settings for all datasources in a repository.

  • Bug Fix: Segment merge could leave out some parts when merging, leading to segments not on average becoming a large as is desired.

Humio 1.6.7

Bug Fixes and Performance Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.7

Archive

2019-11-04

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

cc498d9bfbbae9fc815d046887e93ace

SHA1

bb9c4e01199a5c8727e4b825651139c808964b2f

SHA256

ede04107d73323f9b24374e9d6f45a8d62f56b484a2d042a4e3e0cd7781ddfc8

SHA512

a13ae84ae29339410d5de53cc77a2975f529c6baed9e61941ed9eb2f35130eea6ae0cb14595f7c7f8fb320e2c0cecd7a3e6e690a0f156ba87ceb404d5035f21e

Summary

Bug Fixes and Performance Improvements

No configuration changes required, but see changes to backup in 1.6.6.

Change Log

Humio 1.6.6

Bug Fixes and Performance Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.6

Archive

2019-10-23

2020-08-21

1.5.19

No

Yes

JAR Checksum

Value

MD5

6f5f5a9ca0cc982b8368feab633178bf

SHA1

82feebc7020bda86e42acdb18db6bc162020539a

SHA256

b969805efafe28497a2517ca3a3268dd1bb849bc39eb56ab31d62070ae07a5e0

SHA512

02df102a6589da27b9027b36447bc11222c616ca2c83bd00978d756001843464332b6cfcf886bc4dd749a31abe89ef62ba426bfce286ff37330a95c2ba809566

Summary

Bug Fixes and Performance Improvements

See changes to backup in 1.6.6.

Change Log

  • Humio’s built-in backup has been changed to delay deleting segment data from backup. By default Humio will wait 7 days from a segment file is deleted in Humio until it is deleted from backup. This is controlled using the config DELETE_BACKUP_AFTER_MILLIS. Only relevant if you are using Humio’s built-in backup.

  • Improved error recovery in query language. This should make query error messages easier to read.

  • It’s now possible to change the description for a repository or view.

  • Bug Fix: In Chrome, saving a query and marking it as the default query of the repo would previously not save the default status.

  • Bug Fix: Looking at the events for e.g. a timechart was previously untenable, due to a scrolling bug.

  • Performance improvements in digest pipeline.

Humio 1.6.5

Bug Fixes and Performance Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.5

Archive

2019-10-01

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

d5426b20769fcea54bdb6a296a1b853d

SHA1

7881a0845b5548afd23938731abef349259a5002

SHA256

d4d8abbdc1e4730141a36718101444377ed106c8a3db8557e572ca3eaec35bfa

SHA512

b71876f6d325b99cadbabb65acd304ca713ffb62e319a29941e16c5645540bf824a07c0fcc3d8820c735ae1e027bff1fad05ec150b36bf5bb973bc71d34ac274

Summary

Bug Fixes and Performance Improvements

No data migration required, but see version 1.6.3.

Change Log

  • Bug Fix: Support reading events from the ingest queue in both the format written by 1.6.3 and older and 1.6.4.

  • Improved performance of internal jobs calculating the data for the cluster management pages.

  • Redefined the event-latency metric to start measuring after parsing the events, just before inserting them into the ingest queue in Kafka. This metric is the basis of autosharding decisions and other scheduling priority choices internally and thus needs to reflect the time spent on the parts influenced by those decisions.

  • The new metric event-latency-repo/<repo> includes time spent parsing too and is heavily influenced by the size of the bulks of events being posted to Humio.

  • The new metric ingest-queue-latency measures the latency of events through the ingest queue in Kafka from the “send” to kafka and until it has been received by the Digest node.

  • Bug Fix: Apply the extra Kafka properties from config also on deleteRecordsBefore requests.

Humio 1.6.4

Bug Fixes and Performance Improvements

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.4

Archive

2019-09-30

2020-08-21

1.5.19

No

No

Summary

Bug Fixes and Performance Improvements. Retracted - did not properly support existing events in ingest queue.

No data migration required, but see version 1.6.3.

Change Log

  • Do not install this build. Do not roll back from this build to 1.6.3 - update to 1.6.5 instead.

  • Bug Fix: Creating new labels while adding labels to a dashboard did not actually show the labels as available.

  • Improved performance of timecharts when there are many series and timechart need to select the “top n” ones to display.

  • Improved word wrap of events list.

  • /query endpoint and queryjobs endpoint now coordinate thread usage lowering the maximum total number of runnable threads from queries at any point in time.

  • New metrics tracking number of active datasources, internal target latency of digest, number of threads available for queries, latency of live query updating and segment building, and latency of overall ingest/digest pipeline tracked for each repository.

Humio 1.6.3

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.3

Archive

2019-09-25

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

b4a29de04d375c5f71eda06a73ddb324

SHA1

e3d60d5ec6fb651b35b12dbf4e004872e4558ee2

SHA256

1ea140db06de2ebe78769e1bc1d827f6d5b007fb9419ecd746250d2a1abfa984

SHA512

4c472f8250e41729b73295296816094eb0b8bd53265a4dede89091c413bf9288b5b03c3864f16aba40bcd1cdede28438df4b0aad7fa79dae5acc0c7312f1061c

Summary

Dashboard parameters improvements and Bug Fixes. Data migration is required: Hash filters need rebuilding.

Improvements

Dashboard parameters can depend on each other. Fixed various small UI bugs in data table. Improvements to event list column headers.

Change Log

  • Bug Fix: Latin-1 characters (those with code point 128 - 255) were not added correctly to hash filters. To fix this, Humio needs to rebuild the existing hash filters: The old hash files get deleted, and a new file prefix “hash5h3” is applied to the new files. This will be done in the background after updating to this version. For estimation of time to complete use a rate of 100GB/core/hour of original size. While rebuilding hash filter files the system will have a higher load from this and from searches that would benefit from the filters but need to run without them.

  • New Feature: File based parameters on dashboards can now filter parts of a file out, by specifying a subset of entries in the file that should be used. This filtering can also be based on other parameters, so entries pulled from the file can depend on e.g. a query based parameter.

  • When setting up Humio the server will refuse to start if Kafka is not ready in the sense that the number of live Kafka brokers is less than number of Kafka bootstrap hosts in the configuration for Humio.

  • Bug Fix: The Event List widget no longer shows column menus on dashboards. Editing was not possible, but the menus would open anyway.

  • Bug Fix: The “Show in context” window on event list would “jump” when used and a live query on dashboards.

  • Bug Fix: Fix issue that made the timestamp column wrap on some platforms.

  • Bug Fix: Make JSON word-wrapping work when a column is syntax highlighted.

  • Bug Fix: Exporting a search (Or using /query endpoint in other contexts) would fail if any node was down even when the files needed to satisfy the search were available on other nodes. Note that a search in progress will still fail if a node goes missing while the search runs. (Searches in the UI restart in this case but that is not possible for an export.)

  • Bug Fix: Fix issue where streaming queries failed when a node in the cluster was unavailable.

  • Improved names and states in thread dumps and added a group field to the traces. Run #type=humio class=threaddump state=RUNNABLE | timechart(group,limit=50,span=10s) in the Humio repo to get an idea of variations in what the CPU time is being spent on.

  • LDAP login code rewritten.

  • Bug Fix: In Chrome, it was sometimes not possible to rename a dashboard, clone a dashboard, duplicate a widget, and other actions. This has been fixed.

  • Bug Fix: Using dropEvent() in a parser did not work when using the “Run Tests” button.

  • Replication of segment files among nodes now runs in multiple threads to allow faster restore form peers for a failed node.

  • Bug Fix: Fix issue with layout of pagination of table widgets in dashboards overflowing when it has a horizontal scroll bar

  • EventList column header menu opens on click now, instead of on mouse hover.

  • Bug Fix: Previously, exporting data from queries with parameters would always fail. This now works as expected.

  • Regex matching gets rejected at runtime if it spends too many resources.

  • New config: MAX_JITREX_BACKTRACK default to 1,000,000: Limits CPU resources spent in a regex match, failing the search if exceeded.

  • New config: MAX_EVENT_SIZE defaults to 1 MB. Increasing this may have adverse affects for overall system performance.

  • New config: HASHFILTER_MAX_FILE_PERCENTAGE defaults to 50. Hash filter files that are larger than this relative to their segment file do not get created. This trades the work required to scan them on search for disk space for files that are not very large.

Humio 1.6.2

Event List Columns and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.2

Archive

2019-09-04

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

dbd67c77d4a876f223d5cf30f5765d7b

SHA1

5d4f8b045ed5a98b85c906bbf190d5ea95de4c88

SHA256

407b5f8e24843bb18072ed4ce43e381a1022efb275f18c0f717e8e3784a92228

SHA512

872c39a7893b7196d65fde5d9ddcac31d30ba70ba2b7f4613e59396d06565a6410193036713eb3a4792e0fcfdf75b77bb83673ed8afce7f4f0a47aef568eb1f9

Summary

Event List Columns and Bug Fixes. The release replaces the event list on the search page with a table view where you can control which columns you would like to see.

Change Log

  • New Event List with customizable columns.

  • The fields panel is open by default. You can change this in “Your Account” preferences.

  • The default order of the events on the search page has been reversed. It is more natural to have newer events (lines) below older ones - just like logs appear in a log file. This can be changed in “Your Account”.

  • Saving a default query for you repository also saves the selected columns and will show them by default.

  • The special handling of @display has been removed. The field is now like any other. If you use it today, you can add it as a column in your default columns.

  • Use the keyboard arrows and Enter key to quickly add and remove columns while in the “Filter Fields” textbox.

  • You can now add favorite fields to your views. These fields will always be started to the top of the fields panel, and be visible even if they are not part of the currently visible events.

  • If a field that you would like a column for is not present in the list of fields. You can manually add it from the toolbar of the fields panel.

  • New query function hashRewrite() to hide values of selected fields

  • New query function hashMatch() to be able to search (for exact value) on top of the hashed values.

  • The UI now only checks the version of the Humio installation when determining if it should reload dashboards.

  • Users are now notified about the dashboard reload 5s before reloading.

  • Browser minimum versions get checked in the UI to warn if using a version known to miss required features.

  • Improve scheduling of uploads in S3 archiving to achieve better throughput.

  • Bug Fix: Fixed issue where some cluster nodes where configured differently than others, it would trigger a dashboard reload every 10s.

  • Bug Fix: timechart with limit selecting top series was nondeterministic when live.

Humio 1.6.1

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.1

Archive

2019-08-26

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

333a5243ca407814dc5437c71d7affc7

SHA1

fa3be4c0332421af5b5531fcda456f5a404199f0

SHA256

dd22a4a6c291d78537a4711aea71c0243646b3bdd6b645b9626c6266629c3039

SHA512

5c600ee0f7e88cbcb47500e235a9d2e9581b5630e4cfe596b000d2801219c6dc363ec9d0572a40a3bdd93c77868fbe7603d4502f4bdcbb008ab9e30af09d8f92

Summary

Bug Fixes

Change Log

  • Bug Fix: Fixed issue preventing you from clicking links in Note Widgets.

  • Bug Fix: Live queries could lock the HTTP pool, leading to a combination of high CPU and problems accessing the HTTP interface.

Humio 1.6.0

Support for Improved Compression

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.6.0

Archive

2019-08-22

2020-08-21

1.5.19

No

No

JAR Checksum

Value

MD5

19c48ed4689582534bdb4d2351224497

SHA1

8cb74a483006d732fedb52d835120663800d53a2

SHA256

4e519242ffa15eb15344e912479e350e60376c493d9c51b056c0c1f6b5349122

SHA512

a51db1066c5c7fc21c52a6a1a47d03ddb0b2a7bc977f37c1a65f27fb553ca9099587a5af74a942110f4cbd345b1a468f98407d320ea37e87b4a3cfe70892e044

Summary

Improved compression. Note Widgets and YAML Template Files

Improvements

Dashboard Note Widgets can include descriptions and can contain template expressions and links to external systems using the current parameter and time values

Read more about note widgets at https://library.humio.com/stable/docs/dashboards/widgets/note-widget/

We are also introducing a new YAML file format for dashboard templates. The new format is much human-readable. It is the first step to being able to persist all entities (parsers, queries, alerts) as files.

Support for the now deprecated dashboard file import API and JSON format will continue, but expect it to be removed in a later release.

Change Log

  • This update does not support rolling updates. Stop all Humio nodes. Then start them on the new version.

  • Note! Rolling back to v1.5.x is supported only for COMPRESSION_TYPE=fast which is the default in this release. The default is expected to change to “high” later on. The new compression types “high” and “extreme” are considered BETA release.

  • COMPRESSION_TYPE=fast (Default!) corresponds to versions before 1.6.x

  • COMPRESSION_TYPE=high turns on a stronger compression when segments get merged. This results in better compression, at the expense of having slightly lower compression for the very recent events. The improvement is typically 2-3 times better compression for the merged segments.

  • COMPRESSION_TYPE=extreme uses the stronger compression also in the digest part, even though it is not as effective there due to the gain from having a larger file after the merge.

  • COMPRESSION_LEVEL now supports the range 0 - 9. Default is now 3 for fast type, and 9 for the others. (Up to 17 was allowed previously: Check your config, as values above 9 will be rejected and Humio will refuse to start!)

  • COMPRESSION_LEVEL_MINI allows adjusting the compression level for high and extreme types of the compression inside the critical digest pipeline. Default is 0, max is 6. Keep low for optimal digest throughput.

  • The sizes of the compressed files and the associated hash-filter files are tracked separately for the merged part, allowing you to see in the UI how well the long-term compression works as part of the total set.

  • Introducing a new YAML dashboard file format.

  • Removed internal REST API for shared dashboards.

  • Added GraphQL fields for shared dashboards.

  • Changed GraphQL fields for dashboard widgets.

  • Added Note Widget support for dashboards.

  • The function sort() query function now ignores case when sorting strings.

  • Pending parameter edits toggle, so that parameter changes are not immediately applied if the user desires not to.

  • Renaming a repository is now possible in settings.

  • New function copyEvent() function allows duplicating an event into another datasource while ingesting. Use case to make the two events differ.

  • New function start() and function end() functions provides the time range being queried as fields.

  • New function urlEncode() and function urlDecode() functions allow for encoding or decoding the value of a field for use in urls.

  • The function parseJson() now accepts an exclude and include parameter. Use this to specify which fields should not be included.

  • Added cluster information pages for the Zookeeper & Kafka Cluster used by Humio. Both are available under Administration.

  • Bug Fix: Drawer heights were not being persisted between browser sessions.

  • Bug Fix: Changing Dashboard labels will no longer trigger a “Dashboard was modified remotely” notification.

  • Bug Fix: Styling of the dashboard “Labels” dropdown has been fixed.

Humio 1.5.23

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.23

Archive

2019-07-31

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

11cc896c1d0f7157e63acc1b34428106

SHA1

54b32056d10f567c56dcbad58f658ad88d5f0617

SHA256

0495a5384f2759d6e1adb9ff9030f9ded72b463ac667f74481878b8f2b0df5ed

SHA512

7013f12452a3f191a69630a105a171f6f496d6eca88ca8bae794d7f304669e99a296d17d1b9a9123ed97da8514f657abfa01403048412016be44f250671eb09c

Summary

Maintenance Build

Change Log

  • New config property: CACHE_STORAGE_SOURCE defaults to both, and also allows secondary to only cache files from the secondary storage

  • function collect() now requires the set of fields to collect.

  • Bug Fix: case that assigned fields inside was not handled properly when pre-filtering using the hash filters.

  • Bug Fix: Include size spent on hash filter files on disk in the cluster overview as Humio data rather than system data.

Humio 1.5.22

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.22

Archive

2019-07-11

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

03a4585d4f91d76dcf32eb2605b2f2a5

SHA1

8b449045065f1fcac5fa4720154dd5c07b671dec

SHA256

dcf4c3c2646071ef7ec4e96daba79fc62b10b7d23e7afab168fdd0f1047ffee7

SHA512

e455968440ae5b86d001f700616789dbfa3298cd02e769b473478bf5ff04f888b5c162d1afe5322cc35b040fdbe5d5817feaa850f26770e4f91b0928e595b78e

Summary

Maintenance Build

Change Log

  • There is now a humio-query-id response header on responses to “/query” search requests.

  • Bug Fix: Improved performance of “/query” endpoint.

  • Bug Fix: Always close everything when Akka actorsystem is terminated.

Humio 1.5.21

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.21

Archive

2019-07-04

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

3e69e9568f9def1fe56c9772266e529e

SHA1

17a1f945b825bb6220aa6cf4cf1d4675420578ac

SHA256

84550bd4f356c57e37055b34f5a0fc00c25a20e08faa2d6a0f8843e029550932

SHA512

dcbf18ea92afa7f5c0cbf1f41835a948e3aa0a6b2e303d1c40d8c2c8bd9c9084186e73c1a2aa76221381bf6f66872b7708e994243969273344e28fcb73b7db1c

Summary

Maintenance Build

Change Log

  • If an events gets @error=true in the ingest pipeline (including in the parser) it will also get #error=true as a tag. This makes events with an error become a separate datasource in Humio allowing you to delete them independent from the others and makes problems from parsing timestamps not disrupt the pipeline when back filling old events.

  • New function: function dropEvent() lets you discard an event in the parser pipeline. If a parser filters out events using e.g. a regex match that does not match the parser will just keep the incoming events. Use this new function (typically in a case) to explicitly drop an event while parsing it when it does not match the required format.

Humio 1.5.20

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.20

Archive

2019-07-04

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

6e7fc0c55dcb7e983c3e9ed01fe2a998

SHA1

bee0844d369a237d7ce7da118806be97bb1fab83

SHA256

d647ba881452c4905e44894168461f389bce43e9aa93c58d719f1ec9de62dd13

SHA512

4631ea0f892c5a6044a7c0b008b1350ce2d3408883e73fb3d357bb4f9920c762efbcf7efbb26b1fa3bb5577c327f260c243371c6a367d566ed0dc48794600499

Summary

Maintenance Build

Change Log

  • Bug Fix: “services” is no longer a reserved repo name.

Humio 1.5.19

File Based Parameters on Dashboards

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.19

Archive

2019-07-03

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

fa9d61d17a037583bbe067a4aab64ab3

SHA1

1793534d22cfc53c5b15dde0dc60d008ad9c9204

SHA256

6e21cd3874a948a3ddf3554911c3104e60a2ca33e8e4a039755eca42c03e1508

SHA512

ec09a60164c981970b20fd401140a5dac2e3814f6e1254c3472721ace2db957b92f9035b8833436008054220385b55e1e83b93f6b1547842c289a0194522913c

Summary

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

Improvements

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

New file based parameter type is added to dashboards.

Change Log

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

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

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

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

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

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

Humio 1.5.18

Support Ephemeral Drives for Caching

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.18

Archive

2019-06-26

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

c4d0166d229209681cd23f4d34ce0e75

SHA1

23aeac090b6069258d168f235d025d497baf6147

SHA256

db78a9fdc47bc3f3687e758c9e1dc5c13c14525626199568889226121eca4629

SHA512

a8b66956d7d58a6bba71884ea01c91fea88d96b1c58ff9ba63a0f111da84f270e8bee16e87e1148415635425704472a5d4156b4300b1d7bb58ddd96091cdee49

Summary

New function parseXml and support ephemeral drives for caching.

Change Log

  • Humio can now keep a cache of the latest files on when told the path of a cache-dir using CACHE_STORAGE_DIRECTORY. Humio will then write copies of some of the files from primary and secondary storage here, assuming it is faster to read from the cache. The cache does not need to remain after a restart of Humio. CACHE_STORAGE_PERCENTAGE (Default 90) controls how much of the available space on the drive Humio will try to use. This is useful on system such as AWS where the primary data storage is durable but slow due to being across a network (e.g. EBS) while the server also has fast NVME-drives that are ephemeral to the instance.

  • New function parseXml() for use in parsers

  • New built in parser corelight-es to parse Corelight data send using the Elastic protocol.

  • MAX_EVENT_FIELD_COUNT (default 1000) controls the enforced maximum number of fields in an even in the ingest phase.

  • Bug Fix: Certain regular expressions involving ^ and $ could fail to match.

  • Bug Fix: Parameter input fields for query based parameters initially always showed * even when a default value was set. It now correctly shows the default value for the parameter.

  • Remove configuration flags: REPLICATE_REMOTE_GLOBAL_HOST and REPLICATE_REMOTE_GLOBAL_USER_TOKEN

  • Bug Fix: Reduce size of global snapshots file.

Humio 1.5.17

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.17

Archive

2019-06-20

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

d40aa67958efee188fbbd801389ca6a0

SHA1

912ff791cc76312bdc3c3e72877e9872b0cebca7

SHA256

45a48f7cdb99d4e08f95f1ef6802ecf730e8ae997b23ad1ba6f2f1e5fec14e91

SHA512

ce51829c5152bed8c2d67581239365c4055ddc038545f20877c6a1d499aca6f69b920bc006d2499659194d0b4bf1ebdef7be7d55262318620dd73ee76c8d822b

Summary

Maintenance Build

Change Log

  • Update BitBucket OAuth integration to version 2

  • Bug Fix: Updates to repos with reserved names on legacy repos did not work.

Humio 1.5.16

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.16

Archive

2019-06-11

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

1ae08e9fa6216dd50b413b0b733054d3

SHA1

9da479f33fa955645eb6f8c048a335dee59ff5a8

SHA256

a5738bb660340e67570f673652c49efc2b6e9e4281ddab1c2bc6fdd242418644

SHA512

b96b45050e0cb5d0a1b90968bf22b2bc8ee746076a266f147802b33f920cbac73dc2d5418ff86ed672411758c304fe4d387bb1bdc8c068594acda682fd66ec5b

Summary

Maintenance Build

Change Log

  • Bug Fix: Invalid parser no longer prevents ingest token page from loading.

  • On Windows, the Ctrl+O shortcut no longer opens the “jump” menu on the home page, but Ctrl+Y does instead, to avoid conflicts with browser shortcuts.

  • Bug Fix: Ability to read global-snapshot.json when the file is larger than 1GB.

Humio 1.5.15

Dashboard Improvements and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.15

Archive

2019-06-06

2020-03-14

1.5.8

Yes

No

JAR Checksum

Value

MD5

ad5393b90a76798037d974eb15274170

SHA1

a39f7d6a55a9e20d35a76cc77d1593e733f82fa0

SHA256

ef07ed1498a14912ae33c438dbce446bd3c515598b56a53590bb28e0da764eac

SHA512

35d8cf32cfffc01456fea778186098acc17fadd6003ca910eca6165c6113cbd5ad9a68a5fcd52a9ab9934a51bc3e9175f1f139a5b400e4249cfcd7f2b7faddda

Summary

Dashboard Improvements and Bug Fixes

Change Log

  • Dashboard parameters with fixed list of values now keep the order they were configured with

  • Dashboard parameters with fixed list of values can now have labels for each of the values

  • New function eventFieldCount() that returns the number of fields that this event uses internally for the values, use along with eventSize() to get statistics on how your events are stored.

  • New config: VALUE_DEDUP_LEVEL default to the compression level. Range is [0 ; 63]. Higher values may trade extra digest time to get lower storage of events with many fields.

  • Humio metrics have now been documented.

  • Bug Fix: Regex with [^\W] did not execute [\w] as it should.

Humio 1.5.14

Improved Pre-Filters

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.14

Archive

2019-05-29

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

a04ea786b04438c4028a880948ab4ac0

SHA1

8d82c939347c1a28e46efa5605b5592e5b25824d

SHA256

edc162b7dcd604948cca55d924838754ca0162e3d5d97ba26a5e8cfd0df512b2

SHA512

30935d7230af57de26beb316a5d7c79a35a01d23e41dc4a5d06268910a7aa95535e1f7fbe88448a9f504e7e9a2c97fd43bfa0f90e4ce2a12c1976e5250a0999a

Summary

Improved Pre-Filters

Change Log

  • Improved pre-filters to support more searches while adding less overhead in disk space.

  • The disk space occupied by the pre-filter files now get included when enforcing retention by compressed size.

  • The format of the new hash5h2 files is different from the previous bloom5h1 and the system will generate new files from scratch for all existing segment files and delete any existing bloom5h1 file.

  • New config: HASHFILTER_FILL defaults to 30. Sets the target number of percent bits to be set in the pre-filters. (Range 10-100).

  • New config: BLOCK_SIZE_MIN_KB defaults to 384. Select minimum target block size for data files, in KB.

  • New config: BLOCK_SIZE_MAX_KB defaults to 1024. Select maximum target block size for data files, in KB.

  • cidr(): When file and column parameters are used together, load subnet list from given CSV.

  • Bug Fix: When an alert fails to send the notification, don’t restart the query, just retry the notification later.

Humio 1.5.13

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.13

Archive

2019-05-27

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

894e1bbdc1a57f2f0b46c162f42c3f46

SHA1

ba223177715e7090610100557f0929eb9c628ac0

SHA256

5eb2a227ca5964915ebdd96bce5ae7bb0adb611e983714459440685ab45c86b6

SHA512

07a7237614c98045b72e5dffc3cb5d480adbf7b62747e9932e1599579128b205c9a80cf73983ea2c724dab0a9ba0d2226c84b9cffdbb45ab9e7bdb4eb938d623

Summary

Metrics are now send to a separate file humio-metrics.log.

Change Log

  • Fix some cases where parameters would not be picked up by the UI because of regex or string literals in the query.

  • New log file humio-metrics.log. Metrics data has been removed from the humio-debug.log and moved to humio-metrics.log. Metrics will still also be in the default Humio repository. If you are collecting the Humio log files, with for example Filebeat, you need to add humio-metrics.log to the collector.

Humio 1.5.12

Parameters in Dashboards

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.12

Archive

2019-05-20

2020-03-14

1.5.8

Yes

No

JAR Checksum

Value

MD5

a560cb0ce83c1809b9a5058b69591d7e

SHA1

b631299178941b9b104a35c5d446942b183889ec

SHA256

de58549b4e0b8cc5e1f57c75592259cea90eb022f280f422f1bcb8bdd7068c6b

SHA512

58c40dae601d284b1a4c4fdf19629955c19c74abcb186aec61a8ce1f3c192909c21503f4eec8fc17ede7238f473e497dfe32b24a4e1a6a4c36902cf1ae4c4c0f

Summary

Parameters can be used to make dashboards and queries dynamic.

Change Log

  • You can now use the syntax ?param in queries. This will add input boxes to the search and dashboard pages. Read more in the Dashboard Parameters documentation.

  • URLs now contain parameter values making it easy to share specific dashboard configurations.

  • Parallel upload of segment files to S3. Degree of parallelism can be controlled with e.g. S3_ARCHIVING_WORKERCOUNT=4. Default is 1 if nothing is specified.

Humio 1.5.11

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.11

Archive

2019-05-16

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

4f01eabfd30739ac228e423a5f51582f

SHA1

e7c174433f19fbe81a13f6e7b2b8d849c480d22b

SHA256

e2eb4d827bd1a1a67923c30a535d8b968f4574c9bbf59bfc84c8a2fcfbccaec2

SHA512

952f9de0089c9528accfee959951a54ef400a3ce49d37d1666234a7ec3f1d9de1e7e164d8ff101e461e62f31faf4331575e63eb2fc4b54484bb9f6d9267e8bb2

Summary

Bug Fix Release

Change Log

  • Bloom filters are now always on.

  • Named groups in regular expressions supports having . [ ] in their names.

  • Moving segments to secondary storage can no longer be blocked by merging of segment files / s3 archiving.

Humio 1.5.10

New Bloom Filters

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.10

Archive

2019-05-13

2020-03-14

1.5.8

No

Yes

JAR Checksum

Value

MD5

1b828fd0d80aa3c80aa9f1d4bba0dbd6

SHA1

998c039c894acdbe30d83efa414428ab77de2d7e

SHA256

b18d7b1844f4482f0e1aa8afe7e67ad1bf06e8bb5f40faebe9179c49dc72a412

SHA512

cb3efdf806231d2f3d71d378054e7513eed3bd73ccb445159f8232da4df14bae1f1165bde27d5536554f178dbcde3973d2d64e2f33271247e734cc3d6b88fd3f

Summary

New bloom filters, but please upgrade to 1.5.11 to avoid known problems in this build.

Change Log

  • New experimental bloom filters that speed up searching for constant strings such as UUIDs and IP-addresses; the longer the search string, the bigger the speedup. The bloom filters also help regular expression searching, including case insensitive ones.

  • MUST be enabled with BLOOMFILTER_ENABLED=true (Note! defaults to false in this release, which makes searches skip events they should not).

  • When enabled, this will write files along with the segment files with prefix bloom5h1., which add approximately 5% storage overhead.

  • The bloom filter files will be generated as part of digest work, and also generated for “old” segment files when Humio is otherwise idle. Thus, when the feature is initially enabled, it will be visible that the CPU load is higher for a period of time.

  • It is safe to just delete any bloom5h1. files while the system is running, or in case the feature needs to be disabled.

Humio 1.5.9

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.9

Archive

2019-05-06

2020-03-14

1.5.8

No

No

JAR Checksum

Value

MD5

b6dc38838aac82596ea8eebf294b9a97

SHA1

ca35bf05425265706467adc415c8ff558bad12f9

SHA256

4d0af39687972dc6bb476928edf9c0b10d956336a564d0a828b8e036174e1da5

SHA512

a2b8e9512fc287c8ff3f2d40a734d5bab872ccedf995bdeeb8a3fc900169a7d1bfaa85a6a30e43e0272ea97bf3e3f44e6f397535818e6e7b1fac15ca0ced98d2

Summary

Bug Fix Release

Change Log

  • Add information on query prefixes to the Query Monitor. When inspecting a running query in the Query Monitor the query prefix can now be found in the details pane.

  • Bug Fix: Alerts with multiple notifiers could result in notifications not adhering to the configured notification frequency resulting in notification spam.

  • Bug Fix: Enable sourcetype field in the HEC endpoint to choose parser (unless another parser is attached to the parser token).

  • Bug Fix: Default filters in dashboards could cause search to not find anything.

Humio 1.5.8

New Dashboard Editing Code

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.8

Archive

2019-04-25

2020-03-14

1.4.x

No

Yes

JAR Checksum

Value

MD5

4898c50c07b21c557e16f9ecb0525b64

SHA1

6f7de5e75418ab04752927081ac4af0156b78df9

SHA256

449c36c1b9cf793db02250e1d089594491fde458f46b33b2b4b2967ef7e0bef7

SHA512

d382620aa86df5fc7d24977d6097f1d40829e5b1c5cce5431ce6110ca256be99a636bdb1d5b0d322fee1cc784d55f7b4cc12ae78da059b4089cbb9739494e7e0

Summary

New dashboard editing code and many other improvements

Change Log

  • config property KAFKA_DELETES_ALLOWED has been removed and instead DELETE_ON_INGEST_QUEUE is introduced. DELETE_ON_INGEST_QUEUE is set to true by default. When this flag is set, Humio will delete data on the Kafka ingest queue, when data has been written in Humio. If the flag is not set, Humio will not delete from the ingest queue. No matter how this flag is set, it is important to configure retention for the queue in Kafka. If Kafka is managed by Humio, Humio will set a 48hour retention when creating the queue. This defines how long data can be kept on the ingest queue and thus how much time Humio has to read the data and store it internally.

  • Dashboard queries that are not live and uses a timeinterval relative to now, are migrated to be live queries. Going forward, queries with timeintervals relative to now will be live queries when added to dashboards.

  • Humio’s own Jitrex regular expression engine is again the default one.

  • S3 archiving now supports forward proxies.

  • Validation of bucket and region when configuring S3 archiving.

  • Bug Fix: Built-in audit-log parser now handles a variable number of fractions of seconds.

  • Bug Fix: parseTimestamp() now handles dates, e.g. 31-08-2019.

  • @source and @host is now supported for Filebeat v7.

  • The Auth0 integration now supports importing Auth0-defined roles. New config AUTH0_ROLES_KEY identifies the name of the role attribute coming in the AWT token from Auth0. See new auth0 config options <https://library.humio.com/stable/docs/security/oauth#mapping-auth0-roles>__.

  • In tableview, if column data is of the form \[Label](URL) it is displayed as Label with a link to URL.

  • Bug Fix: Alerts notifiers with standard template did not produce valid JSON.

Humio 1.5.7

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.7

Archive

2019-04-10

2020-03-14

1.4.x

No

No

JAR Checksum

Value

MD5

5ed44bb802f54fc03ea606da0e5d2afe

SHA1

d3c3d7705366851dfa019214c3cf2b653914c7f2

SHA256

41d0da3dd48732136ae245209cb549946e46f31ff0bca9a2fd37d2d9c73b05f4

SHA512

f07ac6a204637973c64f830082245475b7ec3b6dfe01eb98d63a68adaa5f352a0c4647ec189cbc12f543c50e093d63475377031b869538be076c097394a853dc

Summary

Bug Fix Release

Change Log

  • Bug Fix: Revert default Regex engine from jitrex to RE2J. jitrex has a case where it may loop infinitely and this will break the digest pipeline if this happens in a live query.

  • Temporarily disable deletes of events from the ingest queue to allow recovering events skipped in the queue due to the above infinite loop problem.

Humio 1.5.6

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.6

Archive

2019-04-04

2020-03-14

1.4.x

No

No

JAR Checksum

Value

MD5

614a06c67d4e93e1a3f2083ce5cfe4c0

SHA1

57d3259a0469703caa38975a0be19062f0954e57

SHA256

e410583413293132f0e6f09884c3387282892b31164c77472cb0f4343f4d6ec6

SHA512

0a00735576c700ee063824ead2845452cbf1f00530014be127d13cb7da89a55143d64192755b00e3039f175cc64985cad736cd9dbe08f54005163f43008c1a1c

Summary

Bug Fix Release

Change Log

  • Bug Fix: LDAP integration.

Humio 1.5.5

Event Context

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.5

Archive

2019-04-03

2020-03-14

1.4.x

No

No

JAR Checksum

Value

MD5

39a4777bd2dae7d69177426d063dc6df

SHA1

6d27f9ae18dbcb49bfc37f7c014db93f331652ea

SHA256

e3ec14f8cbc6d78c4beede209fe4be958e5c727fe3a7fcb2d7919afc81c3c85d

SHA512

7d3c645974227a9e9dfd8ea261923f516b626d02eea73ab5bd7fdccd3bfdfbfab7f05e37abe49019d7a0ff97bd3824646e4de1ff8f587fdbf3623bed77c9da42

Summary

Event Context

Change Log

  • New event context searches let users select and search around one specific event.

  • Display information on disk space usage of primary / secondary storage location in cluster management UI.

  • A GET on /api/v1/users that lists all known users on the system no longer includes information on the repositories for the user, as that made it too slow.

  • New configuration keys: MAX_SERIES_LIMIT and MAX_BUCKET_POINTS.

  • Restart all relevant queries when an uploaded file gets changed. This allows live queries and alerts to refresh using the latest version of the file.

  • Bug Fix: Live timecharts could accumulate data for 2 buckets instead of 1 into the bucket that was right-most when the charts starts.

  • Bug Fix: Segment merging could reuse a tmp file when the system was restarted, which would block the merging process on that host from making progress.

  • Bug Fix: Fix bug in regex not recognizing [0-9] as part of \w

  • Uploaded files cannot be bigger than specified in the config MAX_FILEUPLOAD_SIZE. Default value is 100 megabytes. The default value is used in our cloud.

  • The size of the Drawer, showing event details on the search page, is remembered (by being saved to local storage)

Humio 1.5.4

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.4

Archive

2019-03-26

2020-03-14

1.4.x

No

No

JAR Checksum

Value

MD5

d3c301554f98e7540728d412b6452e49

SHA1

c172bf5c456df3ded1e08f37f232b0ea7fbf96eb

SHA256

d4b23822b1a63846913dbd9421cfc3a7d937af4c3b3d17262b3674e5a4a99a16

SHA512

82a2f80540e623f05eab2219cf79283f406255b18ae10083de1eecf30038ab8b413d497138c1cfa6c758978c490cbfbc21b3e4abc63e19c1d3bf47c8f1625fb9

Summary

Bug Fix Release

Change Log

  • Bug Fix: Query scheduler could get into a state of doing no work when overloaded during startup. Workaround while working on proper solution: Raise the queue size internally.

Humio 1.5.3

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.3

Archive

2019-03-26

2020-03-14

1.4.x

No

No

JAR Checksum

Value

MD5

64439aad4fb74f03ab9cf140de039d2e

SHA1

16f55ee1018400f92aec8fd0330e54b81077d4dd

SHA256

6acb0265a88ee250390a1021db382724148e8b09a7738fa7c948fd6f95d06870

SHA512

9705984865b1852aff9b4237d391ea94b40e0cee972e1ed82fc4e5b9f84a08a69e71bfd5614ad2b141479ff1b1b50523ab1ef9e7b05c5ce31eb6a35d51f40c96

Summary

Bug Fix Release

Change Log

  • new Config flag WARN_ON_INGEST_DELAY_MILLIS. How much should the ingest delay fall behind before a warning is shown in the search UI. Default is 30 seconds.

  • Bug Fix: Webhook request could end up with malformed requests.

Humio 1.5.2

New Math and Time Functions

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.2

Archive

2019-03-25

2020-03-14

1.4.x

No

No

JAR Checksum

Value

MD5

5df6f461a9703cdf6ae3095f73502e53

SHA1

5400b067c8e7c56b1febc4ed4903e62499f83470

SHA256

8814989d98be9aa7b53ddcdeaffa394056ca70c08edf6c5e2cdcf05a4db21c86

SHA512

de757392b3ae568ed348af4bd0153ebc76b15e4f2b16a540f9af756235479f833b0a8f1d92cd3a87ea011dded75841f1dea91f1d15675ec7c465cc6db32f637d

Summary

New functions for Math and Time operations.

Change Log

  • New functions for “Math” and “Time” operations.

  • Java version check: Allow JDK-11 and 12.

  • Bug Fix: Query prefixes for users were not properly applied to the “export” api.

  • Bug Fix: Date picker marked the wrong day as current.

  • Bug Fix: Repositories with names starting with “api” were inaccessible.

Humio 1.5.1

New regex Implementation

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.1

Archive

2019-03-22

2020-03-14

1.4.x

No

No

JAR Checksum

Value

MD5

669f2e0e026ac5ce1ada07221cbd2397

SHA1

9157d3100b8c35d1c36ef03323aa1431de11b0d4

SHA256

846f0de0235cf4835e5da75853d4fbc069ad6d0fb2c74bafda3a0d471e1041c7

SHA512

5e27430929861a3ef0c3aea3accc88d7b57b8ac133d87dd1757cbc8ed88cb3914a93592c368886eed2b938c576d81099ee97fa60a79118fb4f6d120060dbb705

Summary

The default regex engine has been replaced.

Change Log

  • New regex engine (Humio jitrex) is now the default; configure using DEFAULT_USER_INPUT_REGEX_ENGINE=HUMIO|RE2J. If you experience issues with regular expressions try setting configuration back to the previous default RE2J. You can also pass the special flags /.../G (for Google re2j) or /.../H (for Humio jitrex) to compare.

  • New implementation backing match(...) for exact matching (glob=false) allows using .cvs files up to 1 million lines. The limit for exact match state size can be set using EXACT_MATCH_LIMIT=1000000

  • Timechart more efficient in the backend, better supporting more than 1 series.

  • No owls were hurt in the production of this release.

  • Bug Fix: Kill query or blacklist query was not always killed on all nodes.

Humio 1.5.0

Parsers Migration and Deletes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.5.0

Archive

2019-03-15

2020-03-14

1.4.x

Yes

No

JAR Checksum

Value

MD5

c3615501d40a6cb19301c26174548841

SHA1

0cb80023e27a2e43e6b0281711ed4483e1415caf

SHA256

5ec7ad5370a1768d886885ecf118ea6bcd09af362175011521e1209308ab35b6

SHA512

f5e5d71332d774f87e13143b458707c1ddbf114901292c4b1cbdef27844f0c6e7460afde36c6fa0f5e638c6251b908fcae3b22bcb908506726824399d568b78c

Summary

All parsers are now written in Humio’s query language.

Change Log

  • New BETA feature: Delete Events allows deleting a set of events from the internal store using a filter query and a time range. At this point there is only API (Graphql and REST) for this but no UI.

  • All parsers created before the introduction of parsers written in Humio’s query language are migrated.

  • The option ‘PARSE NESTED JSON’ on the old json parser creation page is no longer available/supported. Instead use parseJson on specific fields, e.g. ‘parseJson() | parseJson(field=foo)’. This has to be done manually for migrated json parsers!

  • Migrated regex parsers with the option ‘PARSE KEY VALUES’ enabled has different parse semantics. If the regex fails key values will no longer be extracted.

  • Bug Fix: permission for editing retention when running with ENFORCE_AUDITABLE=true.

  • Bug Fix: Non root users could not see sandbox data when using RBAC.

Humio 1.4.9

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.9

Archive

2019-03-13

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

658abeee302dd14ad05a2b7d50ca5a6a

SHA1

c5bf3e514152899299880a77faf08fb7bb0595d8

SHA256

dc48a0753a3113ced36f67fd91814735ba31f01cf51cdd6cd4ab31614460acb0

SHA512

fa0f2732aaca9ad7bfde148270547efeec8da6a1d237c88d5d315e25269666054fb0ef76e08d2cfbebef5a29b460a947d75d3994f18c9e0bf0676d226b16fffd

Summary

Bug Fix of retention not working.

Change Log

  • Bug Fix: Retention was not applied to all segment files in a clustered setup. The bug was introduced in 1.4.4.

  • Bug Fix: Prevent labels in gauge widgets from being clipped.

  • Bug Fix: white space in field templates in alerts.

  • Increasing AUTOSHARDING_MAX default from 8 to 16 and start autosharding at 4 instead of 2,

Humio 1.4.8

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.8

Archive

2019-03-11

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

b4757d785261fc262a3d618296d690d1

SHA1

1dc9f2712b87567e40889262da8095086e060d6a

SHA256

0eed830ffdd0ae4bfbacf5f2627a29104a0928e1e3b6635553cf841cef5f0aa2

SHA512

0950bc904e0b80b501c4fca4ee8634db2ca9fcca4fd9154e77dd8c223e867e754d1147b9013434cf15566d5fe21ccfe6056416d1ecf6d242a974141f88673acd

Summary

Bug Fix Release

Change Log

  • Bug Fix introduced in last release for handling error messages

  • Bug Fix create default directories in the Zookeeper Docker Image

Humio 1.4.7

Minor Enhancement

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.7

Archive

2019-03-07

2020-02-14

1.3.2

No

Yes

JAR Checksum

Value

MD5

d09b1e4945cff155ce459cdd293bb4e9

SHA1

d44e10514f3c9b1e46c9b3ccaef5f9418226b4e1

SHA256

bd950358b9eb8f20269ee2823fd579a856c535237d49002891f6f9455c117fd7

SHA512

f3b838a1c2b284467b99e395963685e47ca57a2c774c8a77ef3b51878fece9a8d6dd5371818f9897c6f591996a50f158a233b9cf511ce3167bd887047f4aec92

Summary

Saved queries allowed in case and match.

Change Log

  • Humio now requires Java version 11. The docker images for Humio now include Java 11. If you run the “plain jar” you must upgrade your Java to 11.

  • Saved queries now supported in case and match.

  • Upgraded to Kafka to 2.1.1 in our Docker images and the Java client in Humio. Humio is still be compatible with older versions of Kafka. Lowest supported Kafka version is 1.1.0.

  • Improved handling of the “Kafka reset” aka “Start from fresh Kafka” aka “Set a new topic prefix”. Humio detects and properly handles starting after the user has wiped the Kafka installation, or pointed to a fresh install of Kafka.

Humio 1.4.6

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.6

Archive

2019-03-04

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

8cf206c7d6972c1268f9b01d78b231a7

SHA1

b2b550a80c08715ee6a5f073612e05da7e16468d

SHA256

38aaad962f12cd6d3bc44d0d2467cd9c8e6d12568f9fbe2cd527fbfa23895968

SHA512

f078c07a386aa88ac910f198d81fd6d8d230c5e5e3b205afad6a29741ab1a4e6cb918828d8e2e1fe16e8c3e705705b6eeab5d0cfce17740367ba97b8d0804fe4

Summary

Bug Fix Release

Change Log

  • New config: ENABLE_PERSONAL_API_TOKENS defaults to true. When set to false the API tokens are no longer valid as auth-tokens.

  • When @timestamp is in the filter part of the search then let that limit the timeinterval as if selected in the time selector.

  • Bug Fix: Prevent ‘http response splitting’ attack in the “export as” function.

  • Bug Fix: The personal sandbox was missing in list of visible repos for non-root users when READ_GROUP_PERMISSIONS_FROM_FILE was enabled.

Humio 1.4.5

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.5

Archive

2019-02-27

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

a40c7e599b3e4fafc887ef8712552f70

SHA1

61f99d83c67f6a8d993f5bb13ca5f59887f85358

SHA256

5af2499bd32943ccdc3377b609b244ebf87c32e5c4d4d2c632dc2e7ee1921c3f

SHA512

21f1a835d97f96347b0480b3a9b122cf7ff2a6e2cab7ad0a47b00d8b36ba3a24dafd78d34ee2404659388bbbf319ca066ce47cee7aa2048037fd03a475324c3f

Summary

Bug Fix Release

Change Log

  • NODE_ROLES being applied in more background tasks.

  • Many background tasks now get executed only on hosts with segment storage partitions assigned, and the hosts use the storage partition assignments as the key to decide which hosts must execute the tasks, thus freeing up resources on the other hosts.

  • Bug Fix: Timechart in “steps mode” now displays the the the right of the label instead of to the left, which matches the fact that the labels are the start time.

  • Bug Fix: Shutdown of digest had a timeout of 10 seconds internally, which could lead to being dropped too soon while shutting down or restarting. This could result in ingest lag rising to over 1000 seconds, where the expected lag is the time from the shutdown is initiated until a fe seconds after the new instance is started. There is a new config SHUTDOWN_ABORT_FLUSH_TIMEOUT_MILLIS which defaults to 300000 millis (5 minutes) to allow proper shutdown also on systems with many datasources or slow filesystems / disks.

Humio 1.4.4

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.4

Archive

2019-02-26

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

03050687bddbd6ffe56830ed84f827e4

SHA1

f1f9cabbcbddb014e4aef0f8e1869fbbd8c60c8d

SHA256

8ab6c51081d0b918de61340f7a6d241f740b3ec77ae9d3a7517805c925412af3

SHA512

718e7abf3b89076d07bc36c89606b9a72cc5b7c15432550b903931172ce6fca323aff85a0feecc4e1de5de5a02cc7ccb099c79166d59376ca8dc5dee78c8f2ee

Summary

Bug Fix Release

Change Log

  • Detect if a host in the cluster is being set to have the same vHost index as this host, and exit in this case.

  • Bug Fix: Repository statistics displayed on frontpage were out of date on servers without any digest partitions. This also made the search page display the warning “You don’t have any data yet, consider the following options…” when searching until a result of the search was returned.

  • Bug Fix: Making a repository or view a favorite failed on recently created items.

  • Bug Fix: On a cluster with many segments and a node with no segments, the cluster administration page could time out.

  • Bug Fix: Having timezone offset larger than the span in a timechart could result in errors.

Humio 1.4.3

Improved Restart of Live Queries

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.3

Archive

2019-02-21

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

fb4d7742cb6418b51024f84bb61f9346

SHA1

6ba6f2f9636a28db9c4b882e07df356e2c255f6b

SHA256

440bc3d0321042007c8b0c3749d93175e15d554dae66c1863495bb7464a9dcc4

SHA512

f7a5c820e7482889371217d32faabda602f31389242876b5f7e49a2a8081804707b4013be6dd3323da03b3518aa852cb88c2820ebc44732fbb26330b03102436

Summary

Improved restart of live queries.

Change Log

  • Restart live queries if their query prefixes change when using Role based authentication and access control (RBAC).

  • Remove migration from internal data formats older than what v1.3.x writes. Do not start this version without having upgraded to 1.3.2 or 1.4.x first.

  • Humio’s UI is programmed in Elm and we upgraded to use Elm 0.19.

  • New config option: NODE_ROLES with current options being “all” or “httponly”. The latter allows the node to avoid spending cpu time on tasks that are irrelevant to a nodes that has never had any local segments files and that will never be any assigned segments either.

  • Improved restart performance to better support restarting (or upgrading) the servers in a large cluster with large amounts of data.

Humio 1.4.2

Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.2

Archive

2019-02-19

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

cf5177de7c89a5c02121d29b4d359dab

SHA1

08fc9b230423eb1abde2f8f3c43c6c06e230b457

SHA256

4cfef752ca7286a2cbb91e33ca7619488c06e59079640f7f8f2fd11779066b11

SHA512

2997e1f2a5ea57ce2e7b8ce2c360e113f9dfa2a983abb2e02bcab8e555591783cf7b7b29f4f567bb0531aa83136daa98461b3b4b8cf217d22eb8f4fa8fe513fa

Summary

Minor release. Improve restarting of queries and Ingest listener performance.

Change Log

  • Bug Fix ldap authentication code.

Humio 1.4.1

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.1

Archive

2019-02-18

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

78e0cf1a91b21be2f13f92f4551c212a

SHA1

4f0dc81ffd99d0a7802f2a5f4a1cc492646a5ffc

SHA256

68b99a2998f50c77c91f098e5d033347ab51912e8c639751a6012b29559abd5e

SHA512

1d877446dba301b5e39d723b2e58a88edba98bc46d7c969821adf2db32ae115ef46b90f1ce3d2b0ddfc7df6aa75e5d5f3042e59840007d03c2433197f9c6de87

Summary

Minor release. Improve restarting of queries and Ingest listener performance.

Change Log

  • Improved restarting searches when a node go away.

  • Improved Ingest listener performance. One socket can more throughput than before.

Humio 1.4.0

High Availability for Ingest and Digest

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.4.0

Archive

2019-02-14

2020-02-14

1.3.2

No

No

JAR Checksum

Value

MD5

fb0290d5203f178cfbbef8df7b89106a

SHA1

7e2f17d867734264c91c697849884bb530fbc450

SHA256

cce65b639ab277dd50cf29f2d53ff119d705c64d33a4a118b8e49b899d8dd27c

SHA512

7cfad54614ef63f35fe6d3cc50d2239650845b390e0aea63f1e2e199745a68854524fdb24cad5f59867339cbe0eb2432bd904cef7e7a90e9b115d5abe6f1a52a

Summary

High availability for ingest and digest.

Change Log

  • If rolling back, make sure to roll back to version 1.3.2+

  • Digest partitions can now be assigned to more than one host. Doing so enables the cluster to continue digesting incoming events if a single host is lost from the cluster.

  • Emphasis is on efficiency during normal operation over being efficient in the failure cases: After failure the cluster will need some time to recover during which ingested events will get delayed. The cluster needs to have ample cpu to catch up after such a fail-over. There are both new and reinterpreted configuration options in the config environment for controlling how the segments get build for this.

  • Segments are flushed after 30 minutes. This makes S3 archiving likely to be less than 40 minutes after the incoming stream.

  • Limit match/lookup functions to 20.000 rows or whatever “MAX_STATE_LIMIT” is set to.

  • Bug Fix: Clone existing dashboard when creating from the frontpage was broken.

Humio 1.3.2

Multiple Alert Notifiers

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.3.2

Archive

2019-02-12

2020-02-07

1.3.0

No

No

JAR Checksum

Value

MD5

78600bc158479cc9f830aa5091a2e5b2

SHA1

ae23e67395282d4d639a074e38e83194d7830a6d

SHA256

22756db5d14705888e67f6dc0d70bd42e55af29e72dc33511e405139a637c0d7

SHA512

bd64769af08191c2fb79bd332b891c38adf6484d56b211768efadb952b94b666bad30abd484514c2d49420d2c8fd944cc571491f4f04fdac7036cac0aba27434

Summary

Allow an alert to have multiple notifiers, e.g. both Slack and PagerDuty

Change Log

  • Allow an alert to have multiple notifiers, e.g. both Slack and PagerDuty.

  • Bug Fix: Sandbox permissions for the owner of the sandbox.

  • Bug Fix: Bar charts got incorrect height.

  • Bug Fix: HEC ingest of array of numbers fixed.

Humio 1.3.1

Bug Fixes and New Permission Model

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.3.1

Archive

2019-02-08

2020-02-07

1.3.0

No

No

JAR Checksum

Value

MD5

d4a36b05d6937062d63eb86bc4b8c605

SHA1

c1cb90603d98ea824f0b86a8fa1e6d8763023533

SHA256

513759afc48f71d35a23c3ab6bf9bace08737175ab721aef4bb4c658f23ffd72

SHA512

e911929e8e2cbf0bbf0727735d8ce36b265b0f5a664dc1f1e6a70fc36740998dbc217614e5411846cffa123a27d2039d1785228583075947fca4cbe0691b5ebe

Summary

Bug Fixes in addition to a new permission model.

Change Log

  • Bug Fix: LDAP changes being rolled back to allow users to login using just their username again.

Humio 1.3.0

New Permission Model

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.3.0

Archive

2019-02-07

2020-02-07

1.2.0

Yes

Yes

JAR Checksum

Value

MD5

c2c8064b9528569f55bae4809823d688

SHA1

0ca51526a8fb204a6d7f5d98ef3df9b99b9d9bb8

SHA256

0f4b789dfe2a36cab77850f9a2c1aa2c5d6db9f13527760fb58d428ff3bf6edc

SHA512

d6ec65028371383b770fedb57488530a144edc3ec5a684ed829d1997ff4a2bc6d4607a22d100e6729fcf8c3d30b3e480d45cd9975507754e2a891d0bafee43aa

Summary

New permission model

Change Log

  • New permission model used for Role Based Access Control is now in use all the time. Default setup includes the roles member, admin, and eliminator as usual.

  • The config for RBAC has changed (config file has a new name, environment variable names have changed), see Role Based Authentication.

  • Bug Fix: LDAP fix; may require users to login with full user@domain user name, not just user.

  • Bug Fix: Metric of type=HISTOGRAM in the internal “humio-metrics” repo had all values a factor of 10^6 too low.

  • Bug Fix: worldmap function forgot about normalize option.

Humio 1.2.12

Optimizations and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.12

Archive

2019-02-05

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

8e5166154004d10cc532edf628ff9a75

SHA1

52d1c821efb9faa1e2929e37c18d4b31301ba06c

SHA256

27c07d34ab9f3f1b71f4c69bdd6fa416fbb4e64a6c150dd25fef19261b0541da

SHA512

87f05b4ab55a92ed45c3f0b0594a281b2ebf47b13656b69da0e7c698e0ec2676ad7000fd6bb3cca656057931319af27536ca68e290447b610afeffa7efc18645

Summary

Optimizations and Bug Fixes

Change Log

  • Optimizing for many datasources in a repo by removing a bottleneck related for “tag grouping” auto-detection.

  • Improvements to Query monitor

  • Added a timechart of bulk size to built-in dashboard “Humio stats”.

  • Running queries now show only top-1000 queries to avoid overloading the browser in case of many queries.

  • Bug Fix: lowercase function now preserves unmodified fields in the “include=both” case, and no longer modifies “@timezone”.

Humio 1.2.11

Non-Load Balanced Queries, Optimizations and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.11

Archive

2019-01-31

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

abb43dfa8ee8f12402a76a179410176b

SHA1

1a03197336c007c67d50dbee4a10fb9255f6babc

SHA256

31917a8d9b99a7374e84d2992bf4c7abf17e9a584b1a87ad2c0c4b2ef7413563

SHA512

e808107e58221d854235b2eb4b882ce6f7ce607fe5ad7daf6e3d9cebaef34cf2be39530f9f3f90c7e1af3ee3f007c755e7c9f4570712d776b82ac66e8b857d8b

Summary

Support for non-loadbalanced queries, optimizations and Bug Fixes

Change Log

  • New function for parseFixedWidth().

  • When your query matches more than 200 events, you can now scroll further back in time than those 200, “paging” through the older events. This works for any “non-aggregate query”.

  • New “Zoom and pan” buttons to quickly change the search interval: Double the time-span or move the search interval 1/8th of the span to either side.

  • When your load-balancer does not act as “sticky” as described in Cluster Installation, Humio now internally proxies requests to the proper internal node for search requests.

  • Write Humio metrics into the new repo humio-metrics. Any user can query metrics but only for the repos they can search. Looking at metrics that are not repo-specific requires being a member of the humio-metrics repo.

  • Allow any user to query the humio-audit log, but only for the actions of the user. Looking at the actions of others requires being a member of the humio-audit repo.

  • Bug Fix: Changes to desired digest partition to node assignments did not get reflected in other nodes until a restart of the other nodes.

Humio 1.2.10

Non-Load Balanced Queries, Optimizations and Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.10

Archive

2019-01-28

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

9dc2a50e634009d50bca66d3bcfc5f84

SHA1

72e5306849274de3274367e6a681e331103a2b0a

SHA256

06dd50f0aba251dbbc1d26c653e180786319c945c25a35650f98bab376a55340

SHA512

5dfa5517f83781d1a107dc87ae5948ab7d50ce3fb0131d4d17cf0c244badfd4f3e70b7bf7ef0b4d1639c2a579766d0e607b6d9a85de3cf586e3c3af997613928

Summary

Load Balanced Queries, Optimizations and Bug Fixes

Change Log

  • Bug Fix: parseCsv did not handle broken input gracefully.

  • New built-in parser for the popular .NET Serilog logging library.

  • Added HTTP header to support loadbalancing queries. The header Humio-Query-Session is described in Cluster Installation.

  • Improved HEC performance.

Humio 1.2.9

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.9

Archive

2019-01-18

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

9263f70e884f582a3bf29cf33b30dd23

SHA1

7c2ece55d70d8bf0f6a4809259033d42b54a92f7

SHA256

235a22e311557b26a2493c885cc0875df7de0b36e098149271f7230dee1d6e7f

SHA512

ac8f52d1f342b01978744521d6489c1efcaa98f01a678057642ea194ba097c86832d97c12d79e78d4e1aa2ba1db74c48c5b458bea66890f770916b29962e12fd

Summary

Maintenance Build

Change Log

  • Bug Fix: RetentionJob would not delete remaining segments marked for deletion if one delete failed.

  • Delete of queries on the http endpoint now lets the query live for 5 seconds internally, to allow reusing the same query if resubmitted.

Humio 1.2.8

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.8

Archive

2019-01-17

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

988ba57c9b42c57a996e3cca5874e4f8

SHA1

eff65659bcef942f04e32f13882dd89dd592c00b

SHA256

8ea328361f1a1b0d08177696aecc0239e1802caffd971e93ffc2302bc4bb912b

SHA512

d7f7ea99cc6de3b72adb419ffc52095c1ec7c02b9bc436bd73de7998b04429747c660faa2f672d8a8995c574d9321211000c8586eff753a37c7c1505826da8a3

Summary

Maintenance Build

Change Log

  • New function, mostly for use in parsers scope: parseCSV() parses comma-separated fields into columns by name.

  • Better names for the metrics exposed on JMX. They are all in the “com.humio.metrics” package.

  • Support for applying a custom parser to input events from any “beat” ingester by assigning the parser to the ingest token.

  • Bug Fix: Handle HTTP 413 errors when uploading too large files on the files page

  • Bug Fix: Live queries in a cluster where not all servers had digest partitions could lead to events being stuck in the result when they should have been outside the query range at that point int time.

  • Bug Fix: Cloning built-in parsers made them read-only which was not intentional.

  • Config “KAFKA_DELETES_ALLOWED” can be set to “true” to turn on deletes on the ingest queue even when KAFKA_MANAGED_BY_HUMIO=false

Humio 1.2.7

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.7

Archive

2019-01-15

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

204a89d9d15e30118198c14b0776426a

SHA1

f99f0bfc8df24c6bf6df30143c74b70b99ffce55

SHA256

c56ad4cda1ec9a447c4170540e2d8338767333e775152e27a521cf0948aae08e

SHA512

3225863a2801a30b0a9da59bf14bf1c7d5eac14469fa23d7a312cd765e88e8001a981d537e848067caeae656ad04455db5cde8ee484cd7370e1a58e469330961

Summary

Maintenance Build

Change Log

  • Export as CSV allows selecting the fields in the download dialog when the query does no set the fields through table or select.

  • New function eventSize that provides an estimate of the number of bytes being used to represent the event, uncompressed.

  • A new built-in parser for “syslog” in the format of both the old and new RFC, that uses case to auto-detect the format.

  • S3 archiving has completed testing with customers and is no longer considered BETA, but ready for use now.

  • Humio metrics on the Prometheus endpoint now have help texts and use labels where appropriate.

  • Bug Fix: Short time zone names such as “EST” did not work properly in function that accept a time zone name.

  • Bug Fix: enable escape to clear sticky events in all scenarios

  • Bug Fix: A race condition could lead to memory being leaked.

Humio 1.2.6

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.6

Archive

2019-01-11

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

442b0eea2bda0e1e882d793bce5baf4d

SHA1

622fe45e4c3c6ba2c519ce277a4a490cd385b80d

SHA256

517ee1cca7921aa396584589353690dd8e4d236ceae0e285fcf969e0c559c89d

SHA512

6426c8aa972831d898538e5978446ff379dadd76cd36f557b109898fbdc214fc6c4676dcba7847abf8784f1206b5751cc8d732c1334f3bd2ff608411505ac4cd

Summary

Maintenance Build

Change Log

  • Improved detection of alerts that are canceled to get them restarted.

  • Allow both Basic-auth and OAuth on all ingest endpoints. We recommend putting tokens in the password field of the authentication.

  • Bug Fix: Calendar in query interval selector had time zone problems.

  • World map function now accepts the “precision” parameter for the geohash function embedded inside worldmap().

  • Bug Fix: extracting a field from within a tag-field could make the query optimizer fail.

  • Bug Fix: “stats” function (The [] operator for functions) did not pass on the data used to select default widget.

  • S3 archiving: Include all tag keys in generated file names, also those listed in the configuration.

  • Allow GET/HEAD on elastic _bulk emulation API without auth. Some client poll that API before posting event.

  • HEC endpoints now accepts input from Docker Splunk logging driver. You can thus get your docker container logs into Humio using this logging driver. All you need to do is add --log-driver=splunk --log-opt splunk-token=$TOKEN --log-opt splunk-url=https://humioserver to your docker run.

  • Expose Humio metrics as JMX.

  • Expose Humio metrics to Prometheus. The port needs to be configured using the configuration parameter PROMETHEUS_METRICS_PORT.

  • Bug Fix: When using select() and not including @timestamp, that field got included in exported files anyway. Now it gets included when specified as a selected field.

Humio 1.2.5

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.5

Archive

2019-01-09

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

7d419a81a0a59bcfb2dc0b6cc02bbdb3

SHA1

07d793802c31377f8a60ea0bec52a351176ed948

SHA256

419cadb92f32a3c4f8275c5d2b303c979e4f7fbe5c676d6396f6f40710771f9c

SHA512

cbe4a472c820225a4dff2c8145bf485b819172af6b0295a18593c4e90e7b16233bc069af9a2c030bef586bd32f38bbd60fa33b5be2fac798bfe17c4716bc1e7c

Summary

Maintenance Build

Change Log

  • Query performance improved by fixing a bottleneck that was noticeable on CPUs with more than 16 cores.

  • Humio will by default write threaddumps to the file humio-threaddumps.log every 10 seconds. This is configurable using the configuration parameter DUMP_THREADS_SECONDS. Before this was disabled by default.

  • Allow * as fields for lowercase function to allow lower casing all field names and values. Recommended use case is in the ingest pipeline as this is an expensive operation.

  • Added new query functions lower and upper.

  • If the parser ends up setting a timestamp before 1971, or does not set a timestamp, use now as timestamp for the ingested event. Same for timestamps more than 10 seconds into the future.

  • When running with PREFIX_AUTHORIZATION_ENABLED=true Alerts and Shared dashboards now run as the user who saved them, restricted to those prefixes that the users has at the time the query starts.

  • Bug Fix: Audit-logging did not happen for queries using the “/query” endpoint i.e. using the export button in the UI.

  • Timeouts on the http endpoint have been changed from 60s to infinite. This allows exporting from queries that hit very little data, e.g. a live query that receives one event every hour.

  • Basic auth (used mostly on ingest endpoints) now allows putting the token into the password field instead of the username field. Use of the password field is recommended as some software treats the password as secret and the username as public.

  • HEC protocol now accepts data at “/services/collector” url too. And accepts authorization in the form of a “Authorization” header with any realm name, as long as the token is a valid Humio token. This allows using e.g fluentd and other software to ship to Humio using HEC.

  • Bug Fix: Segments with blocks where all timestamps are zero were reported as broken when trying to read them.

Humio 1.2.4

Secondary Storage of Segment Files

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.4

Archive

2019-01-02

2019-12-11

1.2.0

No

Yes

JAR Checksum

Value

MD5

8f00b74da1609381950edf68d769f7e2

SHA1

ed33fa097e5f203b16efcefdd349cdbac9023cf4

SHA256

6a88855fa503b5275b2dec27c8f4d8e0259abd5deba4134416ee3acb4dad4806

SHA512

b888ec3903f91be343df410a56647903fb0763e81b08c0cef0740d64c364b35f8c3cd72ddd1657bb3a794fd3c39aaf5a1453651f9fb44f6439606e1e1aa5f05b

Summary

Secondary storage of segment files

Change Log

  • Secondary storage of segment files. This allows using a “fast” disk primarily, and a “slow” one for older files.

  • HTTP Event Collector out of beta. Endpoint is located at /api/v1/ingest/hec.

  • Bug Fix: When a segment file was deleted while being scheduled in a query, the query would end up being “99%” done and never complete.

  • Performance fix: Running live queries for weeks with a small time span for the bucket size was expensive.

  • Bug Fix: Deleting an ingest listener did not stop the listener.

  • Extended the internal latency measurement to include the time spent in the custom parsers as well.

Humio 1.2.3

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.3

Archive

2018-12-18

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

4f6da960a7c21c65a8625b168504e151

SHA1

62589a92f1a2b9759d970d2a2d828c667c1d1471

SHA256

ed0242a2a159733babc22e912141ced535e2a4721dfd1ec03c80043e9d2c6976

SHA512

9d1c59e90b0220fb000fcf42bc0dfb71c727703e4d948c1d3dd2185354f2699e073f009b5d569e3c324a430cc7f99b8829433946b5303032c4cb122b1a5f7f92

Summary

Maintenance Build

Change Log

  • Default to running queries on only vcores/2 threads.

  • Performance improvement: queries with NOT NotMatching were much slower than the plainfilter NotMatching.

  • Bug Fix: Display of query speed in clustered version was multiplied by (n+1)/n in a n-node cluster.

  • Bug Fix: Widget auto-selection improved.

  • New ingest endpoints without the repo in the path, as the repo is specified by the token for authentication, repo and and parser selection.

Humio 1.2.2

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.2

Archive

2018-12-14

2019-12-11

1.2.0

No

Yes

JAR Checksum

Value

MD5

24df9210b046af907c826c8151885ab4

SHA1

54649576e7e8960552f094a079e19fcaa81dd42b

SHA256

a1c0d3a35759c707eabad6dc459b059e550916328bd6676a76d5acd1d8a2fcbe

SHA512

d68a3f5d6ed53ee52921b1f4d175dcb74b8270618b291a8a04685992f41222a912b31803c7a5da23710dffe5c7dfb729977d5d9e56515e47f6ef9543c2244074

Summary

Maintenance Build

Change Log

  • Bug Fix: “sandbox” did not work properly with PREFIX_AUTHORIZATION_ENABLED=true

  • Configuration change. ALLOW_UNLIMITED_STATE_SIZE has been replaced by MAX_STATE_LIMIT. MAX_STATE_LIMIT limits state size in Humio searches and now allows specifying a number. For example the number of groups in the groupBy function is limited by MAX_STATE_LIMIT.

Humio 1.2.1

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.1

Archive

2018-12-13

2019-12-11

1.2.0

No

No

JAR Checksum

Value

MD5

edc9569eac0a6b53871bbc2d45128841

SHA1

554b0a1c5d98f5eae3a705f6a30677b1a4ba2059

SHA256

2c73145e4c8fdf986ec57f523c19a4184ccded3e3a20b8529169d320d97dfab1

SHA512

21cac90fa422cb78458c07958db8d9ee284831b7ffefbacd75193eacc6ec405c42dc8c18e26b8170d8803d1aee06388209f6fb1753edc613aaf5f390df0672e0

Summary

Maintenance Build

Change Log

  • Improve maximum throughput of a TCP-listener ingest up to 4 times the previous level for a single socket. Maximum throughput can reach 100.000 events/s when testing with 500 bytes/event on localhost. Use more sockets in parallel to achieve higher throughput.

  • Bug Fix: When pushing the query sub-system to the limit with many simultaneous long-running live queries for more than 10 seconds, a query could end up triggering a restart of itself.

  • Bug Fix: Editing a parser with syntax errors did not work.

Humio 1.2.0

Create Parsers using Humio's Search Language

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.2.0

Archive

2018-12-11

2019-12-11

1.2.0

Yes

Yes

JAR Checksum

Value

MD5

8c08fdaf29d88da3508f64dbaaa3b640

SHA1

e940c781a712f4b3c4561557170a2762dfc296f4

SHA256

812a322cba7f784422262f61cc256cfcad91c81f6e3ea28082150307b69b0a5d

SHA512

5e5dfdc312c51751ec9ffd24173add4acfdbbc2fb679924b05bc4b592c7848389b1d5d3b81326e154b97dd688702a23d4a220f897641546abf5248655f89bd7d

Summary

Create parsers using Humio’s search language. Changes to “Backup” layout.

Change Log

  • New parsers. It is now possible to create parsers using Humio’s search syntax. Check out the Creating a Parser documentation. Existing parsers has not been migrated and it is still possible to use the old parsers. We encourage using the new parsers and will automatically migrate old parsers in a future release.

  • parseTimestamp() function has changed signature. The parameter nowIfNone has been removed and a new addErrors introduced. This can break existing searches/alerts/dashboards (but the parameter has not been widely used). See docs parseTimestamp().

  • Blacklist queries. In the administration section of Humio it is now possible to blacklist queries. This can also be done from the Query Monitor page, by clicking a query and then block it in the details section, or using the Query Blacklist page directly.

  • kvParse() function no longer overrides existing fields by default. To override existing fields based on input use: kvParse(override=true). See docs kvParse().

  • The parser overview page now shows parser errors. This is a quick way to detect if parsers are working as expected.

  • The backup feature now stores the copies of the segment files in separate folders for each Humio node. This allows the Humio nodes to delete files that are no longer owned by that node also in the case where all Humio nodes share a shared network drive. This change has the effect that existing backups are no longer valid and cannot be read by this version. Delete any existing backups when upgrading, or reconfigure Humio to use a fresh location for the backups.

  • Bug Fix: In a cluster where any node did not have any digest roles, queries could get polled much too frequently.

Humio 1.1.37

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.37

Archive

2018-12-03

2019-06-21

1.1.0

No

No

JAR Checksum

Value

MD5

4bceede76af7c3bce25ebd5aea43f247

SHA1

45fb2bb7f927ac376c7b79f851c6e15624b0daa8

SHA256

9e021b952271054906c7d0c926ab21ef3a70cb36114819fa860d03827eed77d1

SHA512

dc68309d17ed2815b3bf1219c36ae343eb778356cc07a819a23db046b48f013f65c464e24e1dab90713ce35a1dee6fd21d8f513539a93ddfd5081a5d8995d673

Summary

Maintenance Build

Change Log

  • Bug Fix: Field-extracting using regex did not work in live queries in an implicit AND.

  • Add debug logs for LDAP login.

  • Fix bug in UI when uploading file.

Humio 1.1.36

Role-Based Auth Support for SAML & LDAP

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.36

Archive

2018-11-28

2019-06-21

1.1.0

No

Yes

JAR Checksum

Value

MD5

cb5614ccde77ea9789a0cfb300cd5a16

SHA1

fc269cc45480142120ec11949f89cb2212df60d4

SHA256

b41d9ecf30c02199cb5a3a954da1e80457b643d85622c0790ed9ee6ba1eb7a97

SHA512

8270540462fb03756b02bc6f6d4af37eef7c033c45664b05649c8aaf7484b1ae20ddbe707a6261a4b71c017372b916b835694e16138b6732807db2f42acdf4f9

Summary

Role-based auth support for SAML & LDAP

Change Log

  • Role-based access control is now supported for on-prem when using SAML or LDAP for authentication. See Role Based Authentication.

  • Config variable ~~`AUTO_CREATE_USER_ON_SUCCESSFULL_LOGIN`~~ renamed to (the correctly spelled) AUTO_CREATE_USER_ON_SUCCESSFUL_LOGIN.

  • Set thread priorities on internal threads.

  • Extended session() function to accept an array of function instead of only one.

  • GELF over HTTP support. Note that this format is a good fit for uncommon events, but due to lack of bulk support not efficient for streams with high amounts of traffic. Authentication is required using basic auth with an ingest token (or personal API token, but using that is not recommended).

Humio 1.1.35

Graylog Compatible Ingest Support

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.35

Archive

2018-11-27

2019-06-21

1.1.0

No

No

JAR Checksum

Value

MD5

72a131e4c17781a44b449624dd2c6c5f

SHA1

831ce32e06c543a661e91f3f52ee577db2aaa0d3

SHA256

20a57eb91dbf23a1aef0b6fce605ac238536881b4f4f7a7eb2b178a444797fe9

SHA512

0d148f4a13c104bf70d403ba948f4723074d5cf6e15dd59e69d5f2195f8697f56f6e26146361e21831b35c5b14455c3c644da7718379c3c5e7adeb1f321185d5

Summary

Graylog compatible ingest support.

Change Log

  • Allow ingest in “GELF” v1.1 format. See GELF Payload Specification. Humio supports ingest on using the UDP and UDP chunked encodings, and both may optionally be compressed using ZLIB. (Gzip not supported yet.) TCP is supported as zero-byte-delimited uncompressed.

  • Bug Fix: Alerts did not properly encode all parts of the query in the URL that is sent in the notification.

Humio 1.1.34

Improved LDAP Support

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.34

Archive

2018-11-22

2019-06-21

1.1.0

No

Yes

JAR Checksum

Value

MD5

ab1eafa8442d6ed275c94527ed96ed19

SHA1

7a48b49cba75653d610cc700fab5237707fada44

SHA256

4aa7256991fbc5275ede446402ae9540281bcf39ba8a4503a0510d559ddcd45f

SHA512

2c4b1ff36ee3d4409f0ae142cfd749d1ada4228b4a6c533685ff476093117f3a472ecc8c5b3e7354ab4412406d488488cc6ffb5f4ca905c8bd5144a128925d1a

Summary

Improved LDAP support

Change Log

  • By default users must be added inside Humio before they can log in using external authentication methods like LDAP and SAML. This can be controlled using the configuration flag AUTO_CREATE_USER_ON_SUCCESSFUL_LOGIN=false. If users are auto created in Humio when they successfully login for the first time, the user will not have access to any repositories unless explicitly granted. A new user will only be able to access the users personal sandbox.

  • Bug Fix for match function. In some cases it did not match quoted strings.

Humio 1.1.33

Bug Fix and Digest Performance

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.33

Archive

2018-11-15

2019-06-21

1.1.0

No

No

JAR Checksum

Value

MD5

5a840e455815bf24e87ae39348effcfe

SHA1

af4b4f35e2269622f4caaa37c3cc498029bd17bc

SHA256

85ca4356d4ec798ed19fa36c647701a316b6d6b83bc5d1685741c96e1cbe951c

SHA512

7153862acd7603bc213137e42a1bc28f2ed1d80a057dec7513d8a65b0fdece6e7d87e6145744bbeabdd3bd87966cfb81f507c76b6c4ea8961eaadf239a6524ac

Summary

Bug Fix and digest performance

Change Log

  • Fixed: Parsers did not show the build-in parsers

  • Digest throughput improvements

Humio 1.1.32

stripAnsiCodes() function

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.32

Archive

2018-11-15

2019-06-21

1.1.0

Yes

Yes

JAR Checksum

Value

MD5

d33e3e5efff00f0b1d85d385ea269462

SHA1

4f31157403313e8b17137366b3a8328773f026f5

SHA256

3c1122d4bea20462bbbabcd0dc42650756c7da2dd90c6460d6de304d3c3bf210

SHA512

0e0e0182678ae1b6ce1f46b15a9d2fb2818d3ac625920feca372d024510d3cecef0dd79dcd46a3839e4123211d834d5124cc019cbb43c8d6fea24f075deb52f2

Summary

stripAnsiCodes() function, top on multiple fields and Bug Fixes, default repository query

Change Log

  • top function now support more than one field to group on combination of fields.

  • New stripAnsiCodes function: strips ANSI color codes from a field.

  • New range function: Finds numeric range between the smallest and largest numbers for the specified field over a set of events.

  • Repositories’ default search interval has been replaced with the possibility to choose a default repository query. All default search intervals will be migrated to default queries. A default query can be set by saving a query and checking the “Use as default” checkbox.

  • Added support for Java 11. Humio can now be run with Java 9 or Java 11. Humio’s Docker images are updated to use Java 11 and we encourage people to update to Java 11 and use Azul’s OpenJDK Zulu builds.

  • Bug Fix connecting to Kafka when using the property EXTRA_KAFKA_CONFIGS_FILE.

Humio 1.1.31

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.31

Archive

2018-11-09

2019-06-21

1.1.0

No

No

JAR Checksum

Value

MD5

60e957fae4f61ea8176aa2575546d400

SHA1

eae8ff212e0f53a72a202358510fc91e33a022f3

SHA256

2db5c9571a7c7ea60587ecb96af1b427db7171b9fa8a81a50bf6e80bb51d478e

SHA512

53f21f1352d9df0f7c0e13ab3e41f19b708129065cbbfa2b0c98054b49f6fac1d6ee3a198e56d0a3809f82e32fec9191f02ddc11f8827c8dd186adb1c9a66382

Summary

Reduce latency of incoming events.

Change Log

  • The latency measured from an event arrive at Humio until live queries have been updated with that event has been reduced by approximately 1 second to now be in the 0 - 500 millisecond range.

  • It is now possible to block ingestion in a repository. It can be done from the repository’s settings page.

  • Improved build-in dashboards, allowing them to be shared using share links like any other dashboard.

Humio 1.1.30

Bug Fixes

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.30

Archive

2018-11-04

2019-06-21

1.1.0

No

No

JAR Checksum

Value

MD5

32a2d83501170709e29b4773382ed9da

SHA1

56b88c67f4c46fe9353d52992935340e7654c1d8

SHA256

04c3cc3efdeb71d79865081a9fee70acc0751af27bceb1efb80188ac1fb0a0ca

SHA512

0e6bbedaac7ccec7fbe163ad23522be0cb00bdf391716b75cedab92426bdd4deec864ce6ae8cadf4d0b4e1a23a7f43d611ebbe7023c4f237b34b5b3c295f4d2a

Summary

Bug Fix - ‘Create Parser’ button opened a beta page for creating parsers

Change Log

  • Bug Fix: ‘Create Parser’ button opened a beta page for creating parsers.

  • Bug Fix: Handle clients posting empty bulks of events.

Humio 1.1.29

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.29

Archive

2018-11-02

2019-06-21

1.1.0

No

No

JAR Checksum

Value

MD5

bfd7b069334c3e9fcc3f669ef7108284

SHA1

249dabc85c1d0846dbd92e5c12c2fbcbeaae61ba

SHA256

26071929b87a33ac4ae913521b16e8d9791358a615db84194a6b63e195106329

SHA512

7967a83ba7157b9e22e73a1fa19d69f40bc3269ff27bbd13f367e3f691f5df5ed3a29a3715ca84cad9e3e3b105d6e254545982564e92f635561d13f349961489

Summary

Bug Fixes

Change Log

  • Added config option: QUERY_EXECUTOR_CORES:Int allows setting cores for query engine individually.

  • Bug Fix: Allow ‘.’ in S3 paths.

  • Bug Fix: Live queries could get false sharing of “Eval” results.

Humio 1.1.28

Improved SAML Authentication

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.28

Archive

2018-10-31

2019-06-21

1.1.0

No

Yes

JAR Checksum

Value

MD5

3e64aa4a09bef57eea35d35f1b4fa33e

SHA1

02c468696787e5720abb007ce79976256a8d368c

SHA256

5859b357a306c1acf606a6e5fce75cc28d5891a950a320e3522c25998298d777

SHA512

95b9ff0929f7f80941586311e3f2623f7d8357fdb2ef2b9d537c8f1672a987afcd5dd1bce7873ab9a08f4353b5bbebd7c2bbfc98ff90afd94bbea748c99dd3f4

Summary

Improved SAML authentication and digest performance

Change Log

  • Dashboard searches are kept running for 3 days, when they are not polled. After that they are not kept alive on the server. This is configurable using the config IDLE_POLL_TIME_BEFORE_DASHBOARD_QUERY_IS_CANCELLED_MINUTES. This replaces IDLE_POLL_TIME_BEFORE_LIVE_QUERY_IS_CANCELLED_MINUTES.

  • When zooming to a wider time range on a timechart with a fixed “span” parameter, widen the span and a dd a warning to allow the chart to work instead of failing with “too many bucket”.

  • Performance improvements for digest on systems with many sparse datasources.

  • Bug Fix: Back-pressure on ingest should not be applied to internal log lines, such as the internal debug and audit log entries.

  • Bug Fix: The first search to hit a repository in a cluster with millions of segments would fail while listing those files.

Humio 1.1.27

Back-Pressure on Ingest Overload

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.27

Archive

2018-10-24

2019-06-21

1.1.0

No

No

JAR Checksum

Value

MD5

8517a2486d8c6dcc9219b186c26c2f7f

SHA1

cf1fb05f32d5675cdb3faca53416c0de3faab22c

SHA256

d29498ec6e65c0a38d3c6ba50ef0c6d9c106df32aa96dba237b52d418d8809e3

SHA512

4045bf8dfde298fee12b8f37abc0ea3a0ec37733c47582342450bd59e5b4f7a8a783878926dfe1d2605e9d27fe9bbc98f7fbf907125ce54aa600e88f74ebbb1b

Summary

Back-pressure on ingest overload and Bug Fixes

Change Log

  • When too much data flows into Humio for Humio to keep up, apply back-pressure by responding statuscode 503 and header Retry-After: 300.

  • Many changes internally to prepare for having more than one node in the “Digest rules” for fail-over handling of ingest traffic.

  • Bug Fix: The event list on the search page now correctly resets the widget when a new search is started

  • Bug Fix: The max value of the y-axis of timecharts is now correctly updated on new results

  • Bug Fix: Pagination now works for tables on dashboards

Humio 1.1.26

Maintenance Build

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.26

Archive

2018-10-15

2019-06-21

1.1.0

No

No

JAR Checksum

Value

MD5

38fb6d4e13106b90ee91060def4741a9

SHA1

b196f3f6337b3e5b519ed8e95c694b11ddecda1f

SHA256

4804482761ce478d55d30226790c2ed3ee5fb4266940810663cab39971a394e8

SHA512

f9f6368ad401811ff7d2af18995e5f025822d3a5d8d3f69d5da50a0aa8fcf7cb246168311828dc87a3bef2770700796a46e3f36c0390208085edb2df3f464a36

Summary

Minor Release

Change Log

  • Performance improvement in table, sort and tail especially when using a large limit.

  • Bug Fix: select function did not render results if they did not have @timestamp and @id. (Select is like table but unsorted and allows exporting an unbounded set of events)

  • Bug Fix: session function could miss events in some situations.

  • Bug Fix: Using the field message instead of log (as described in v1.1.25) did not work properly.

Humio 1.1.25

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.25

Archive

2018-10-12

2019-06-21

1.1.0

No

No

Summary

Adds Worldmap and Sankey visualizations and SAML authentication support.

Change Log

  • New visualizations: Worldmap and Sankey.

  • New visualization helper functions geohash, worldmap, sankey.

  • The new visualizations require a change to the CSP. If you have your own CSP, you need to add 'unsafe-eval' to the script-src key.

  • New query syntax: match on a field that eases matching for several cases on a single field.

  • Support using filebeat to ship logs from Helm chart for ingest logs from a Kubernetes cluster. The message can be in the field log or message.

  • The update services widget that “phones home” to update.humio.com can now only be disabled if you have a license installed.

  • Bug Fix: Performance regression in functions table, sort, tail and head that slowed them down a lot when the limit was larger than 100.

  • Bug Fix: S3 archiving now handles grouped tags properly, generating one file for each tag combination also for grouped tags.

  • Bug Fix: Split function could use the timestamp of one event in more of the following events than those that originated in that event.

  • Bug Fix: Importing repositories from another Humio instance has repository ID where repository name was required.

  • Bug Fix: Searching using ... | *foo*** | ... is identical to ... | foo | ... since plain text searches are always substring matches. But the former got turned into a full-string regex match for ^.*foo.*$ which is 10-30 times slower compared to the fast substring search in Humio.

Humio 1.1.24

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.24

Archive

2018-10-05

2019-06-21

1.1.0

No

No

Summary

Maintenance Build

Change Log

  • Reorder query prefixes to execute queries more efficiently. Moves tags to the front of query string to allow better start-of-query datasource filtering.

  • Bug Fix: segments deleted by retention-by-size would sometimes get left behind in global, adding warnings to users searching at intervals including deleted segments.

Humio 1.1.23

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.23

Archive

2018-10-01

2019-06-21

1.1.0

Yes

No

Summary

Update Kafka server version to 2.0.0

Change Log

  • Humio’s Kafka and Zookeeper Docker images have been upgraded to use Kafka 2.0.0. We recommended to keep the update procedure simple and not do a rolling upgrade. Instead shutdown Humio Kafka and Zookeeper. Then fetch the new images and start Zookeeper, Kafka and Humio. For details see Kafka’s documentation for upgrading. (Note: This change was listed in release notes for v1.1.20 even though it was applied only to the kafka client there, and not to the server).

  • The query planner has been improved, so it can more precisely limit which data to search based on tags.

  • Bug Fix: Do not reassign partitions in Kafka when there is already sufficient replicas (Only applied when KAFKA_MANAGED_BY_HUMIO=true, the default).

  • Bug Fix: Do not remove other topic configs in Kafka when setting those needed by humio (Only applied when KAFKA_MANAGED_BY_HUMIO=true, the default).

  • Bug Fix: Handle empty uploaded files.

  • Improved performance of parsers that have (?<@timestamp>\S+) as their timestamp extractor regex.

Humio 1.1.22

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.22

Archive

2018-09-27

2019-06-21

1.1.0

No

No

Summary

Fix Kafka prefix configuration problem. Faster percentiles. Allow globbing when using match().

Change Log

  • Add flag match(..., glob=true|false) allowing the key column of a CSV file to include globbing with *.

  • The key/value parser now (also) considers characters below 0x20 to be separators. Good for e.g. FIX-format messages.

  • Percentile function changed to use 32bit precision floating point making it ~3x faster.

  • Bug Fix: The UI for setting node ID on an ingest listener did not work.

  • Bug Fix: If using Kafka prefix configuration, the server would always assume Kafka has been reset. Releases 1.1.20 introduced this problem.

Humio 1.1.21

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.21

Archive

2018-09-25

2019-06-21

1.1.0

No

No

Summary

Bug fix release.

Change Log

  • “Query Monitor” now also shows cpu time spent in the last 5 seconds.

  • Bug Fix: Timechart on views broke in previous version 1.1.20

  • Bug Fix: The implicit tail(200) that is applied when no aggregate function is in the query input did not sort properly in certain cases.

Humio 1.1.20

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.20

Archive

2018-09-24

2019-06-21

1.1.0

Yes

No

Summary

Use Kafka version 2.0.0

Change Log

  • Added the possibility to add extra Kafka configuration properties to Kafka consumers and producers by pointing to a properties file using EXTRA_KAFKA_CONFIGS_FILE. This makes it possible to connect to a Kafka cluster using SSL and SASL.

  • Humio is upgraded to use the Kafka 2.0 client. It is still possible to connect to a Kafka running version 1.X

  • ~~Humio’s Kafka and Zookeeper Docker images have been upgraded to use Kafka 2.0.0.~~ (Update: See 1.1.23)

Humio 1.1.19

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.19

Archive

2018-09-21

2019-06-21

1.1.0

No

No

Summary

Cluster administration, dashboard clone/export/import and faster startup on large datasets.

Change Log

  • Dashboards can now be copied to other repos and exported and imported as templates.

  • New cluster management actions for reassigning partitions to hosts and moving existing data to other hosts.

  • Auto-nice long running queries, making them take on lower priority compared to younger queries, measured by cputime spent.

  • Generate pretty @display value in split() function.

  • Fix #2263, support for !match().

  • Bug Fix: HUMIO_KAFKA_TOPIC_PREFIX was not applied to all topics used by Humio, only where the name matched global-*".

  • Startup of the server is now much faster on large datasets.

  • Faster response on cluster management and entering the search page.

  • Upgrading to this version requires running at least v1.1.0. If you run an older version, upgrade to v1.1.18, then v1.1.19.

  • Setting INGEST_QUEUE_INITIAL_PARTITIONS in config decides the initial number of partition in the ingest queue. This only has effect when starting a fresh Humio cluster with no existing data.

  • Allow negative index in splitString, which then selects from the end instead of from the start. -1 is the last element.

Humio 1.1.18

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.18

Archive

2018-09-13

2019-06-21

1.1.0

No

No

Summary

Ease using your own Kafka including older versions of Kafka.

Change Log

  • Ease using your own Kafka including older versions of Kafka

  • Set KAFKA_MANAGED_BY_HUMIO=false to stop Humio from increasing the replication of the topics in Kafka.

  • Added MAX_HOURS_SEGMENT_OPEN to the number of hours after which you want a segment closed and a new one started even if it has not filled up. Note that you may want to disable segment merging in this case to preserve these smaller segment files by also setting ENABLE_SEGMENT_MERGING=false

Humio 1.1.17

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.17

Archive

2018-09-10

2019-06-21

1.1.0

No

No

Summary

Show Events Per Second (EPS) when searching.

Change Log

  • Show Events Per Second (EPS) when searching.

  • Improve search performance when adding fields to events.

  • Dashboards can now be copied to other views.

Humio 1.1.16

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.16

Archive

2018-09-06

2019-06-21

1.1.0

Yes

No

Summary

Add CRC to data files. Migrates data to support upcoming features to later serve as a potential roll back point.

Change Log

  • Note! v1.1.15 is able to read the files generated by v1.1.16. Rolling back to version 1.1.14 or earlier is not possible, as those versions cannot read the files that have CRC.

  • Adds CRC32c to the segment file contents.

  • Support CSV downloads. End the query with | table([...]) or | select([...]) to choose columns.

  • New ‘cluster overview’ tab in admin page (this is work in progress, feedback appreciated).

  • Regular expression matching with a ‘plain’ prefix is now faster.

  • Bug Fix. Regular expressions using /.../ syntax sometimes matched incorrectly.

  • Scheduling of queries now take cpu time spent in each into account, allowing new queries to get more execution time than long-running queries.

Humio 1.1.15

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.15

Archive

2018-09-03

2019-06-21

1.1.0

No

No

Summary

Support for setting parsers in our Kubernetes integration and a new parseHexString function.

Change Log

  • Our Helm chart for ingest logs from a Kubernetes cluster now support setting a parser using the pod label humio-parser. More information can be found in our HELM.

  • Updated instructions for configuring the PagerDuty notifier.

  • New function: parseHexString().

  • Bug Fix. Tables now sort globally instead per page.

Humio 1.1.14

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.14

Archive

2018-08-21

2019-06-21

1.1.0

No

No

Summary

Starring alerts and Introduce a displaystring for formatting log strings.

Change Log

  • Starring alerts. Get your favorite alerts to the top of the list.

  • Introduced @displaystring.

  • Improve Netflow parser to handle packets coming out of order.

  • Bug Fix. Slack notifier had the message twice in the request.

Humio 1.1.13

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.13

Archive

2018-08-16

2019-06-21

1.1.0

Yes

No

Summary

Improve LDAP support.

Change Log

  • Enable logging in with LDAP without providing domain name. Domain name can be set as a config using LDAP_DOMAIN_NAME. See LDAP.

  • Enforce an upper bound of the number of fields allowed for one event. The limit is 1000. If an event has too many fields, 1000 are included.

Humio 1.1.12

Major Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.12

Archive

2018-08-15

2019-06-21

1.1.0

Yes

No

Summary

SMTP support for sending emails, new Files UI and support for self-signed certs for ldap.

Change Log

  • SMTP support for sending emails

  • New Files UI. Possible to manage files for use in the lookup() function.

  • Add new functions now(), transpose() and drop() to the query language.

  • LDAPS can use a self-signed certificate through config.

  • Bug Fix: Segment file replication did not (re-)fetch a segment file if the file was missing on disk while the “global” state claimed it was present.

  • Fix bug with tail() inside groupby(), bucket(), [...] or stats() expressions.

  • Add operators >, <, >=, <=, and % to eval expressions.

  • Eliminate the backtics syntax from eval, the same effect can be obtained with transpose().

  • LDAP users must now be added with their domain. For example add user@myorganisation.com (instead of just user). Existing users are migrated by the system, so no actions are required.

Humio 1.1.11

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.11

Archive

2018-08-03

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Bug Fix: “Export to file” did not work in the UI.

  • Performance improvement in the internal logging to the Humio dataspace.

  • Eliminated a race condition in the ingest pipeline that could drop data in overload conditions.

Humio 1.1.10

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.10

Archive

2018-08-02

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Now using Google’s RE2/j as the default, not the JDK’s. Can be configured using USE_JAVA_REGEX=true|false.

  • Autosharding now happens after tag grouping. Improves performance in case where some datasources are slow and others very fast when those are grouped.

Humio 1.1.9

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.9

Archive

2018-07-30

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Bug Fix. When encountering a broken segment file, let the server start and ignore the broken file.

Humio 1.1.8

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.8

Archive

2018-07-26

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Improve handling color codes in Humio’s built in key-value parser

  • Bug Fix. Autosharded tags should not get tag-grouped.

Humio 1.1.7

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.7

Archive

2018-07-05

2019-06-21

1.1.0

Yes

No

Summary

Minor Release

Change Log

  • Datasource autosharding is now able to reduce the number of shards.

  • New function match() is like lookup() but better suited for filtering.

  • Bug Fix. sort() with multiple fields was not stable for missing values.

  • Bug Fix. Fix split() to allow splitting JSON arrays of simple values.

  • Bug Fix. Remove race condition that could create duplicate events on restart.

  • Verify Java version requirement on startup.

  • Update embedded GeoLite2 database to 20180703 version.

Humio 1.1.6

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.6

Archive

2018-07-04

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Improved datasource autosharding to be less eager.

  • Restructured documentation.

  • Bug Fix. Log rotation of Humio’s own log files. Files was not deleted, but now they are.

  • Bug Fix. Viewing details of a logline while doing a live query did not pause the stream. This resulted in the details view being closed when the logline went out of scope.

Humio 1.1.5

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.5

Archive

2018-06-28

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Remove supervisors from the Docker image humio/humio-core

Humio 1.1.4

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.4

Archive

2018-06-28

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Bug Fix. Repo admins that are allowed to delete data can now delete datasources.

Humio 1.1.3

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.3

Archive

2018-06-27

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Rename a widget on dashboard directly from the dashboard itself.

  • Supporting links in tables.

  • Fix memory problem when streaming events using the query endpoint.

Humio 1.1.2

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.2

Archive

2018-06-25

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • Fix clock on dashboards page.

  • Fix creating the sandbox dataspace in the signup flow.

  • Allow fields in alert webhooks.

Humio 1.1.1

Minor Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.1

Archive

2018-06-21

2019-06-21

1.1.0

No

No

Summary

Minor Release

Change Log

  • fix fullscreen mode for readonly dashboards

Humio 1.1.0

Major Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.1.0

Archive

2018-06-21

2019-06-21

1.1.0

Yes

No

Summary

Minor Release

Change Log

  • Dataspaces has been split into views and repositories. This allows searching across multiple repositories and adds support for fine grained access permissions. Read the introduction in this blogpost and check out the Repositories documentation.

  • It is not possible to rollback to previous versions when upgrading. Backup Global data by copying the file /data/humio-data/global-data-snapshot.json. Then it will be possible to rollback (with the possibility of loosing new datasources, users, dashboards etc that was created while running this version).

  • Amazon AMI available in the Amazon marketplace.

  • Added documentation for Kafka Connect.

  • Improved Fluentbit integration to better support ingesting logs from Kubernetes.

  • Added query function parseUrl().

  • Moved some of the edit options from the dashboard list to the dashboard itself.

Humio 1.0.69

Hotfix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.0.69

Archive

2018-06-12

2019-06-12

1.1.0

No

No

Summary

Hotfix Release

Change Log

  • Bug Fix: Canceling a query in 1.0.68 would consume resources, blocking worker threads for a long time. Please upgrade.

Humio 1.0.68

Regular Update Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.0.68

Archive

2018-06-11

2019-06-11

1.1.0

No

Yes

Summary

Regular update release.

Change Log

  • Bug Fix: deeplinking did not work in combination with having to log in.

  • Ingest queue replication factor in Kafka is now by default set to 2 (was 1). If it is currently set to 1 Humio will increase it to 2. The configuration parameter INGEST_QUEUE_REPLICATION_FACTOR can be used to control the replication factor.

  • Changes to Humio’s logging. Humio now logs to 2 files /data/logs/humio-debug.log and /data/logs/humio_std_out.log. Std out has become less noisy and is mostly error logging. This is only relevant for on-prem installations.

Humio 1.0.67

Regular Update Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.0.67

Archive

2018-06-01

2019-06-01

1.1.0

No

No

Summary

Regular update release.

Change Log

  • Support for GDPR: Hardened audit logging

  • Improved search performance when reading data from spinning disk

Humio 1.0.66

Minor Update Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.0.66

Archive

2018-05-23

2019-05-23

1.1.0

No

No

Summary

Minor update release.

Change Log

  • Added “prune replicas” method on on-premises HTTP API to remove extra copies when reducing replica count in cluster.

  • Increased default thread pool sizes a bit, but still only 1/4 of what the were before 1.0.65

Humio 1.0.65

Minor Update Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.0.65

Archive

2018-05-22

2019-05-22

1.1.0

No

No

Summary

Minor update release.

Change Log

  • Fixed bug: Importing a dataspace from another Humio instance did not handle multi-node cluster properly

  • Search performance improvement: Reduce GC-pressure from reading files.

  • Reduced default thread pool sizes.

Humio 1.0.64