Published on 2019-09-25 00:00:00

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

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