-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Logging 5.6, Logging 5.7, Logging 5.9
-
3
-
False
-
-
False
-
-
-
Critical
As per the logs we documented about enabling stream based retention but there is no clarity on how to set retention period to clear the logs from object storage.
We need to add the note in the doc to make customer aware that logs retention for object bucket should be configured on storage provider side
For cost-efficient logs pruning, it is recommended to set global retention on the object storage provider side. Pruning older logs is a cost free task provided by the storage provided & omits Loki's resource to be bound to the task of pruning logs.
Ref KCS https://access.redhat.com/solutions/7053212
Second issue: "Retention Period of 30 days"
It's needed to remove the incorrect sentence:
This is not for managing the retention for stored logs. Global retention periods for stored logs to a supported maximum of 30 days is configured with your object storage.
As in a documentation bug was requested to clarify the previous sentence and it was added the sentence below, but forgetting to remove the previous:
If there is no retention period defined on the s3 bucket or in the LokiStack custom resource (CR), then the logs are not pruned and they stay in the s3 bucket forever, which might fill up the s3 storage.
- is related to
-
OBSDOCS-494 Emphasizing the Loki 30-days log retention support
- Closed
-
OBSDOCS-703 Incorrect Information in the NOTE on Loki's Stream-Based Retention Documentation
- Closed
- relates to
-
OBSDOCS-494 Emphasizing the Loki 30-days log retention support
- Closed
-
OBSDOCS-703 Incorrect Information in the NOTE on Loki's Stream-Based Retention Documentation
- Closed
-
OBSDOCS-1070 Loki default retention note
- Closed
-
OBSDOCS-712 [enterprise-4.14] Issue in file logging/log_storage/cluster-logging-loki.adoc
- Closed
- links to