From 768fb5b04ffb4948f2d5680da558069b4eb1238e Mon Sep 17 00:00:00 2001 From: Julie Stickler Date: Mon, 21 Oct 2024 12:07:38 -0400 Subject: [PATCH] docs: support clarification for filesystem --- docs/sources/operations/storage/filesystem.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/sources/operations/storage/filesystem.md b/docs/sources/operations/storage/filesystem.md index d97a80e7823d..68ca759cafbc 100644 --- a/docs/sources/operations/storage/filesystem.md +++ b/docs/sources/operations/storage/filesystem.md @@ -1,8 +1,8 @@ --- title: Filesystem object store -menuTitle: Filesystem object store +menuTitle: Filesystem object store description: Describes the features and limitations of using a filesystem object store with Loki. -weight: 300 +weight: 300 --- # Filesystem object store @@ -20,7 +20,7 @@ A folder is created for every tenant all the chunks for one tenant are stored in If Loki is run in single-tenant mode, all the chunks are put in a folder named `fake` which is the synthesized tenant name used for single tenant mode. -See [multi-tenancy]({{< relref "../multi-tenancy" >}}) for more information. +See [multi-tenancy](https://grafana.com/docs/loki//operations/multi-tenancy/) for more information. ## Pros @@ -30,6 +30,8 @@ Great for low volume applications, proof of concepts, and just playing around wi ## Cons +The filesystem is not supported by Grafana Labs for production environments (for those customers who have purchased a support contract). + ### Scaling At some point there is a limit to how many chunks can be stored in a single directory, for example see [issue #1502](https://github.com/grafana/loki/issues/1502) which explains how a Loki user ran into a strange error with about **5.5 million chunk files** in their file store (and also a workaround for the problem). @@ -44,4 +46,4 @@ The durability of the objects is at the mercy of the filesystem itself where oth ### High Availability -Running Loki clustered is not possible with the filesystem store unless the filesystem is shared in some fashion (NFS for example). However using shared filesystems is likely going to be a bad experience with Loki just as it is for almost every other application. +Running Loki clustered is not possible with the filesystem store unless the filesystem is shared in some fashion (NFS for example). However using shared filesystems is likely going to be a bad experience with Loki just as it is for almost every other application.