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? | Entry | Class | First Registered | Last 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 API | 1.246.0 | 1.258.99 |
| Advance Warning |
The mutation deleteFeatureFlag will be removed from the code in LTS 1.270. It is replaced by resetFeature. | GraphQL API | 1.254.0 | 1.270.0 |
| Deprecation |
The userId parameter for the updateDashboardToken GraphQL mutation has been deprecated and will be removed in version 1.273. | GraphQL API | 1.217.0 | 1.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
| GraphQL API | 1.252.0 | 1.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 API | 1.253.0 | 1.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
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. | Storage | 1.200 | Undetermined |