From f6a7d94eba7615afc134769f2b84131b69f10c68 Mon Sep 17 00:00:00 2001 From: sarah-spang <86264026+sarah-spang@users.noreply.github.com> Date: Wed, 12 Apr 2023 12:53:24 -0600 Subject: [PATCH 1/5] Docs: add URL to Log entry deletion page Doc currently says the API to delete logs is still under development. Updated doc to point to new log entry deletion doc. --- docs/sources/operations/storage/retention.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/sources/operations/storage/retention.md b/docs/sources/operations/storage/retention.md index 111535d53e6cc..da0604c541681 100644 --- a/docs/sources/operations/storage/retention.md +++ b/docs/sources/operations/storage/retention.md @@ -186,12 +186,7 @@ policy set correctly. For more details check or [GCS's documentation](https://cloud.google.com/storage/docs/managing-lifecycles). -Currently, the retention policy can only be set globally. A per-tenant retention -policy with an API to delete ingested logs is still under development. - -Since a design goal of Loki is to make storing logs cheap, a volume-based -deletion API is deprioritized. Until this feature is released, if you suddenly -must delete ingested logs, you can delete old chunks in your object store. Note, +If you suddenly must delete ingested logs, you can delete old chunks in your object store. Note, however, that this only deletes the log content and keeps the label index intact; you will still be able to see related labels but will be unable to retrieve the deleted log content. @@ -199,6 +194,10 @@ retrieve the deleted log content. For further details on the Table Manager internals, refer to the [Table Manager]({{}}) documentation. +Alternatively, if the BoltDB Shipper is configured for the index store, you can enable [Log entry deletion](https://grafana.com/docs/loki/latest/operations/storage/logs-deletion/) to delete log entries from a specific stream. + + + ## Example Configuration From 0bac6b5a0f3816a48138b2f2d03f0bb6bee1731d Mon Sep 17 00:00:00 2001 From: sarah-spang <86264026+sarah-spang@users.noreply.github.com> Date: Wed, 12 Apr 2023 13:01:55 -0600 Subject: [PATCH 2/5] Docs: Update URL to use relref --- docs/sources/operations/storage/retention.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/sources/operations/storage/retention.md b/docs/sources/operations/storage/retention.md index da0604c541681..7161d53e7a359 100644 --- a/docs/sources/operations/storage/retention.md +++ b/docs/sources/operations/storage/retention.md @@ -194,9 +194,7 @@ retrieve the deleted log content. For further details on the Table Manager internals, refer to the [Table Manager]({{}}) documentation. -Alternatively, if the BoltDB Shipper is configured for the index store, you can enable [Log entry deletion](https://grafana.com/docs/loki/latest/operations/storage/logs-deletion/) to delete log entries from a specific stream. - - +Alternatively, if the BoltDB Shipper is configured for the index store, you can enable [Log entry deletion]({{}}) to delete log entries from a specific stream. ## Example Configuration From e4a85c8a6f72ac2340f5c81e1ba284075808a734 Mon Sep 17 00:00:00 2001 From: sarah-spang <86264026+sarah-spang@users.noreply.github.com> Date: Wed, 26 Apr 2023 09:25:44 -0600 Subject: [PATCH 3/5] Update docs/sources/operations/storage/retention.md Co-authored-by: J Stickler --- docs/sources/operations/storage/retention.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/operations/storage/retention.md b/docs/sources/operations/storage/retention.md index 7161d53e7a359..aa6f92354c565 100644 --- a/docs/sources/operations/storage/retention.md +++ b/docs/sources/operations/storage/retention.md @@ -186,7 +186,7 @@ policy set correctly. For more details check or [GCS's documentation](https://cloud.google.com/storage/docs/managing-lifecycles). -If you suddenly must delete ingested logs, you can delete old chunks in your object store. Note, +If you must delete ingested logs, you can delete old chunks in your object store. Note, however, that this only deletes the log content and keeps the label index intact; you will still be able to see related labels but will be unable to retrieve the deleted log content. From ee7aff55e80e283f5f39d49abbb8af0d4128d7c3 Mon Sep 17 00:00:00 2001 From: sarah-spang <86264026+sarah-spang@users.noreply.github.com> Date: Wed, 26 Apr 2023 09:26:08 -0600 Subject: [PATCH 4/5] Update docs/sources/operations/storage/retention.md Co-authored-by: J Stickler --- docs/sources/operations/storage/retention.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/operations/storage/retention.md b/docs/sources/operations/storage/retention.md index aa6f92354c565..f8e07d81fd08c 100644 --- a/docs/sources/operations/storage/retention.md +++ b/docs/sources/operations/storage/retention.md @@ -194,7 +194,7 @@ retrieve the deleted log content. For further details on the Table Manager internals, refer to the [Table Manager]({{}}) documentation. -Alternatively, if the BoltDB Shipper is configured for the index store, you can enable [Log entry deletion]({{}}) to delete log entries from a specific stream. +Alternatively, if the BoltDB Shipper is configured for the index store, you can enable [Log entry deletion]({{}}) to delete log entries from a specific stream. ## Example Configuration From 36b5bfd3ad66273d0eb76d042565606e51ab1824 Mon Sep 17 00:00:00 2001 From: J Stickler Date: Tue, 17 Dec 2024 16:04:38 -0500 Subject: [PATCH 5/5] Update docs/sources/operations/storage/retention.md --- docs/sources/operations/storage/retention.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/operations/storage/retention.md b/docs/sources/operations/storage/retention.md index 27875faffda62..092414c94555d 100644 --- a/docs/sources/operations/storage/retention.md +++ b/docs/sources/operations/storage/retention.md @@ -219,7 +219,7 @@ retrieve the deleted log content. For further details on the Table Manager internals, refer to the [Table Manager](https://grafana.com/docs/loki//operations/storage/table-manager/) documentation. -Alternatively, if the BoltDB Shipper is configured for the index store, you can enable [Log entry deletion]({{}}) to delete log entries from a specific stream. +Alternatively, if the BoltDB Shipper is configured for the index store, you can enable [Log entry deletion](https://grafana.com/docs/loki//operations/storage/logs-deletion/) to delete log entries from a specific stream. ## Example Configuration