Removed Features
This page lists features that have been removed from the product, organized by version number.
Falcon LogScale 1.207.0 GA (2025-09-23)
GraphQL API
Removed the deprecated GraphQL field isValidFilterAlertQuery on the type
queryAnalysis
returned from the queryAnalysis GraphQL query.
Falcon LogScale 1.201.2 LTS (2025-10-01)
Storage
Removed the ingest request backpressure mechanism introduced in 1.115. This mechanism throttled ingest requests on nodes running digest work while experiencing event latency. The implementation prevented clusters from properly using Kafka as a buffer for event backlogs. Additionaly, it hid the existence of backlogs from administrators by delaying events on shippers rather than in Kafka where they are visible to LogScale.
Administrators are advised to either:
Size nodes to handle temporary ingest rate spikes without falling behind on digest.
Run separate ingest and digest nodes to prevent ingest spikes from consuming capacity needed for digest work.
This change also removes the following dynamic configurations:
Configuration
Removed the following deprecated environment variables:
JOIN_ENABLED
SELFJOIN_ENABLED
WINDOW_ENABLED
SERIES_ENABLED
Falcon LogScale 1.201.1 LTS (2025-09-02)
Storage
Removed the ingest request backpressure mechanism introduced in 1.115. This mechanism throttled ingest requests on nodes running digest work while experiencing event latency. The implementation prevented clusters from properly using Kafka as a buffer for event backlogs. Additionaly, it hid the existence of backlogs from administrators by delaying events on shippers rather than in Kafka where they are visible to LogScale.
Administrators are advised to either:
Size nodes to handle temporary ingest rate spikes without falling behind on digest.
Run separate ingest and digest nodes to prevent ingest spikes from consuming capacity needed for digest work.
This change also removes the following dynamic configurations:
Configuration
Removed the following deprecated environment variables:
JOIN_ENABLED
SELFJOIN_ENABLED
WINDOW_ENABLED
SERIES_ENABLED
Falcon LogScale 1.201.0 GA (2025-08-12)
GraphQL API
Removed the deprecated field lastScheduledSearch on the GraphQL mutation ScheduledSearch.
Falcon LogScale 1.200.0 GA (2025-08-05)
Storage
Removed the ingest request backpressure mechanism introduced in 1.115. This mechanism throttled ingest requests on nodes running digest work while experiencing event latency. The implementation prevented clusters from properly using Kafka as a buffer for event backlogs. Additionaly, it hid the existence of backlogs from administrators by delaying events on shippers rather than in Kafka where they are visible to LogScale.
Administrators are advised to either:
Size nodes to handle temporary ingest rate spikes without falling behind on digest.
Run separate ingest and digest nodes to prevent ingest spikes from consuming capacity needed for digest work.
This change also removes the following dynamic configurations:
Falcon LogScale 1.198.0 GA (2025-07-22)
Configuration
Removed the following deprecated environment variables:
JOIN_ENABLED
SELFJOIN_ENABLED
WINDOW_ENABLED
SERIES_ENABLED
Falcon LogScale 1.195.1 LTS (2025-07-22)
Configuration
Removed server compatibility checks from multi-cluster searches. These checks became obsolete due to some internal implementation changes occurred in past versions. The new behavior is described at Multi-Cluster Compatibility Across Versions.
Additional related changes:
Removed the
UNSAFE_RELAX_FEDERATED_PROTOCOL_VERSION_CHECK
environment variable.Deprecated the remoteServerCompatVersion field in the
RemoteClusterConnectionStatus
type (returned by the checkRemoteClusterConnection() GraphQL query).Will remove the remoteServerCompatVersion field no earlier than version 1.207, following the
ShortTerm
API stability deprecation policy.The
QueryBacktrackingLimit
feature flag has been removed. Use theQueryBacktrackingLimit
dynamic configuration to adjust the limit.Functions
As previously announced in RN Issue, the following functions can no longer be used after the first aggregate function:
.
For example, this query is no longer valid:
Invalid Example for Demonstration - DO NOT USElogscalegroupBy(class) | eventSize()
These functions can still be used before the first aggregate function:
logscaleeventSize() | tail(200)
This change is necessary as these functions require access to original events, which are not available post-aggregation.
Free-text search is no longer supported after the first aggregate function (as previously announced in RN Issue). For example, this query is no longer supported:
logscale Syntaxtail(200) | "Lorem ipsum dolor"
You can still search for strings in specific fields after aggregation:
logscale Syntaxtail(200) | msg="Lorem ipsum dolor"
Free-text search before the first aggregate function remains supported:
logscale"Lorem ipsum dolor" | tail(200)
Falcon LogScale 1.195.0 GA (2025-07-01)
Configuration
Removed server compatibility checks from multi-cluster searches. These checks became obsolete due to some internal implementation changes occurred in past versions. The new behavior is described at Multi-Cluster Compatibility Across Versions.
Additional related changes:
Removed the
UNSAFE_RELAX_FEDERATED_PROTOCOL_VERSION_CHECK
environment variable.Deprecated the remoteServerCompatVersion field in the
RemoteClusterConnectionStatus
type (returned by the checkRemoteClusterConnection() GraphQL query).Will remove the remoteServerCompatVersion field no earlier than version 1.207, following the
ShortTerm
API stability deprecation policy.The
QueryBacktrackingLimit
feature flag has been removed. Use theQueryBacktrackingLimit
dynamic configuration to adjust the limit.
Falcon LogScale 1.190.0 GA (2025-05-27)
Functions
As previously announced in RN Issue, the following functions can no longer be used after the first aggregate function:
.
For example, this query is no longer valid:
Invalid Example for Demonstration - DO NOT USElogscalegroupBy(class) | eventSize()
These functions can still be used before the first aggregate function:
logscaleeventSize() | tail(200)
This change is necessary as these functions require access to original events, which are not available post-aggregation.
Free-text search is no longer supported after the first aggregate function (as previously announced in RN Issue). For example, this query is no longer supported:
logscale Syntaxtail(200) | "Lorem ipsum dolor"
You can still search for strings in specific fields after aggregation:
logscale Syntaxtail(200) | msg="Lorem ipsum dolor"
Free-text search before the first aggregate function remains supported:
logscale"Lorem ipsum dolor" | tail(200)
Falcon LogScale 1.189.3 LTS (2025-08-06)
Installation and Deployment
Support for the
HUMIO_DEBUG
,JAVA_DEBUG_PORT
,DEBUG_SUSPEND_FLAG
andJAVA_DEBUG_OPTS
environment variables in the LogScale Launcher Script has been removed. If the LogScale process needs to be started in debug mode, set the relevant flags in theHUMIO_OPTS
environment variable instead.Administration and Management
Humio-Usage v0.2.0 dashboard data has been removed and replaced with a note and link to the Usage Page.
Removed assigned metrics:
segments-assigned-to-host-as-owner
segment-bytes-assigned-to-host-as-owner
These metrics provided incomplete data, tracking only post-merge segment assignments while excluding rebalancing-related segment movements.
GraphQL API
The following deprecated GraphQL fields have now been removed on the
Parser
output datatype:
assetType
sourceCode
tagFields
testData
The following deprecated GraphQL mutations have been removed:
createParser
updateParser
removeParser
The deprecated testParser GraphQL mutation has now been removed.
Note that a number of parser CRUD APIs were deprecated alongside testParser back in release 1.120, and these APIs will also be removed soon. Consider this as a reminder to move to the newer APIs if you have not already done so.
The deprecated
storage
task of the GraphQLNodeTaskEnum
has been removed (deprecated since v1.173.0). For more information, see RN Issue.This removal affects hosts configured with node role
all
:
Dynamic configuration to disable segment storage and search is no longer supported
Use existing node eviction mechanism instead for this functionality
getFilterAlertConfig GraphQL field has been removed on
HumioMetadata
datatype.
Falcon LogScale 1.189.2 LTS (2025-07-22)
Installation and Deployment
Support for the
HUMIO_DEBUG
,JAVA_DEBUG_PORT
,DEBUG_SUSPEND_FLAG
andJAVA_DEBUG_OPTS
environment variables in the LogScale Launcher Script has been removed. If the LogScale process needs to be started in debug mode, set the relevant flags in theHUMIO_OPTS
environment variable instead.Administration and Management
Humio-Usage v0.2.0 dashboard data has been removed and replaced with a note and link to the Usage Page.
Removed assigned metrics:
segments-assigned-to-host-as-owner
segment-bytes-assigned-to-host-as-owner
These metrics provided incomplete data, tracking only post-merge segment assignments while excluding rebalancing-related segment movements.
GraphQL API
The following deprecated GraphQL fields have now been removed on the
Parser
output datatype:
assetType
sourceCode
tagFields
testData
The following deprecated GraphQL mutations have been removed:
createParser
updateParser
removeParser
The deprecated testParser GraphQL mutation has now been removed.
Note that a number of parser CRUD APIs were deprecated alongside testParser back in release 1.120, and these APIs will also be removed soon. Consider this as a reminder to move to the newer APIs if you have not already done so.
The deprecated
storage
task of the GraphQLNodeTaskEnum
has been removed (deprecated since v1.173.0). For more information, see RN Issue.This removal affects hosts configured with node role
all
:
Dynamic configuration to disable segment storage and search is no longer supported
Use existing node eviction mechanism instead for this functionality
getFilterAlertConfig GraphQL field has been removed on
HumioMetadata
datatype.
Falcon LogScale 1.189.1 LTS (2025-06-11)
Installation and Deployment
Support for the
HUMIO_DEBUG
,JAVA_DEBUG_PORT
,DEBUG_SUSPEND_FLAG
andJAVA_DEBUG_OPTS
environment variables in the LogScale Launcher Script has been removed. If the LogScale process needs to be started in debug mode, set the relevant flags in theHUMIO_OPTS
environment variable instead.Administration and Management
Humio-Usage v0.2.0 dashboard data has been removed and replaced with a note and link to the Usage Page.
Removed assigned metrics:
segments-assigned-to-host-as-owner
segment-bytes-assigned-to-host-as-owner
These metrics provided incomplete data, tracking only post-merge segment assignments while excluding rebalancing-related segment movements.
GraphQL API
The following deprecated GraphQL fields have now been removed on the
Parser
output datatype:
assetType
sourceCode
tagFields
testData
The following deprecated GraphQL mutations have been removed:
createParser
updateParser
removeParser
The deprecated testParser GraphQL mutation has now been removed.
Note that a number of parser CRUD APIs were deprecated alongside testParser back in release 1.120, and these APIs will also be removed soon. Consider this as a reminder to move to the newer APIs if you have not already done so.
The deprecated
storage
task of the GraphQLNodeTaskEnum
has been removed (deprecated since v1.173.0). For more information, see RN Issue.This removal affects hosts configured with node role
all
:
Dynamic configuration to disable segment storage and search is no longer supported
Use existing node eviction mechanism instead for this functionality
getFilterAlertConfig GraphQL field has been removed on
HumioMetadata
datatype.
Falcon LogScale 1.189.0 GA (2025-05-20)
Administration and Management
Removed assigned metrics:
segments-assigned-to-host-as-owner
segment-bytes-assigned-to-host-as-owner
These metrics provided incomplete data, tracking only post-merge segment assignments while excluding rebalancing-related segment movements.
GraphQL API
The following deprecated GraphQL fields have now been removed on the
Parser
output datatype:
assetType
sourceCode
tagFields
testData
The following deprecated GraphQL mutations have been removed:
createParser
updateParser
removeParser
The deprecated
storage
task of the GraphQLNodeTaskEnum
has been removed (deprecated since v1.173.0). For more information, see RN Issue.This removal affects hosts configured with node role
all
:
Dynamic configuration to disable segment storage and search is no longer supported
Use existing node eviction mechanism instead for this functionality
getFilterAlertConfig GraphQL field has been removed on
HumioMetadata
datatype.
Falcon LogScale 1.187.0 GA (2025-05-06)
Installation and Deployment
Support for the
HUMIO_DEBUG
,JAVA_DEBUG_PORT
,DEBUG_SUSPEND_FLAG
andJAVA_DEBUG_OPTS
environment variables in the LogScale Launcher Script has been removed. If the LogScale process needs to be started in debug mode, set the relevant flags in theHUMIO_OPTS
environment variable instead.
Falcon LogScale 1.184.0 GA (2025-04-15)
Administration and Management
Humio-Usage v0.2.0 dashboard data has been removed and replaced with a note and link to the Usage Page.
GraphQL API
The deprecated testParser GraphQL mutation has now been removed.
Note that a number of parser CRUD APIs were deprecated alongside testParser back in release 1.120, and these APIs will also be removed soon. Consider this as a reminder to move to the newer APIs if you have not already done so.
Falcon LogScale 1.183.1 LTS (2025-05-01)
GraphQL API
The following items have been removed:
assetType field on the types
Alert
,Dashboard
,ViewInteraction
, andSavedQuery
.GraphQL mutations createAlertFromTemplate, createAlertFromPackageTemplate, createScheduledSearchFromTemplate, and createScheduledSearchFromPackageTemplate.
Enumeration value
ChangeTriggersAndActions
from the enumeration typesPermission
andViewAction
.
Falcon LogScale 1.182.0 GA (2025-04-01)
GraphQL API
The following items have been removed:
assetType field on the types
Alert
,Dashboard
,ViewInteraction
, andSavedQuery
.GraphQL mutations createAlertFromTemplate, createAlertFromPackageTemplate, createScheduledSearchFromTemplate, and createScheduledSearchFromPackageTemplate.
Enumeration value
ChangeTriggersAndActions
from the enumeration typesPermission
andViewAction
.
Falcon LogScale 1.177.2 LTS (2025-04-23)
Storage
The
WriteNewSegmentFileFormat
feature flag has been reverted and the feature is not yet available for general use. A future release will reintroduce this functionality.Configuration
The deprecated
QUERY_COORDINATOR
environment variable has now been removed.
Falcon LogScale 1.177.1 LTS (2025-03-19)
Configuration
The deprecated
QUERY_COORDINATOR
environment variable has now been removed.
Falcon LogScale 1.173.0 GA (2025-01-28)
Configuration
The deprecated
QUERY_COORDINATOR
environment variable has now been removed.
Falcon LogScale 1.171.3 LTS (2025-04-23)
Storage
The
WriteNewSegmentFileFormat
feature flag has been reverted and the feature is not yet available for general use. A future release will reintroduce this functionality.
Falcon LogScale 1.165.3 LTS (2025-04-23)
Storage
The
WriteNewSegmentFileFormat
feature flag has been reverted and the feature is not yet available for general use. A future release will reintroduce this functionality.GraphQL API
Removed the following deprecated fields from the
Cluster
GraphQL type:
ingestPartitionsWarnings
suggestedIngestPartitions
suggestedIngestPartitions
storagePartitions
storagePartitionsWarnings
suggestedStoragePartitions
Configuration
The dynamic configuration and related GraphQL API
AstDepthLimit
has been removed.The
UNSAFE_ALLOW_FEDERATED_CIDR
,UNSAFE_ALLOW_FEDERATED_MATCH
, andALLOW_MULTI_CLUSTER_TABLE_SYNCHRONIZATION
environment variables have been removed as they now react as if they are always enabled.
Falcon LogScale 1.165.2 LTS (2024-12-17)
GraphQL API
Removed the following deprecated fields from the
Cluster
GraphQL type:
ingestPartitionsWarnings
suggestedIngestPartitions
suggestedIngestPartitions
storagePartitions
storagePartitionsWarnings
suggestedStoragePartitions
Configuration
The dynamic configuration and related GraphQL API
AstDepthLimit
has been removed.The
UNSAFE_ALLOW_FEDERATED_CIDR
,UNSAFE_ALLOW_FEDERATED_MATCH
, andALLOW_MULTI_CLUSTER_TABLE_SYNCHRONIZATION
environment variables have been removed as they now react as if they are always enabled.
Falcon LogScale 1.165.1 LTS (2024-12-17)
GraphQL API
Removed the following deprecated fields from the
Cluster
GraphQL type:
ingestPartitionsWarnings
suggestedIngestPartitions
suggestedIngestPartitions
storagePartitions
storagePartitionsWarnings
suggestedStoragePartitions
Configuration
The dynamic configuration and related GraphQL API
AstDepthLimit
has been removed.The
UNSAFE_ALLOW_FEDERATED_CIDR
,UNSAFE_ALLOW_FEDERATED_MATCH
, andALLOW_MULTI_CLUSTER_TABLE_SYNCHRONIZATION
environment variables have been removed as they now react as if they are always enabled.
Falcon LogScale 1.164.0 GA (2024-11-12)
Configuration
The dynamic configuration and related GraphQL API
AstDepthLimit
has been removed.
Falcon LogScale 1.163.0 GA (2024-11-05)
GraphQL API
Removed the following deprecated fields from the
Cluster
GraphQL type:
ingestPartitionsWarnings
suggestedIngestPartitions
suggestedIngestPartitions
storagePartitions
storagePartitionsWarnings
suggestedStoragePartitions
Configuration
The
UNSAFE_ALLOW_FEDERATED_CIDR
,UNSAFE_ALLOW_FEDERATED_MATCH
, andALLOW_MULTI_CLUSTER_TABLE_SYNCHRONIZATION
environment variables have been removed as they now react as if they are always enabled.
Falcon LogScale 1.153.4 LTS (2024-12-17)
Installation and Deployment
The previously deprecated
jar
distribution of LogScale (e.g.server-1.117.jar
) is no longer published starting from this version. For more information, see Falcon LogScale 1.130.0 GA (2024-03-19).The previously deprecated
humio/kafka
andhumio/zookeeper
Docker images are now removed and no longer published.API
The following previously deprecated KAFKA API endpoints have been removed:
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment/set-replication-defaults
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment/id
Configuration
The obsolete configuration parameters
AUTOSHARDING_TRIGGER_DELAY_MS
andAUTOSHARDING_CHECKINTERVAL_MS
have been removed due to autosharding being handled by rate monitoring and not by ingest delay anymore.Other
Unnecessary
digest-coordinator-changes
anddesired-digest-coordinator-changes
metrics have been removed. Instead, the logging in theIngestPartitionCoordinator
class has been improved, to allow monitoring of when reassignment of desired and current digesters happens — by searching forWrote changes to desired digest partitions
/Wrote changes to current digest partitions
.
Falcon LogScale 1.153.3 LTS (2024-10-02)
Installation and Deployment
The previously deprecated
jar
distribution of LogScale (e.g.server-1.117.jar
) is no longer published starting from this version. For more information, see Falcon LogScale 1.130.0 GA (2024-03-19).The previously deprecated
humio/kafka
andhumio/zookeeper
Docker images are now removed and no longer published.API
The following previously deprecated KAFKA API endpoints have been removed:
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment/set-replication-defaults
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment/id
Configuration
The obsolete configuration parameters
AUTOSHARDING_TRIGGER_DELAY_MS
andAUTOSHARDING_CHECKINTERVAL_MS
have been removed due to autosharding being handled by rate monitoring and not by ingest delay anymore.Other
Unnecessary
digest-coordinator-changes
anddesired-digest-coordinator-changes
metrics have been removed. Instead, the logging in theIngestPartitionCoordinator
class has been improved, to allow monitoring of when reassignment of desired and current digesters happens — by searching forWrote changes to desired digest partitions
/Wrote changes to current digest partitions
.
Falcon LogScale 1.153.1 LTS (2024-09-18)
Installation and Deployment
The previously deprecated
jar
distribution of LogScale (e.g.server-1.117.jar
) is no longer published starting from this version. For more information, see Falcon LogScale 1.130.0 GA (2024-03-19).The previously deprecated
humio/kafka
andhumio/zookeeper
Docker images are now removed and no longer published.API
The following previously deprecated KAFKA API endpoints have been removed:
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment/set-replication-defaults
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment/id
Configuration
The obsolete configuration parameters
AUTOSHARDING_TRIGGER_DELAY_MS
andAUTOSHARDING_CHECKINTERVAL_MS
have been removed due to autosharding being handled by rate monitoring and not by ingest delay anymore.Other
Unnecessary
digest-coordinator-changes
anddesired-digest-coordinator-changes
metrics have been removed. Instead, the logging in theIngestPartitionCoordinator
class has been improved, to allow monitoring of when reassignment of desired and current digesters happens — by searching forWrote changes to desired digest partitions
/Wrote changes to current digest partitions
.
Falcon LogScale 1.152.0 GA (2024-08-20)
Configuration
The obsolete configuration parameters
AUTOSHARDING_TRIGGER_DELAY_MS
andAUTOSHARDING_CHECKINTERVAL_MS
have been removed due to autosharding being handled by rate monitoring and not by ingest delay anymore.
Falcon LogScale 1.149.0 GA (2024-07-30)
Installation and Deployment
The previously deprecated
jar
distribution of LogScale (e.g.server-1.117.jar
) is no longer published starting from this version. For more information, see Falcon LogScale 1.130.0 GA (2024-03-19).The previously deprecated
humio/kafka
andhumio/zookeeper
Docker images are now removed and no longer published.
Falcon LogScale 1.148.0 Internal (2024-07-23)
API
The following previously deprecated KAFKA API endpoints have been removed:
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment
POST
/api/v1/clusterconfig/kafka-queues/partition-assignment/set-replication-defaults
GET
/api/v1/clusterconfig/kafka-queues/partition-assignment/id
Falcon LogScale 1.143.0 GA (2024-06-18)
Other
Unnecessary
digest-coordinator-changes
anddesired-digest-coordinator-changes
metrics have been removed. Instead, the logging in theIngestPartitionCoordinator
class has been improved, to allow monitoring of when reassignment of desired and current digesters happens — by searching forWrote changes to desired digest partitions
/Wrote changes to current digest partitions
.
Falcon LogScale 1.136.2 LTS (2024-06-12)
Storage
The full JDK has been removed from the Docker images, leaving only the bundled JDK that is part of LogScale release tarballs.
Falcon LogScale 1.136.1 LTS (2024-05-29)
Storage
The full JDK has been removed from the Docker images, leaving only the bundled JDK that is part of LogScale release tarballs.
Falcon LogScale 1.136.0 GA (2024-04-30)
Storage
The full JDK has been removed from the Docker images, leaving only the bundled JDK that is part of LogScale release tarballs.
Falcon LogScale 1.131.3 LTS (2024-09-24)
GraphQL API
The enabledFeatures() query has been removed from GraphQL schema. Use featureFlags() query instead.
Falcon LogScale 1.131.2 LTS (2024-05-14)
GraphQL API
The enabledFeatures() query has been removed from GraphQL schema. Use featureFlags() query instead.
Falcon LogScale 1.131.1 LTS (2024-04-17)
GraphQL API
The enabledFeatures() query has been removed from GraphQL schema. Use featureFlags() query instead.
Falcon LogScale 1.129.0 GA (2024-03-12)
GraphQL API
The enabledFeatures() query has been removed from GraphQL schema. Use featureFlags() query instead.
Falcon LogScale 1.124.3 LTS (2024-05-14)
GraphQL API
Removed the
Asset
interface type in GraphQL thatAlert
,Dashboard
,Parser
,SavedQuery
andViewInteraction
datatypes implemented. It was not used as a type for any field. All fields from theAsset
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.
Falcon LogScale 1.124.2 LTS (2024-03-20)
GraphQL API
Removed the
Asset
interface type in GraphQL thatAlert
,Dashboard
,Parser
,SavedQuery
andViewInteraction
datatypes implemented. It was not used as a type for any field. All fields from theAsset
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.
Falcon LogScale 1.124.1 LTS (2024-02-29)
GraphQL API
Removed the
Asset
interface type in GraphQL thatAlert
,Dashboard
,Parser
,SavedQuery
andViewInteraction
datatypes implemented. It was not used as a type for any field. All fields from theAsset
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.
Falcon LogScale 1.121.0 GA (2024-01-16)
Configuration
The
DEFAULT_PARTITION_COUNT
configuration parameter has been removed, as it was unused by the system due to earlier changes to partition handling.
Falcon LogScale 1.119.0 GA (2023-12-19)
GraphQL API
Removed the
Asset
interface type in GraphQL thatAlert
,Dashboard
,Parser
,SavedQuery
andViewInteraction
datatypes implemented. It was not used as a type for any field. All fields from theAsset
interface type are still present in the implementing types.
Falcon LogScale 1.118.4 LTS (2024-02-23)
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() .
Falcon LogScale 1.118.3 LTS (2024-02-06)
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() .
Falcon LogScale 1.118.2 LTS (2024-01-17)
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() .
Falcon LogScale 1.118.0 GA (2023-12-12)
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() .
Falcon LogScale 1.112.4 LTS (2024-02-23)
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 toBooleanResultType
datatype. Removed theclientMutationId
field on the returned type and replaced it by a boolean field namedresult
.Most deprecated queries, mutations and fields have now been removed from the GraphQL API.
Configuration
Some deprecated configuration variables have now been removed:
GCP_STORAGE_UPLOAD_CONCURRENCY
GCP_STORAGE_DOWNLOAD_CONCURRENCY
They have been replaced by
S3_STORAGE_CONCURRENCY
andGCP_STORAGE_CONCURRENCY
settings that internally handle rate-limiting responses from the bucket provider.
Falcon LogScale 1.112.3 LTS (2024-01-30)
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 toBooleanResultType
datatype. Removed theclientMutationId
field on the returned type and replaced it by a boolean field namedresult
.Most deprecated queries, mutations and fields have now been removed from the GraphQL API.
Configuration
Some deprecated configuration variables have now been removed:
GCP_STORAGE_UPLOAD_CONCURRENCY
GCP_STORAGE_DOWNLOAD_CONCURRENCY
They have been replaced by
S3_STORAGE_CONCURRENCY
andGCP_STORAGE_CONCURRENCY
settings that internally handle rate-limiting responses from the bucket provider.
Falcon LogScale 1.112.2 LTS (2024-01-22)
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 toBooleanResultType
datatype. Removed theclientMutationId
field on the returned type and replaced it by a boolean field namedresult
.Most deprecated queries, mutations and fields have now been removed from the GraphQL API.
Configuration
Some deprecated configuration variables have now been removed:
GCP_STORAGE_UPLOAD_CONCURRENCY
GCP_STORAGE_DOWNLOAD_CONCURRENCY
They have been replaced by
S3_STORAGE_CONCURRENCY
andGCP_STORAGE_CONCURRENCY
settings that internally handle rate-limiting responses from the bucket provider.
Falcon LogScale 1.112.1 LTS (2023-11-15)
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 toBooleanResultType
datatype. Removed theclientMutationId
field on the returned type and replaced it by a boolean field namedresult
.Most deprecated queries, mutations and fields have now been removed from the GraphQL API.
Configuration
Some deprecated configuration variables have now been removed:
GCP_STORAGE_UPLOAD_CONCURRENCY
GCP_STORAGE_DOWNLOAD_CONCURRENCY
They have been replaced by
S3_STORAGE_CONCURRENCY
andGCP_STORAGE_CONCURRENCY
settings that internally handle rate-limiting responses from the bucket provider.
Falcon LogScale 1.111.0 GA (2023-10-10)
Storage
The unused
humio-backup
symlink inside Docker containers has been removed.Configuration
Some deprecated configuration variables have now been removed:
GCP_STORAGE_UPLOAD_CONCURRENCY
GCP_STORAGE_DOWNLOAD_CONCURRENCY
They have been replaced by
S3_STORAGE_CONCURRENCY
andGCP_STORAGE_CONCURRENCY
settings that internally handle rate-limiting responses from the bucket provider.
Falcon LogScale 1.108.0 GA (2023-09-19)
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 toBooleanResultType
datatype. Removed theclientMutationId
field on the returned type and replaced it by a boolean field namedresult
.Most deprecated queries, mutations and fields have now been removed from the GraphQL API.
Falcon LogScale 1.107.0 GA (2023-09-12)
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.
Falcon LogScale 1.100.3 LTS (2024-01-22)
GraphQL API
The deprecated
RegistryPackage
datatype has been deleted, along with the deprecated mutations and fields using it:
installPackageFromRegistry() mutation
updatePackageFromRegistry() mutation
package
in theSearchdomain
datatype
Falcon LogScale 1.100.2 LTS (2023-11-15)
GraphQL API
The deprecated
RegistryPackage
datatype has been deleted, along with the deprecated mutations and fields using it:
installPackageFromRegistry() mutation
updatePackageFromRegistry() mutation
package
in theSearchdomain
datatype
Falcon LogScale 1.100.1 LTS (2023-10-28)
GraphQL API
The deprecated
RegistryPackage
datatype has been deleted, along with the deprecated mutations and fields using it:
installPackageFromRegistry() mutation
updatePackageFromRegistry() mutation
package
in theSearchdomain
datatype
Falcon LogScale 1.100.0 LTS (2023-08-16)
GraphQL API
The deprecated
RegistryPackage
datatype has been deleted, along with the deprecated mutations and fields using it:
installPackageFromRegistry() mutation
updatePackageFromRegistry() mutation
package
in theSearchdomain
datatype
Falcon LogScale 1.95.0 GA (2023-06-20)
GraphQL API
The deprecated
RegistryPackage
datatype has been deleted, along with the deprecated mutations and fields using it:
installPackageFromRegistry() mutation
updatePackageFromRegistry() mutation
package
in theSearchdomain
datatype
Falcon LogScale 1.94.2 LTS (2023-11-15)
API
Degrade and deprecate some REST and GraphQL APIs due to the introduction of
AutomaticSegmentDistribution
andAutomaticDigesterDistribution
. 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 beO
:
reapply_targetBytes
reapply_targetSegments
reapply_inboundBytes
reapply_inboundSegments
Falcon LogScale 1.94.1 LTS (2023-10-28)
API
Degrade and deprecate some REST and GraphQL APIs due to the introduction of
AutomaticSegmentDistribution
andAutomaticDigesterDistribution
. 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 beO
:
reapply_targetBytes
reapply_targetSegments
reapply_inboundBytes
reapply_inboundSegments
Falcon LogScale 1.94.0 LTS (2023-07-05)
API
Degrade and deprecate some REST and GraphQL APIs due to the introduction of
AutomaticSegmentDistribution
andAutomaticDigesterDistribution
. 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 beO
:
reapply_targetBytes
reapply_targetSegments
reapply_inboundBytes
reapply_inboundSegments
Falcon LogScale 1.89.0 GA (2023-05-11)
API
Degrade and deprecate some REST and GraphQL APIs due to the introduction of
AutomaticSegmentDistribution
andAutomaticDigesterDistribution
. 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 beO
:
reapply_targetBytes
reapply_targetSegments
reapply_inboundBytes
reapply_inboundSegments
Falcon LogScale 1.81.0 GA (2023-03-14)
Automation and Triggers
The deprecated REST Alert API has been removed.
Other
The deprecated REST Action API endpoint for testing actions has been removed.
Falcon LogScale 1.76.5 LTS (2023-07-04)
API
Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.
Falcon LogScale 1.76.4 LTS (2023-06-22)
API
Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.
Falcon LogScale 1.76.3 LTS (2023-04-27)
API
Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.
Falcon LogScale 1.76.2 LTS (2023-03-06)
API
Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.
Falcon LogScale 1.76.1 LTS (2023-02-27)
API
Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.
Falcon LogScale 1.76.0 GA (2023-02-07)
API
Removed the API for managing ingest tokens. This has long been deprecated and replaced by a GraphQL API.
Falcon LogScale 1.63.6 LTS (2023-03-22)
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:
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.
Falcon LogScale 1.63.5 LTS (2023-03-06)
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:
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.
Falcon LogScale 1.63.4 LTS (2023-02-01)
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:
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.
Falcon LogScale 1.63.3 LTS (2022-12-21)
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:
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.
Falcon LogScale 1.63.2 LTS (2022-11-30)
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:
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.
Falcon LogScale 1.63.1 LTS (2022-11-14)
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:
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.
Humio Server 1.57.0 GA (2022-09-13)
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:
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.
Humio Server 1.51.3 LTS (2022-12-21)
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.
Humio Server 1.51.2 LTS (2022-10-05)
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.
Humio Server 1.51.1 LTS (2022-08-29)
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.
Humio Server 1.51.0 LTS (2022-08-15)
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.
Humio Server 1.49.1 GA (2022-07-26)
API
The deprecated REST API for parsers has been removed.
Humio Server 1.48.1 GA (2022-07-19)
Installation and Deployment
Remove the following feature flags and their usage:
EnterpriseLogin
,OidcDynamicIdpProviders
,UsagePage
,RequestToActivity
,CommunityNewDemoData
.
Humio Server 1.44.0 GA (2022-06-21)
API
The deprecated REST API for actions has been removed, except for the endpoint for testing an action.
Humio Server 1.29.0 GA (2021-07-09)
GraphQL API
Deprecated argument
name
was removed fromMutation.updateParser
field.Deprecated argument
repositoryName
was removed fromMutation.updateParser
field.
Humio Server 1.21.0 GA (2021-02-22)
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.