-
Task
-
Resolution: Done
-
Major
-
Logging 5.9.0
-
None
-
5
-
False
-
-
False
-
NEW
-
VERIFIED
-
Release Note Not Required
-
-
-
Log Storage - Sprint 243, Log Storage - Sprint 244, Log Storage - Sprint 245, Log Storage - Sprint 246, Log Storage - Sprint 247
Description
As a LokiStack administrator I want to be able to define a additional ObjectStorageSchema using V13 and TSDBv3 for an effective date in the future, so that newer incoming logs are eligible to use the structured metadata indexing capabilities.
Acceptance Criteria
- The LokiStack administrator can define an additional schema without breaking access to stored logs in previous schemas (V11/V12) and indexed by boltdb-shipper.
- The LokiStack administrator can see in the resource status or per alert if the old logs (using V11/V12 and boltdb-shipper) fall out of retention and is able to drop the old schema.
Developer Notes
- Boltdb-shipper to TSDB Migration Docs
- Considering if the above migration docs imply additions/validation for the LokiStack limits config.
- Evaluate if an alert or resource status condition can be use to nudge people to upgrade from the present default schema (V11) to V13.
- blocks
-
LOG-4804 Add a custom metric that collects Loki stacks requiring a schema upgrade
-
- Closed
-
- links to
- mentioned on