-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Logging 5.8
-
3
-
False
-
-
False
-
-
-
Critical
URL
https://docs.openshift.com/container-platform/4.14/logging/log_storage/installing-log-storage.html
Description
Having the same value of `spec.storage.schema.version` and `spec.storage.schema.effectiveDate` are important when Loki is present as documented in https://grafana.com/docs/loki/latest/operations/storage/schema/.
A change in the schema means to don't be able to see the old streams as documented in the upstream documentation because it's changed where the streams are written and read.
Change proposed
Change all the Loki examples for being consistent for having the same value of `spec.storage.schema.version` and `spec.storage.schema.from`, currently, at least, it's observed two different:
spec: size: 1x.small storage: schemas: - version: v12 <------- this version effectiveDate: '2022-06-01' <--- <--- this time is the field from in Loki that could be adjusted to something different
and
storage: schemas: - effectiveDate: "2020-10-11" <--- this time is the field from in Loki that could be adjusted to something different version: v11 <--- this version
Then, the current `version` used should be the newest: v12 and it should be used the same value across of all the examples. In the future, this could change to a new schema version.
The `effectiveDate` and `version` should be explained the meaning and importance of it as per https://grafana.com/docs/loki/latest/operations/storage/schema/.
- relates to
-
OBSDOCS-891 Recommended storage technology for Loki Logging storage
- In Progress
- links to