Download: https://repo.humio.com/repository/maven-releases/com/humio/server/1.131.2/server-1.131.2.tar.gz

Hide file hashes

Show file hashes

These notes include entries from the following previous releases: 1.131.1, 1.131.1

Bug fixes and updates.

Removed

Items that have been removed as of this release.

GraphQL API

The enabledFeatures() query has been removed from GraphQL schema. Use featureFlags() query instead.

Deprecation

Items that have been deprecated and may be removed in a future release.

In the GraphQL API, the ChangeTriggersAndAction enum value for both the Permission and ViewAction enum is now deprecated and will be removed in version 1.136 of LogScale.

In the GraphQL API, the name argument to the parser field on the Repository datatype has been deprecated and will be removed in version 1.136 of LogScale.

We are deprecating the humio/kafka and humio/zookeeper Docker images due to low use. The planned final release for these images will be with LogScale 1.148.0.

Better alternatives are available going forward. We recommend the following:

• If your cluster is deployed on Kubernetes: STRIMZI

• If your cluster is deployed to AWS: MSK

If you still require humio/kafka or humio/zookeeper for needs that cannot be covered by these alternatives, please contact Support and share your concerns.

The QUERY_COORDINATOR environment variable is deprecated. To control whether a node should be allowed to be a query coordinator, use the query node task instead. Node tasks can be assigned and unassigned at runtime using the assignTasks() and unassignTasks() GraphQL mutations respectively, or controlled using the INITIAL_DISABLED_NODE_TASKS environment variable.

For more information, see INITIAL_DISABLED_NODE_TASKS.

The following GraphQL queries and mutations for interacting with parsers are deprecated and scheduled for removal in version 1.142.

• The deprecated createParser() mutation is replaced by createParserV2() . The differences between the old and new mutation are:

  • testData input field is replaced by testCases, which can contain more data than the old tests could. This includes adding assertions to the output of a test. These assertions are not displayed in the UI yet. To emulate the old API, you can take the old test string and put it in the ParserTestEventInput inside the ParserTestCaseInput, and they will behave the same as before.

  • fieldsToBeRemovedBeforeParsing can now be specified as part of the parser creation.

  • force field is renamed to allowOverwritingExistingParser.

  • sourceCode field is renamed to script.

  • tagFields field is renamed to fieldsToTag.

  • languageVersion is no longer an enum, but a LanguageVersionInputType instead.

  • The mutation returns a Parser, instead of a Parser wrapped in an object.

  • The mutation fails when a parser has more than 2,000 test cases, or the test input in a single test case exceeds 40,000 characters.

• The deprecated removeParser() mutation is replaced by deleteParser(). The difference between the old and new mutation is:

  • The mutation returns boolean to represent success or failure, instead of a Parser wrapped in an object.

• The deprecated testParser() mutation is replaced by testParserV2() . The differences between the old and new mutation are:

  • The test cases are now structured types, instead of just being strings. To emulate the old API, take the test string and put it in the ParserTestEventInput inside the ParserTestCaseInput, and they will behave the same as before.

  • The new test cases can contain assertions about the contents of the output.

  • The mutation output is significantly different from before, as it provides more detailed information on how a test case has failed.

  • The mutation now accepts both a language version and list of fields to be removed before parsing.

  • The parserScript field is renamed to script.

  • The tagFields field is renamed to fieldsToTag.

• The deprecated updateParser() mutation is replaced by updateParserV2() where more extensive test cases can be set. Continuing to use the previous API may result in test information on parsers being lost. To ensure information is not unintentionally erased, please migrate away from the deprecated APIs for both reading and updating parser test cases and use updateParserV2() instead. The differences between the previous and the new mutation are:

  • testData input field is replaced by testCases, which can contain more data than the old tests could. This includes adding assertions to the output of a test. These assertions are not displayed in the UI yet. To emulate the old API, you can take the old test string and put it in the ParserTestEventInput inside the ParserTestCaseInput, and they will behave the same as before.

  • sourceCode field, used to updating the parser script, is changed to the script field, which takes a UpdateParserScriptInput object. This updates the parser script and the language version together.

  • tagFields field is renamed to fieldsToTag.

  • The languageVersion is located inside the UpdateParserScriptInput object, and is no longer an enum, but a LanguageVersionInputType instead.

  • The repositoryName and id fields are now correctly marked as mandatory in the schema. Previously this wasn't the case, even though the mutation would fail without them.

  • The mutation returns a Parser, instead of a Parser wrapped in an object.

  • The old mutation had a bug where it would overwrite the languageVersion with a default value in some cases, which is fixed in the new one.

  • The mutation fails when a parser has more than 2,000 test cases, or the test input in a single test case exceeds 40,000 characters.

On the Parser type:

• testData field is deprecated and replaced by testCases.

• sourceCode field is deprecated and replaced by script.

• tagFields field is deprecated and replaced by fieldsToTag.

For more information, see DeleteParserInput , LanguageVersionInputType , createParserV2() , testParserV2() , updateParserV2() , Parser .

The assetType GraphQL field on Alert, Dashboard, Parser, SavedQuery and ViewInteraction datatypes has been deprecated and will be removed in version 1.136 of LogScale.

The any argument to the type parameter of sort() and table() has been deprecated and will be removed in version 1.142.

Warnings prompts will be shown in queries that fall into either of these two cases:

• If you are explicitly supplying an any argument, please either simply remove both the parameter and the argument, for example change sort(..., type=any) to sort(...) or supply the argument for type that corresponds to your data.

• If you are sorting hexadecimal values by their equivalent numerical values, please change the argument of type parameter to hex e.g. sort(..., type=hex).

In all other cases, no action is needed.

The new default value for sort() and table() will be number. Both functions will fall back to lexicographical ordering for values that cannot be understood as the provided argument for type.

Behavior Changes

Scripts or environment which make use of these tools should be checked and updated for the new configuration:

• Security

  DNS caches are now invalidated after 60 seconds instead of never. To override this behavior, set the security policy networkaddress.cache.ttl in the security manager of the JRE (see Java Networking Properties).

• Ingestion

  It is no longer possible to delete a parser that is being used in an ingest feed. The parser must first be removed from the ingest feed.

  For more information, see Delete an Ingest Feed.

Upgrades

Changes that may occur or be required during an upgrade.

• Installation and Deployment

  The minimum required LogScale version to upgrade from has been raised to 1.106, in order to remove some workarounds for compatibility with old versions.

New features and improvements

Fixed in this release

Early Access

Improvement

Recent Package Updates

The following LogScale packages have been updated within the last month.