openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OBSDOCS-1070

Browse Source
This commit is contained in:
Satyajeet Munje
2024-05-20 16:24:03 +05:30
committed by openshift-cherrypick-robot
parent 3348dc9039
commit 090e649b67
2 changed files with 19 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
modules/logging-loki-retention.adoc
View File

@@ -1,6 +1,6 @@
// Module included in the following assemblies:
//
// logging/cluster-logging-loki.adoc
//
// * observability/logging/log_storage/cluster-logging-loki.adoc
:_mod-docs-content-type: PROCEDURE
[id="logging-loki-retention_{context}"]
@@ -8,12 +8,14 @@
With Logging version 5.6 and higher, you can configure retention policies based on log streams. Rules for these may be set globally, per tenant, or both. If you configure both, tenant rules apply before global rules.
include::snippets/logging-retention-period-snip.adoc[]
[NOTE]
====
Although logging version 5.9 and higher supports schema v12, v13 is recommended.
====
. To enable stream-based retention, create a `LokiStack` custom resource (CR):
. To enable stream-based retention, create a `LokiStack` CR:
+
.Example global stream-based retention for AWS
[source,yaml]

14
snippets/logging-retention-period-snip.adoc Normal file
View File

@@ -0,0 +1,14 @@
// Text snippet included in the following assemblies:
//
// * observability/logging/log_storage/cluster-logging-loki.adoc
//
// Text snippet included in the following modules:
//
// * logging-loki-retention.adoc
:_mod-docs-content-type: SNIPPET
[IMPORTANT]
====
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.
====