Published on 2019-03-15 00:00:00

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

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