Humio Server 1.13.0 Preview (2020-06-24)

VersionTypeRelease DateAvailabilityEnd of SupportSecurity UpdatesUpgrades FromJDK CompatibilityReq. Data MigrationConfig. Changes
1.13.0Preview2020-06-24Cloud, On-Prem2021-08-26No1.12.011NoNo
JAR ChecksumValue
MD5c9dca247bec107fa41c6ec1fe5bb5d3b
SHA151e898057d10d80e6a50ab86ab5bedf71d348f5b
SHA256b5c21c0028f1d61104821e5d4749b15cea7e208aa9bfb9307a9b10e077f6f7b6
SHA5125b148d8d8fd8680fd61c642bda45f7dba2cb0aa21efeb2752b02a6467a7063036f1b31ea347816ecdcba676cf1d9d199e409620bd6b1acd2cc2fdeff78767375

Many improvements, including some related to free-text searching, load balancing queries, TLS support, IPlocation() query function, and some configuration changes.

Bug Fixes

  • Configuration

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

    • Added support for WebIdentityTokenCredentialsProvider on AWS.

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

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

    • Internal communication in a Humio installation can now be encrypted using TLS. See TLS.

Improvement

  • Configuration

    • 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 Configuration Settings and Manual Cluster Deployment.

  • Other

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

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

    • TLS encrypts communication using TLS to/from Zookeeper, Kafka, and other Humio nodes.

    • Humio can now balance and reuse existing queries internally in the cluster. Load balancer configuration to achieve this is no longer needed. See Configuration Settings and Manual Cluster Deployment.