Not released.

Advance Warning

The following items are due to change in a future release.

• Security

  Starting from LogScale version 1.237, support for insecure ldap connections will be removed. Self-Hosted customers using LDAP will only be able to use ldaps secure connections.

• User Interface

  From version 1.225.0, LogScale will enforce a new limit of 10 labels that can be added or removed in bulk for assets such as dashboards, actions, alerts and scheduled searches.

  Labels will also have a character limit of 60.

  Existing assets that violate these newly imposed limits will continue to work until they are updated - users will then be forced to remove or reduce their labels to meet the requirement.

• Queries

  Due to various upcoming changes to LogScale and the recently introduced regex engine, the following regex features will be removed in version 1.225:

  • Octal notation

  • Quantification of unquantifiable constructs

  Octal notation is being removed due to logic application difficulties and its tendency to make typographical errors easier to overlook.

  Here is an example of a common octal notation issue:

  regex

  /10\.26.\122\.128/

  In this example, \122 is interpreted as the octal escape for R rather than the intended literal 122. Similarly, the . matches not just the punctuation itself but also any single character except for new lines.

  Any construction of \x where x is a number from 1 to 9 will always be interpreted as a backreference to a capture group. If the corresponding capture group does not exist, it will be an error.

  Quantification of unquantifiable constructs is being removed due to lack of appropriate semantic logic, leading to redundancy and errors.

  Unquantifiable constructs being removed include:

  • ^ (the start of string/start of line)

  • $ (the end of string/end of line)

  • ?= (a positive lookahead)

  • ?! (a negative lookahead)

  • ?<= (a positive lookbehind)

  • <?<!> (a negative lookbehind)

  • \b (a word boundary)

  • \B (a non-word boundary)

  For example, the end-of-text construct $* only has meaning for a limited number of occurrences. There can never be more than one occurrence of the end of the text at any given position, making elements like $ redundant.

  A common pitfall that causes this warning is when users copy and paste a glob pattern like *abc* in as a regex, but delimit the regex with start of text and end of text anchors:

  regex

  /^*abc*$/

  The proper configuration should look like this:

  regex

  /abc/

  For more information, see LogScale Regular Expression Engine V2.

Deprecation

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

The following GraphQL APIs are deprecated and will be removed in version 1.225 or later:

In the updateSettings mutation, these input arguments are deprecated:

• isPackageDocsMessageDismissed

• isDarkModeMessageDismissed

• isResizableQueryFieldMessageDismissed

On the UserSettings type, these fields are deprecated:

• isPackageDocsMessageDismissed

• isDarkModeMessageDismissed

Note

The deprecated input arguments will have no effect, and the deprecated fields will always return true until their removal.

The userId parameter for the updateDashboardToken GraphQL mutation has been deprecated and will be removed in version 1.273.

The EXTRA_KAFKA_CONFIGS_FILE configuration variable has been deprecated and planned to be removed no earlier than version 1.225.0. For more information, see RN Issue.

rdns() has been deprecated and will be removed in version 1.249. Use reverseDns() as an alternative function.

The Secondary Storage feature is now deprecated and will be removed in LogScale 1.231.0.

The Bucket Storage feature provides superior functionality for storing rarely queried data in cheaper storage while keeping frequently queried data in hot storage (fast and expensive). For more information, see Bucket Storage.

Please contact LogScale support for any concerns about this deprecation.

Behavior Changes

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

• Configuration

  The environment variable VALIDATE_BLOCK_CRCS_BEFORE_UPLOAD has been removed to guarantee segment validation before uploading segment files to bucket storage. Previously, this environment variable was set to true by default, allowing users to disable this functionality by disabling checking block CRCs prior to upload.

New features and improvements

Fixed in this release

Known Issues

Improvement

Recent Package Updates

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