Upcoming Changes

This page lists the upcoming changes that have been identified in the release notes. Where possible, notification of the change and version number will be provided.

Type?EntryClassFirst RegisteredLast Supported Version
Behavior Changes

After an organization is soft deleted using the removeOrganization mutation, you can now only call the following mutations on that organization:

Previously, you could call any mutation on a soft-deleted organization.

GraphQL API1.246.01.258.99
Advance Warning

The mutation deleteFeatureFlag will be removed from the code in LTS 1.270. It is replaced by resetFeature.

GraphQL API1.254.01.270.0
Deprecation

The userId parameter for the updateDashboardToken GraphQL mutation has been deprecated and will be removed in version 1.273.

GraphQL API1.217.01.272.99
Deprecation

The GraphQL field meta has been deprecated and now requires authentication. It will be completely removed in LogScale 1.304. To achieve similar results, use the loginInfo and clusterConfig fields instead.

To temporarily opt out of the authentication requirement, the feature flag UnauthenticatedMeta can be enabled.

GraphQL API1.252.01.304.0
Improvement

The GraphQL datatype ScheduledReport now exposes the field createdInfo, which contains structured creation metadata. Data points include author and timestamp, which is consistent with other asset types such as filter alerts, dashboards, and parsers.

The existing fields createdBy and creationDate are now deprecated and will be removed in version 1.306. Migration to the createdInfo field is recommended, as it provides richer author information (user, token, and/or system) alongside the creation timestamp.

Existing scheduled reports are automatically migrated, no action is required.

GraphQL API1.253.01.306.0
Known Issues

For clusters using secondary storage where the primary storage on some nodes in the cluster may be getting filled (that is, the storage usage on the primary disk is halfway between PRIMARY_STORAGE_PERCENTAGE and PRIMARY_STORAGE_MAX_FILL_PERCENTAGE), those nodes may fail to transfer segments from other nodes. The failure will be indicated by the error java.nio.file.AtomicMoveNotSupportedException with message "Invalid cross-device link".

This does not corrupt data or cause data loss, but will prevent the cluster from being fully healthy, and could also prevent data from reaching adequate replication.

Storage1.200Undetermined