Falcon LogScale 1.264.0 GA (2026-10-27)
| Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Downgrades To? | Config. Changes? |
|---|---|---|---|---|---|---|---|---|
| 1.264.0 | GA | 2026-10-27 | Cloud | Next LTS | No | 1.177.0 | 1.177.0 | No |
Hide file download links
Download
Use docker pull humio/humio-core:1.264.0 to download the latest version
Bug fixes and updates
Advance Warning
The following items are due to change in a future release.
GraphQL API
The mutation deleteFeatureFlag will be removed from the code in LTS 1.270. It is replaced by resetFeature.
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:
Fleet Management
The feature flag
FleetInstallTokenExpiryhas been enabled. Default and sensor installation tokens now expire after 30 days. Custom enrollment tokens are enforced with a maximum expiry of 180 days. Existing custom tokens that exceed this limit have 180 days applied from the time of this update.Functions
The function
readPersistedAggregation()is now the only supported way to read data from a Persisted Aggregation Repository. This restriction is enforced across all query paths.
Upgrades
Changes that may occur or be required during an upgrade.
Security
The base Docker image has been updated to remove compromised eMudhra CA certificates.
Compromised eMudhra CA certificates have been removed from the bundled JRE trust store.
New features and improvements
User Interface
A query formatter is now available in the Query Editor. Formatting normalizes indentation and line breaks, and inserts line breaks where applicable when a line becomes too long. When text is selected, formatting applies only within the selection.
The keyboard shortcut is Shift+Alt+F on Windows and command+⌥ option+F on macOS.
Fixed in this release
Storage
An issue has been fixed where searches could silently miss events after their segment closed, with no error or warning. This occurred when a parser built a field value from text at the end of @rawstring followed by text from the beginning of another field, such as @timezone.
For example, a parser that stores @timezone as
Zand ts as2026-09-29T12:58:42Zcould have those events missed by a search forts="2026-09-29T12:58:42Z"after the segment closed. Whether an event was missed depended on which other events were stored alongside it, however the events themselves were stored correctly.The fix applies to newly written data. Segments written before this fix retain the issue until their hash filter files are regenerated or the segments age out.
An issue has been fixed where
httponlyand ingest nodes never stored lookup tables in their table disk cache, delaying queries that use lookup files. These nodes now only use up to 10% of available disk space for the table cache by default.Cache size is configurable with the dynamic configuration parameter
TableCacheMaxStorageFractionForIngestAndHttpOnly.
Ingestion
An issue has been fixed where non-finite floating-point values like positive infinity, negative infinity, and NaN resulted in invalid JSON when ingested through Open Telemetry Protocol (OTLP). Now these values produce the strings
Infinity,-Infinity, andNaNrespectively, following the ProtoJSON format for representing protobuf as JSON.
Queries
Two corner case issues have been fixed where an invalid regular expression could produce an internal validation error instead of a descriptive error message such as Unknown escape sequence.
An issue has been fixed where query handover during upgrades could fail when upgrading from a version earlier than 1.263.
An issue has been fixed where
match()functions with cross-view file references using thefile://syntax did not work in multi-cluster search queries. For example,match(file="file://otherView:lookup.csv", ...)now works correctly when the query runs across federated clusters.
Functions
An issue has been fixed where a missing
tagorviewparameter in the functionreadPersistedAggregation()returned an InternalErrorDuringFunctionValidation error instead of a MissingRequiredArgument error.A regression introduced in version 1.261 has been fixed where the function
selectLast()discarded fields with an empty string ("") as their value.
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
Administration and Management
The GraphQL mutation redactEvents() now emits a log line when a redaction job ends. The log entry includes how long the job took and the reason it ended.
GraphQL API
The GraphQL query analyzeQuery() now supports the argument parser, enabling analysis of parser queries.
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.
Ingestion
Memory allocations during
gzipanddeflatedecompression have been reduced by eliminating unnecessary copies of input buffers.The default request timeout for HTTP endpoints that handle file uploads has been increased to 10 minutes to prevent failures during large file uploads.
Queries
Query reuse checks during submission now timeout after 5 seconds, ensuring the check does not run longer than the total time allowed for the submission.
Fleet Management
Users without
changepermissions for Fleet Management now see a read-only version of the Config Editor page and a read-only Group Details dialog.The ability for the Fleet Management configuration editor to test configuration drafts on selected collector instances before publish has been restored. Publishing a tested draft is now completed from the configuration editor rather than from the test status page.
Recent Package Updates
The following LogScale packages have been updated within the last month.
Package Changes
cisco/ios has been updated to v1.12.1.
Fixed timestamp parsing for syslog messages with a leading dot before the timestamp (e.g., .Oct 13 11:48:38 PDT) by updating the regex pattern to optionally strip the leading dot before extracting the timestamp with timezone
For more information, see Package cisco/ios Release Notes.
fortinet/fortimail has been updated to v2.0.1.
Updated ECS version to 9.5.0
Updated CPS version to 1.2.0
Enhanced timestamp parsing to support timezone-aware formats using Vendor.log.tz field
Fixed regex pattern for email error matching to remove unintended empty match case
For more information, see Package fortinet/fortimail Release Notes.
aws/guardduty has been updated to v2.0.0.
Added dataset-based event categorization: GuardDuty findings are assigned event.dataset = guardduty.finding with event.category = threat and event.type = indicator; non-finding events (notifications) are assigned event.dataset = guardduty.notification with event.category = configuration and event.type = info
Added support for parsing Vendor.lastUpdatedAt (milliseconds epoch) as an alternative timestamp source when Vendor.updatedAt is not present
Updated rule.name regex extraction to use a conditional case block to safely handle events where rule.name is not set
Updated ECS version to 9.5.0
Updated CPS version to 1.2.0
For more information, see Package aws/guardduty Release Notes.
cisco/ise has been updated to v2.1.0.
Added support for relayed syslog logs with double-header format (logs relayed through a syslog aggregator)
Added fallback pattern for non-ISE or malformed logs
Updated ECS version to 9.5.0
Fixed condition syntax for AcctReply-Status outcome determination (AND keyword added)
Fixed splitString function call to use named field parameter
Updated getfield calls to use correct getField casing
Added user.domain := lower(user.domain) for consistent domain normalization
Fixed event.type for event code 80006 (Change Of Authorization Request) from change to info
Fixed event.type for event code 80014 (EndPoint purge event) from deletion to end
Fixed event.type for event code 80006 (CISE_RADIUS_Accounting CoA) from change to info
Minor code formatting and indentation improvements
For more information, see Package cisco/ise Release Notes.
cisco/firepower has been updated to v2.2.0.
Added support for FTD EMBLEM format logs with no hostname and extra context segment in the message identifier (e.g., %FTD--4-419002, %FTD-bridge-6-110002)
Added new regex pattern to handle EMBLEM syslog format: <priority>:timestamp: %IDENTIFIER: message
Updated message identifier regex to support optional context segment in facility name (e.g., FTD-session, FTD-bridge) and handle double-dash separators before severity code
For more information, see Package cisco/firepower Release Notes.
f5networks/bigip has been updated to v3.1.2.
Updated test case data
For more information, see Package f5networks/bigip Release Notes.
microsoft/windows-dns-debug has been updated to v1.5.3.
Updated ThreadID regex pattern from [A-Z0-9]{4} to [A-Z0-9]{3,6} across all case branches to support thread IDs of varying lengths
Applied lower() function to Vendor.RemoteIP when assigning server.address and client.address to ensure consistent lowercase IP address formatting
For more information, see Package microsoft/windows-dns-debug Release Notes.