Falcon LogScale 1.89.0 Preview (2023-05-11)

VersionTypeRelease DateAvailabilityEnd of SupportSecurity UpdatesUpgrades FromJDK CompatibilityReq. Data MigrationConfig. Changes
1.89.0Preview2023-05-11Cloud, On-Prem2024-07-31No1.44.011NoNo

Bug fixes and updates.

Advanced Warning

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

  • Installation and Deployment

    • Support for running on Java 11, 12, 13, 14, 15 and 16 will be removed by the end of September 2023.

Improvements, new features and functionality

  • Automation and Alerts

    • The Alert and Scheduled Search jobs no longer produce logs about specific alerts or scheduled searches in the humio repository. The logs are still sent to the humio-activity repository, which in normal setup is also ingested into the humio repository. So before, the logs would normally be duplicated, now they are not. The only difference between the two types of logs, is that the logs from the humio-activity repository all have loglevel equal to INFO. You can use the severity field instead to distinguish between the severity of the logs.

  • GraphQL API

    • Mutations enableAlert and disableAlert have been added for enabling and disabling an alert without changing other fields.

  • Configuration

    • Automatic rebalancing of existing segments onto cluster nodes has been enabled.

      Manual editing of the segment partition table is no longer supported. The table is no longer displayed in the Cluster Administration UI.

      The segments will be distributed onto cluster nodes based on the following node-level settings:

      • ZONE defines a node's zone. The balancing logic will attempt to distribute segment replicas across as many zones as possible.

      • The target disk usage percentage determines how much of the node disk we will consider usable for storing segment data during a rebalance. The balancing logic will attempt to keep nodes equally full, while considering the node zone and segment replication factor. This can be configured via GraphQL using the setTargetDiskUsagePercentage mutation. The default value is 90.

      • Nodes with a NODE_ROLES setting that excludes segment storage will not receive segments as part of a rebalance.

  • Log Collector

    • Added a new test status for configurations, which allows you to try out a configuration on one or more instances before it's published.

      For more information, see Testing a Remote Configuration.

  • Other

    • Degrade and deprecate some REST and GraphQL APIs due to the introduction of AutomaticSegmentDistribution and AutomaticDigesterDistribution. The deprecated elements will be removed in a future release, once the upgrade compatibility with version 1.88.0 is dropped. We expect this to be no earlier than September 2023.

      The following REST endpoints are deprecated, as they no longer have an effect and return meaningless results:

      • api/v1/clusterconfig/segments/prune-replicas

      • api/v1/clusterconfig/segments/distribute-evenly

      • api/v1/clusterconfig/segments/distribute-evenly-reshuffle-all

      • api/v1/clusterconfig/segments/distribute-evenly-to-host

      • api/v1/clusterconfig/segments/distribute-evenly-from-host

      • api/v1/clusterconfig/segments/partitions

      • api/v1/clusterconfig/segments/setdefaults

      • api/v1/clusterconfig/segments/set-replication-defaults

      • api/v1/clusterconfig/partitions/setdefaults

      • api/v1/clusterconfig/ingestpartitions/distribute-evenly-from-host

      • api/v1/clusterconfig/ingestpartitions/setdefaults

      • api/v1/clusterconfig/ingestpartitions (POST only, GET will continue to work)

      The following GraphQL mutations are deprecated, as they no longer have an effect and return meaningless results:

      • startDataRedistribution

      • updateStoragePartitionScheme

      The IngestPartitionScheme mutation is not deprecated, but as it updates state that is overwritten by automation, we recommend against using it — it exists solely to serve as a debugging tool.

      The following GraphQL fields on the cluster object are deprecated, and return meaningless values:

      • ingestPartitionsWarnings

      • suggestedIngestPartitions

      • storagePartitions

      • storagePartitionsWarnings

      • suggestedStoragePartitions

      • storageDivergence

      • reapply_targetSize

      The following fields in the return value of the api/v1/clusterconfig/segments/segment-stats endpoint are deprecated and degraded to always be O:

      • reapply_targetBytes

      • reapply_targetSegments

      • reapply_inboundBytes

      • reapply_inboundSegments

    • The following cluster management features are now enabled:

      • AutomaticJobDistribution

      • AutomaticDigesterDistribution

      • AutomaticSegmentDistribution

      For more information, see Digest Rules.

Bug Fixes

  • UI Changes

    • An error for lacking permissions that appeared when updating the organization settings has been fixed. Now, if you have permissions to view the Organization Settings page, you can also update information on it.

    • The Search page would reload when using the browser's history navigation buttons. This issue has now been fixed.

  • Automation and Alerts

    • The throttle field would be empty when editing an Alert; this issue has now been fixed.

    • Fixed an issue where clicking the Inspect link in Alert notifications would land on a missing page.

  • Dashboards and Widgets

    • The following issues have been fixed on dashboards:

      • A dashboard would sometimes be perceived as changed on the server even though it was not.

      • Discard unsaved changes would appear when creating and applying new parameters.

  • Functions

    • The rename() function would drop the field, if the field and as arguments were identical; this issue has now been fixed.

  • Other

    • An edge case has been fixed where query workers could fail to include minisegments if the minisegments were merged at a bad time, causing queries to be missing the data in those segments.

    • Fixed an issue that could cause segments to appear missing in queries, due to the presence of deleted minisegments with the same target as live minisegments.

    • Some merged segments could temporarily be missing from query results right after an ephemeral node reboot. This issue has been fixed.