Falcon LogScale 1.122.0 GA (2024-01-23)
Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Config. Changes? |
---|---|---|---|---|---|---|---|
1.122.0 | GA | 2024-01-23 | Cloud | 2025-03-01 | No | 1.70.0 | No |
Available for download two days after release.
Bug fixes and updates.
Advance Warning
The following items are due to change in a future release.
Installation and Deployment
We aim to stop publishing the
jar
distribution of LogScale (e.g.server-1.117.jar
) as of LogScale version 1.130.0.Users deploying via Docker images are not affected. Users deploying on bare metal should ensure they deploy the
tar
artifact, and not thejar
artifact.A migration guide for bare metal deployments is available at How-To: Migrating from server.jar to Launcher Startup.
We intend to drop support for Java 17, making Java 21 the minimum. We plan to make this change in March 2024.
Deprecation
Items that have been deprecated and may be removed in a future release.
The assetType GraphQL field on
Alert
,Dashboard
,Parser
,SavedQuery
andViewInteraction
datatypes has been deprecated and will be removed in version 1.136 of LogScale.In the GraphQL API, the
ChangeTriggersAndAction
enum value for both thePermission
andViewAction
enum is now deprecated and will be removed in version 1.136 of LogScale.The
humio
Docker image is deprecated in favor ofhumio-core
.humio
is no longer considered suitable for production use, as it runs Kafka and Zookeeper on the same host as LogScale, which our deployment guidelines no longer recommend. The final release ofhumio
Docker image will be in version 1.130.0.The new
humio-single-node-demo
image is an all-in-one container suitable for quick and easy demonstration setups, but which is entirely unsupported for production use.For more information, see Installing Using Containers.
In the GraphQL API, the name argument to the parser field on the
Repository
datatype has been deprecated and will be removed in version 1.136 of LogScale.
New features and improvements
UI Changes
Time zone data has been updated to IANA 2023d.
Deletion of a file that is actively used by live queries will now stop those queries.
For more information, see Exporting or Deleting a File.
Automation and Alerts
The following changes affects the UI for Standard Alerts:
A minimum time window of 1 minute is introduced, since anything smaller will not produce reliable results. Any existing standard alert with a time window smaller than 1 minute will not run, instead an error notification will be shown.
It is no longer possible to specify the time window and the throttle period in milliseconds. Any existing standard alerts with a time window or throttle period specified in milliseconds will have it rounded to the nearest second.
When saving the alert, the query window is automatically changed to the largest unit in the Relative Time Syntax that can represent it. For example
24h
is changed to1d
and60s
is changed to1m
.
Configuration
New dynamic configurations have been added:
defaultDigestReplicationFactor
dynamic configuration defaults to2
if the value is not explicitly set and there is more than 1 node in the cluster performing digest.If necessary, a different default can be explicitly set using the
DEFAULT_DIGEST_REPLICATION_FACTOR
environment variable.defaultSegmentReplicationFactor
dynamic configuration defaults to2
if the value is not explicitly set, unless there is only 1 node in the cluster storing segments, or ifUSING_EPHEMERAL_DISKS
environment variable is set totrue
.If necessary, a different default can be explicitly set using the
DEFAULT_SEGMENT_REPLICATION_FACTOR
environment variable.
Dashboards and Widgets
A series of improvements has been added to the dashboard layout experience:
New widgets will be added in the topmost available space
When you drag widgets up, all widgets in the same column will move together
Improved experience when swapping the order of widgets (horizontally or vertically)
Queries
Live query cost metrics corrections:
livequeries-rate
metric has changed from long to double.livequeries-rate-canceled-due-to-digest-delay
metric has changed from long to double.
For more information, see Node-Level Metrics.