Falcon LogScale 1.247.0 GA (2026-06-30)

Version?Type?Release Date?Availability?End of SupportSecurity UpdatesUpgrades From?Downgrades To?Config. Changes?
1.247.0GA2026-06-30

Cloud

Next LTSNo1.177.01.177.0No

Hide file download links

Show file download links

Bug fixes and updates

Advance Warning

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

  • Installation and Deployment

    • We are decommissioning the the Nexus server used to host Java-based LogScale installation binaries, with a tentative decommission date of August 14, 2026. To download Java-based LogScale installers, please send a request to logscalesuccess@crowdstrike.com to obtain a username & API token, which are required to download from our new distribution platform.

Removed

Items that have been removed as of this release.

GraphQL API

  • For the GraphQL datatype User, both the deprecated GraphQL field permissionsPage and the datatype UserPermissionsPage have been removed due to disuse. To obtain similar results, users should apply the permissions field instead.

    For more information, see User .

Configuration

  • The ability to configure the number of rows in a table via the environment variable NUMBER_OF_ROWS_IN_OWNER_HOSTS_TABLE has been removed, and replaced in favor of correlation with how segments are distributed across nodes. The default value for the number of rows is 10,000.

Metrics and Monitoring

  • The humio-metrics repository metric ingest-request-time-ms has been removed due to disuse.

Deprecation

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

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

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

Fixed in this release

  • User Interface

    • An issue has been fixed that was causing Unicode-based control characters to be missing from the Event List.

  • Queries

    • Fixed an issue where a rare race condition occurring during query hand-over could cause failure during rolling restarts for static queries with defineTable() dependencies.

    • An issue has been fixed where queries with large join() function subquery results could cause nodes to crash during query submission from the query coordinator to the worker node.

  • Metrics and Monitoring

    • An issue with the query debug log fields userUtilizationPercentage and orgUtilizationPercentage has been fixed. These fields were showing incorrect values when multiple queries were running concurrently for a given user or organization.

Known Issues

  • Storage

    • For clusters using secondary storage where the primary storage on some nodes in the cluster may be getting filled (that is, the storage usage on the primary disk is halfway between PRIMARY_STORAGE_PERCENTAGE and PRIMARY_STORAGE_MAX_FILL_PERCENTAGE), those nodes may fail to transfer segments from other nodes. The failure will be indicated by the error java.nio.file.AtomicMoveNotSupportedException with message "Invalid cross-device link".

      This does not corrupt data or cause data loss, but will prevent the cluster from being fully healthy, and could also prevent data from reaching adequate replication.

Improvement

  • Queries

    • To make cluster upgrades less disruptive, the query state cache can now be reused when a cluster gets upgraded.

  • Other

    • The threads used for query mapping on worker nodes have been renamed. Previously, the naming convention was query-(vhost), where (vhost) was the virtual host of the node. The new naming convention is now (prefix)query-mapper, where (prefix) is the value of HUMIO_THREADNAME_PREFIX.