Storage

• The full JDK has been removed from the Docker images, leaving only the bundled JDK that is part of LogScale release tarballs.

GraphQL API

• The enabledFeatures() query has been removed from GraphQL schema. Use featureFlags() query instead.

GraphQL API

• The enabledFeatures() query has been removed from GraphQL schema. Use featureFlags() query instead.

GraphQL API

• Removed the Asset interface type in GraphQL that Alert, Dashboard, Parser, SavedQuery and ViewInteraction datatypes implemented. It was not used as a type for any field. All fields from the Asset interface type are still present in the implementing types.

Configuration

• The DEFAULT_PARTITION_COUNT configuration parameter has been removed, as it was unused by the system due to earlier changes to partition handling.

Configuration

• The DEFAULT_PARTITION_COUNT configuration parameter has been removed, as it was unused by the system due to earlier changes to partition handling.

GraphQL API

• Removed the Asset interface type in GraphQL that Alert, Dashboard, Parser, SavedQuery and ViewInteraction datatypes implemented. It was not used as a type for any field. All fields from the Asset interface type are still present in the implementing types.

API

• The deprecated REST endpoints api/v1/dataspaces/(id)/deleteevents and /api/v1/repositories/(id)/deleteevents have been removed. You can use the redactEvents GraphQL mutation and query instead.

  For more information, see redactEvents().

API

• The deprecated REST endpoints api/v1/dataspaces/(id)/deleteevents and /api/v1/repositories/(id)/deleteevents have been removed. You can use the redactEvents GraphQL mutation and query instead.

  For more information, see redactEvents().

API

• The deprecated REST endpoints api/v1/dataspaces/(id)/deleteevents and /api/v1/repositories/(id)/deleteevents have been removed. You can use the redactEvents GraphQL mutation and query instead.

  For more information, see redactEvents().

Installation and Deployment

• All Zookeeper-related functionality for LogScale was deprecated in December 2022, and is now removed:

  • Removed the Zookeeper status page from the User Interface

  • Removed the Zookeeper related GraphQL mutations

  • Removed the migration support for node IDs created by Zookeeper, as we no longer support upgrading from version prior to 1.70.

  Depending on your chosen Kafka deployment, ZooKeeper may still be required to support Kafka.

• Running on Java 11, 12, 13, 14, 15 and 16 is no longer supported. The minimum supported Java version is 17 starting from this LogScale release.

Storage

• The unused humio-backup symlink inside Docker containers has been removed.

GraphQL API

• The deprecated client mutation ID concept is now being removed from the GraphQL API:

  • Removed the clientMutationId argument for a lot of mutations.

  • Removed the clientMutationId field from the returned type for a lot of mutations.

  • Renamed the ClientMutationID datatype, that was returned from some mutations to BooleanResultType datatype. Removed the clientMutationId field on the returned type and replaced it by a boolean field named result.

• Most deprecated queries, mutations and fields have now been removed from the GraphQL API.

Configuration

• Some deprecated configuration variables have now been removed:

  • S3_STORAGE_UPLOAD_CONCURRENCY

  • GCP_STORAGE_UPLOAD_CONCURRENCY

  • S3_STORAGE_DOWNLOAD_CONCURRENCY

  • GCP_STORAGE_DOWNLOAD_CONCURRENCY

  They have been replaced by S3_STORAGE_CONCURRENCY and GCP_STORAGE_CONCURRENCY settings that internally handle rate-limiting responses from the bucket provider.

Storage

• The unused humio-backup symlink inside Docker containers has been removed.

Configuration

• Some deprecated configuration variables have now been removed:

  • S3_STORAGE_UPLOAD_CONCURRENCY

  • GCP_STORAGE_UPLOAD_CONCURRENCY

  • S3_STORAGE_DOWNLOAD_CONCURRENCY

  • GCP_STORAGE_DOWNLOAD_CONCURRENCY

  They have been replaced by S3_STORAGE_CONCURRENCY and GCP_STORAGE_CONCURRENCY settings that internally handle rate-limiting responses from the bucket provider.

Installation and Deployment

• All Zookeeper-related functionality for LogScale was deprecated in December 2022, and is now removed:

  • Removed the Zookeeper status page from the User Interface

  • Removed the Zookeeper related GraphQL mutations

  • Removed the migration support for node IDs created by Zookeeper, as we no longer support upgrading from version prior to 1.70.

  Depending on your chosen Kafka deployment, ZooKeeper may still be required to support Kafka.

GraphQL API

• The deprecated client mutation ID concept is now being removed from the GraphQL API:

  • Removed the clientMutationId argument for a lot of mutations.

  • Removed the clientMutationId field from the returned type for a lot of mutations.

  • Renamed the ClientMutationID datatype, that was returned from some mutations to BooleanResultType datatype. Removed the clientMutationId field on the returned type and replaced it by a boolean field named result.

• Most deprecated queries, mutations and fields have now been removed from the GraphQL API.

Installation and Deployment

• Running on Java 11, 12, 13, 14, 15 and 16 is no longer supported. The minimum supported Java version is 17 starting from this LogScale release.

GraphQL API

• The deprecated RegistryPackage datatype has been deleted, along with the deprecated mutations and fields using it:

  • installPackageFromRegistry mutation

  • updatePackageFromRegistry mutation

  • package in the Searchdomain datatype

GraphQL API

• The deprecated RegistryPackage datatype has been deleted, along with the deprecated mutations and fields using it:

  • installPackageFromRegistry mutation

  • updatePackageFromRegistry mutation

  • package in the Searchdomain datatype

API

• 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/partitions/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

API

• 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/partitions/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

Automation and Alerts

• The deprecated REST Alert API has been removed.

Other

• The deprecated REST Action API endpoint for testing actions has been removed.

API

• Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.

API

• Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.

Installation and Deployment

• Deprecated feature removal: the file-based backup feature was deprecated in 1.42.0 and is now removed from Humio. The following configs are no longer supported and will do nothing if set:

  • BACKUP_NAME

  • BACKUP_DIR

  • BACKUP_KEY

  The DELETE_BACKUP_AFTER_MILLIS config is still supported, as it is used for configuring the delay between a file being marked for deletion in Humio, and that file being removed from bucket storage.

Installation and Deployment

• Deprecated feature removal: the file-based backup feature was deprecated in 1.42.0 and is now removed from Humio. The following configs are no longer supported and will do nothing if set:

  • BACKUP_NAME

  • BACKUP_DIR

  • BACKUP_KEY

  The DELETE_BACKUP_AFTER_MILLIS config is still supported, as it is used for configuring the delay between a file being marked for deletion in Humio, and that file being removed from bucket storage.

API

• The deprecated REST API for actions has been removed, except for the endpoint for testing an action.

• The deprecated REST API for parsers has been removed.

API

• The deprecated REST API for parsers has been removed.

Installation and Deployment

• Remove the following feature flags and their usage: EnterpriseLogin, OidcDynamicIdpProviders, UsagePage, RequestToActivity, CommunityNewDemoData.

API

• The deprecated REST API for actions has been removed, except for the endpoint for testing an action.

GraphQL API

• Deprecated argument repositoryName was removed from Mutation.updateParser field.

• Deprecated argument name was removed from Mutation.updateParser field.

Other

• The deprecated built-in parser bro-json has been deleted. It has been replaced by the parser zeek-json.

• The deprecated built-in parser json-for-notifier has been deleted. It has been replaced by the parser json-for-action.