Humio Server 1.5.21 Archive (2019-07-04)
| Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Config. Changes? |
|---|---|---|---|---|---|---|---|
| 1.5.21 | Archive | 2019-07-04 | Cloud | 2020-11-30 | No | 1.5.8 | No |
Available for download two days after release.
Hide file hashes
| JAR Checksum | Value |
|---|---|
| MD5 | 3e69e9568f9def1fe56c9772266e529e |
| SHA1 | 17a1f945b825bb6220aa6cf4cf1d4675420578ac |
| SHA256 | 84550bd4f356c57e37055b34f5a0fc00c25a20e08faa2d6a0f8843e029550932 |
| SHA512 | dcbf18ea92afa7f5c0cbf1f41835a948e3aa0a6b2e303d1c40d8c2c8bd9c9084186e73c1a2aa76221381bf6f66872b7708e994243969273344e28fcb73b7db1c |
Maintenance Build
Fixed in this release
Summary
If an events gets
@error=truein the ingest pipeline (including in the parser) it will also get#error=trueas 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.
Functions
New 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 acase) to explicitly drop an event while parsing it when it does not match the required format.