Falcon LogScale 1.253.0 GA (2026-08-11)
| Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Downgrades To? | Config. Changes? |
|---|---|---|---|---|---|---|---|---|
| 1.253.0 | GA | 2026-08-11 | Cloud | Next LTS | No | 1.177.0 | 1.177.0 | No |
Hide file download links
Download
Use docker pull humio/humio-core:1.253.0 to download the latest version
Bug fixes and updates
Breaking Changes
The following items create a breaking change in the behavior, response or operation of this release.
Functions
LogScale LTS version 1.258 will include a breaking change to subquery semantics for the
worldMap()andsankey()functions. Result fields will no longer be automatically detected, and results must be assigned to a specific field - magnitude forworldMap()and weight forsankey()respectively.This change avoids unpredictable behavior in sub-queries, and allows further development on related systems. The following is an example of a query that is impacted by this change:
logscaleworldMap(lat=lat,lon=lon,magnitude={ w_squared := w*w | sum(w_squared) | magnitude := math:sqrt(_sum) })Currently, the query will be interpreted as:
logscaleworldMap(lat=lat,lon=lon,magnitude={ w_squared := w*w | magnitude := sum(w_squared) })From version 1.258, the
math:sqrtpart of the query will no longer be discarded.
Advance Warning
The following items are due to change in a future release.
Documentation
Our documentation homepage, functionality, and content will undergo a series of improvements before the end of August 2026. As the volume of content on the site has grown significantly, we recognize that finding the right information can be challenging. These changes are designed to improve navigation, make content easier to find, and provide clearer distinctions between content areas.
Functionality and Navigation
New Default Homepage โ Improved navigation and organization to help you find information more quickly. The existing legacy homepage will remain available.
Curated Content Pages โ Topic-specific pages that provide key resources tailored to different areas of the documentation. Each page includes:
Search scoped to that specific content area
Highlights of new and recently updated pages
Guided Workflow Pages โ Step-by-step, page-by-page guides to help you learn about specific areas of LogScale.
Bookmark Groups โ Organize bookmarks into custom groups to create your own categorized link collections.
Page Watching and Notifications โ Monitor pages and content for changes, so you're always aware of updates to the content you use most.
Custom Homepage โ Set a Curated Content page as your homepage, so visiting library.humio.com takes you directly to your preferred content area.
Content Improvements
New CrowdStrike Query Language (CQL) Manual โ A standalone manual covering:
Query structure and execution context
Internal data representation
Datatypes used in queries and functions
Function types, input and output values, and related functions
Common query patterns organized by use case and challenge
Guides for translating SQL to CQL
New Getting Data Out Manual โ Covers the different ways to extract information from LogScale, including APIs, the search interface, dashboards, and automation.
New Getting Data In Manual โ Covers the methods, tools, and integrations available for ingesting data into LogScale.
New Administration Manuals โ Separate, dedicated manuals for Self-Hosted and Cloud customers.
We will provide updates as each improvement becomes available โ we welcome your feedback as the changes roll out.
API
Starting in version 1.258, the
queryjobsendpoint will always use pagination, even when no pagination arguments have been given. When no arguments are provided, the endpoint will return the maximum page size and an offset of 0. Unless the dynamic configuration parameterQueryResultRowCountLimithas been raised from its default value, this will initially be the entire result.All clients should begin transitioning to use the paginated polling method ahead of version 1.258.
Deprecation
Items that have been deprecated and may be removed in a future release.
The GraphQL field meta has been deprecated and now requires authentication. It will be completely removed in LogScale 1.304. To achieve similar results, use the loginInfo and clusterConfig fields instead.
To temporarily opt out of the authentication requirement, the feature flag
UnauthenticatedMetacan be enabled.The userId parameter for the updateDashboardToken GraphQL mutation has been deprecated and will be removed in version 1.273.
Behavior Changes
Scripts or environment which make use of these tools should be checked and updated for the new configuration:
GraphQL API
After an organization is soft deleted using the removeOrganization mutation, you can now only call the following mutations on that organization:
recoverOrganization โ Restores the organization to visible state.
rollbackOrganization โ Fully deletes the organization under certain conditions and permissions.
Previously, you could call any mutation on a soft-deleted organization.
Upgrades
Changes that may occur or be required during an upgrade.
Security
Apache Log4j has been updated to version 2.25.5 to address a medium severity Common Vulnerabilities and Exposures (CVE) item.
Bouncy Castle Java dependencies have been upgraded to version 1.85.
New features and improvements
Dashboards and Widgets
Shared dashboard links now support specifying a time zone, allowing recipients to view data in the intended time zone rather than their own local time.
Fixed in this release
Storage
An issue has been fixed where the environment variable
GCP_STORAGE_ENDPOINT_BASEwas not being used for requests to Google Cloud Storage (GCS).Note
With this release, configured clusters will begin using this value for all GCS storage requests.
Fixed an issue where segment and auxiliary file downloads could leak files in a temporary directory.
Ingestion
Fixed an issue where parsers with a zero-length/empty test case could be saved successfully, resulting in a non-specific error when queried using LogScale's GraphQL API via the LogScale GUI (v1.219.1).
In the event this occurs, the user will be notified with the error Test case #X has no text or consists only of white spaces, with
Xdefining which test case contains the error.
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_PERCENTAGEandPRIMARY_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
User Interface
The selected event panel in the Parser Editor is now resizable, allowing users to adjust its height by clicking and dragging.
GraphQL API
The GraphQL datatype ScheduledReport now exposes the field createdInfo, which contains structured creation metadata. Data points include author and timestamp, which is consistent with other asset types such as filter alerts, dashboards, and parsers.
The existing fields createdBy and creationDate are now deprecated and will be removed in version 1.306. Migration to the createdInfo field is recommended, as it provides richer author information (user, token, and/or system) alongside the creation timestamp.
Existing scheduled reports are automatically migrated, no action is required.
Configuration
A minimum limit of 4 GB has been added for the default value of the dynamic configuration parameter
MaxTableForQuerySizeBytes.When a configuration file contains invalid YAML, the button on the configuration editor page is now disabled to prevent publishing invalid configurations.
Queries
The full set of nested dependencies for a query is now sent as part of the query result, and is located in the filesUsed field. This enables nested dependences to appear as table tabs in the UI.
Other
Just-In-Time (JIT) logs from the Java Virtual Machine (JVM) have been disabled by default due to disuse and cost. LogScale will now run without them.
To continue including them, users can add the following JVM option using the environment variable
JVM_LOG_DIRif defining a custom log path:javaXlog:jit*=debug:file=$JVM_LOG_DIR/jit_humio.log:time,tags:filecount=5,filesize=1024000If not defining a custom log path, use the default path
logs.