Falcon LogScale 1.213.0 GA (2025-11-04)
| Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Downgrades To? | Config. Changes? |
|---|---|---|---|---|---|---|---|---|
| 1.213.0 | GA | 2025-11-04 | Cloud | Next LTS | No | 1.150.0 | 1.177.0 | No |
Available for download two days after release.
Hide file download links
Download
Use docker pull humio/humio-core:1.213.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
Renamed parameter
caseInsensitiveintext:editDistance()andtext:editDistanceAsArray()toignoreCasefor consistency with other functions.
Removed
Items that have been removed as of this release.
GraphQL API
Removed deprecated GraphQL elements:
Mutations:
addStarToAlertV2
removeStarFromAlertV2
addStarToScheduledSearch
removeStarFromScheduledSearch
Fields:
Alert.isStarred
ScheduledSearch.isStarred
UserSettings.starredAlerts
The GraphQL enum value
GraphQlDirectivesAmountLimitfrom enumDynamicConfighas also been removed.Metrics and Monitoring
Removed the deprecated metric datasource-count, which was responsible for continuously reporting the number of datasources per repository.
Repository datasource information is still available in the following ways:
When new datasources are created and deleted, that information is available to users via datasource logs.
Users can also obtain the datasource count using the query
GET api/v1/repositories/$DATASPACEto view a current list of datasources for a given repository.For more information, see Repository and View Settings, Datasources, Ingestion: Ingest Phase.
Deprecation
Items that have been deprecated and may be removed in a future release.
The
EXTRA_KAFKA_CONFIGS_FILEconfiguration 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. UsereverseDns()as an alternative function.
Behavior Changes
Scripts or environment which make use of these tools should be checked and updated for the new configuration:
Dashboards and Widgets
Removed the support email link (logscalesupport@crowdstrike.com) from scheduled report email footers.
Metrics and Monitoring
The internal monitoring jobs that used to query the internal humio repository for metrics now query the humio-metrics repository instead.
To support this, the default value of
SEARCH_PIPELINE_MONITOR_QUERYhas been changed to#kind=logs | count()for clusters without metrics in the LogScale repository.
Upgrades
Changes that may occur or be required during an upgrade.
Installation and Deployment
Upgraded the bundled Java Development Kit (JDK) to Java 25.0.1.
For this upgrade, users should be aware that systems configured with Transparent Huge Pages (THP) mode as
madvise, the option-XX:+UseTransparentHugePagesdoes not enable huge pages when running with the default garbage collecter G1. To address this, the following workaround is available:java# echo always > /sys/kernel/mm/transparent_hugepage/enabled
New features and improvements
API
Added the parameter
dataspaceIdto the Missing Segments API to allow deletion of all missing segments in a specific dataspace.
Fixed in this release
API
A file's HTTP PATCH endpoint could get stuck while reading new data by imposing size restrictions and ensuring the stream is read properly using Pekko sinks. This issue has now been fixed.
Dashboards and Widgets
Shared dashboards containing widgets using anchored time points (for example:
calendar: 1w@wfor last week) would fail authorization and fail to display dashboard data. This issue has now been fixed.
Queries
Fixed an issue where the internal polling frequency of subqueries could result in slower result display.
Functions
The
parseTimestamp()function would cause an internal server error when used outside parsers and given format strings with insufficient date information. This issue has now been fixed.The serialization protocol in the
defineTable()function caused query failure. This issue has now been fixed.