Added the new fileDownloadParallelism setting for FDR feeds to download files from the same SQS message in parallel. See Adjust Polling Nodes Per Feed for all the details.

Parsing JSON arrays in drill-down context menus no longer adds a trailing dot to the prefix field name.

Add Falcon LogScale announcement on login and signup pages.

Contextual drill-down menus for field interactions have been introduced, see Field Interactions. In particular:

Interactions on JSON data now enabled for JSON arrays in the Event List.

Humio is now a Falcon product. The Humio owl logo and icons are therefore replaced by beautiful falcons.

Following its name change, mentions of Humio have been changed to Falcon LogScale.

The Single Value widget has updated properties:

Change Humio logo to Falcon LogScale on login and signup pages.

Self-hosted only: the old implementation of how alert queries are run has been removed. As a consequence, the dynamic configuration UseLegacyAlertJob has also been removed.

Added two new message templates to actions, {query_start_s} and {query_end_s}. See Message Templates and Variables for details.

Added new createDashboardFromTemplateV2 mutation with input parameters aligned with the rest of the create from template mutations.

JSON in Log Line and JSON formats columns in Event List widgets now have fields underlined on hover and are clickable. This allows drill-downs and copying values easily.

QueryAPI — Added staticMetaData property to QueryJobStartedResult. At the moment it only contains the property executionMode, which can be used to communicate hints about the way the backend executes the query to the front-end.

QueryAPI — executionModeHint renamed to executionMode.

Introduced new valid array syntax in array:contains() and array:regex() functions:

Improved the format():

See the format() reference documentation page for all the above mentioned updates on the supported formatting syntax.

Added a new ingest endpoint for receiving metrics and traces via OpenTelemetry OTLP/http. See OpenTelemetry for all the details.

New background task that runs at startup. It verifies the checksums present in local segment files, traversing the most recently updated segment files on the local disk, using the timestamps they have when Humio status. If a file has invalid checksum it will be renamed to crc-error.X where X is the ID of the segment. An error will be logged as well.

Add an additional validation check when uploading files to S3-like bucket storage. Humio will now perform a HEAD request for the file's final location in the bucket to verify that the upload succeeded.

Created new test function for event forwarders, which takes as input an event forwarder configuration and tests whether it is possible to connect to the Kafka server. The current test function which takes an ID as input and tests an existing event forwarder by ID, is now marked as deprecated.

Added a new dynamic config UndersizedMergingRetentionPercentage, with a default value of 20. This configuration value is used when selecting undersized segments to merge, this setting controls how wide a time span can be merged together.

The setting is interpreted as a percentage of the repository's retention by time setting. A reasonable range is 0 through to 90.

Added use of the HTTP Proxy Client Configuration, if configured, in a lot of places.

When selecting a parser test case, the selected test case is highlighted in the UI, so you can see what is selected.

Empty datasource directories will be now removed from the local file system while starting the server.

Add a script in the tarball distribution's bin directory to check the execution environment, checking common permission issues and other requirements for an environment suitable for running Logscale.

It's now possible to expand multiple bell notifications.

Use latest version of Java 17 in Docker images.

Change missing @timestamp field to give a warning instead of an error in functions tail(), head(), bucket(), and timeChart().

Bug fixed in Scatter Chart widget tooltip, so that the description of the actual point only is shown in the tooltip when hovering the mouse over one point, instead of multiple points.

Fixed a bug where query result containing no valid results was handled incorrectly in visualisation.

Fixed an issue where NaN values could cause groupBy() queries to fail.

Fixed an issue where match() would sometimes give errors when ignoreCase=true and events contained latin1 encoded characters.

Fixed a bug where the selfJoin() function would not apply the postfilter parameter.

When selecting a parser test case, the selected test case is highlighted in the UI, so you can see what is selected.

It is now possible for a user to use the same personal invite token after the user has been transferred to another organization.

Fixed an issue where nothing was displayed on the average ingest chart in case only one datapoint is present.

When a host is removed from global, a job tries to clean up any references to it from other places in global, such as segments. Fixed a bug in this job that meant it didn't clean up references on segments that were tombstoned but not yet gone from global. This could block cleanup of those segments.

Fix an issue causing a content-length check for bucket uploads to fail when encryption was enabled. The content-length check is not normally enabled, so this should only affect clusters that have disabled ETag-based validation.

Fix an issue that could cause event redaction tasks to fail to complete, if a segment having events redacted was deleted due to retention.

Fixed a regression causing a reflective method lookup to fail when Humio is running on a Java prior to 13.

OIDC known issue preventing login:

if you are running LogScale self-hosted, this version will not work in an environment where you are Authenticating with OpenID Connect and you use an HTTP Proxy, but you do not want to call OpenIDConnect through the HTTP Proxy.

Please do not upgrade to this version if this is the case — upgrade to Falcon LogScale 1.63.4 Stable (2023-02-01) and Falcon LogScale 1.70.1 Stable (2023-02-01) instead, where this issue has been fixed.