Humio Server 1.5.1 Archive (2019-03-22)
| Version | Type | Release Date | End of Support | Upgrades From | JDK Compatibility | Data Migration | Config. Changes |
|---|---|---|---|---|---|---|---|
| 1.5.1 | Archive | 2019-03-22 | 2019-11-19 | 1.4.x | 11 | No | No |
| JAR Checksum | Value |
|---|---|
| MD5 | 669f2e0e026ac5ce1ada07221cbd2397 |
| SHA1 | 9157d3100b8c35d1c36ef03323aa1431de11b0d4 |
| SHA256 | 846f0de0235cf4835e5da75853d4fbc069ad6d0fb2c74bafda3a0d471e1041c7 |
| SHA512 | 5e27430929861a3ef0c3aea3accc88d7b57b8ac133d87dd1757cbc8ed88cb3914a93592c368886eed2b938c576d81099ee97fa60a79118fb4f6d120060dbb705 |
The default regex engine has been replaced.
Bug Fixes
Summary
No owls were hurt in the production of this release.
Kill query or blacklist query was not always killed on all nodes.
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.csvfiles up to 1 million lines. The limit for exact match state size can be set usingEXACT_MATCH_LIMIT=.0.0.Timechart more efficient in the backend, better supporting more than 1 series.