-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Logging 5.8
-
0
-
False
-
-
False
-
-
As indicated in this JIRA entry, since Logging version 5.6, the Lokistack compactor has been equipped with a function to delete chunk data past its retention period in object storage.
Retention in Loki has always been global for a cluster and deferred to the underlying object store. Since version 2.3.0, Loki can handle retention through the Compactor component.
Therefore, it has become possible to set the log retention period on the Loki side without configuring TTL settings on the object storage side. However, the following note is included in the documentation for Loki's stream-based retention:
NOTE: This is not for managing the retention of stored logs. Global retention periods for stored logs to a supported maximum of 30 days is configured with your object storage.
Is this explanation accurate? The note seems to suggest that the retention period settings are exclusively managed by the object storage, not by Loki, which could be misleading and inconsistent with the actual functionality.
- is related to
-
-
- To Do
-
- relates to
-
-
- To Do
-
-
-
- Closed
-
-
-
- Closed
-