From 92103059949cf4d4a968abc796ba7715e53d442f Mon Sep 17 00:00:00 2001 From: Steven Dungan <114922977+stevendungan@users.noreply.github.com> Date: Fri, 22 Nov 2024 12:48:05 -0500 Subject: [PATCH] docs: Update Blooms docs (#15081) (cherry picked from commit 3aad529f651aa8c9543de375a73e392c167c81b7) --- docs/sources/get-started/labels/structured-metadata.md | 2 -- docs/sources/operations/bloom-filters.md | 1 + 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/sources/get-started/labels/structured-metadata.md b/docs/sources/get-started/labels/structured-metadata.md index f51bda629120..f52cd035c9b6 100644 --- a/docs/sources/get-started/labels/structured-metadata.md +++ b/docs/sources/get-started/labels/structured-metadata.md @@ -26,8 +26,6 @@ You should only use structured metadata in the following situations: - If you are using [Explore Logs](https://grafana.com/docs/grafana-cloud/visualizations/simplified-exploration/logs/) to visualize and explore your Loki logs. You must set `discover_log_levels` and `allow_structured_metadata` to `true` in your Loki configuration. - If you are a large-scale customer, who is ingesting more than 75TB of logs a month and are using [Bloom filters](https://grafana.com/docs/loki//operations/bloom-filters/) (Experimental), starting in [Loki 3.3](https://grafana.com/docs/loki//release-notes/v3-3/) Bloom filters now utilize structured metadata. -We do not recommend extracting information that already exists in your log lines and putting it into structured metadata. - ## Attaching structured metadata to log lines You have the option to attach structured metadata to log lines in the push payload along with each log line and the timestamp. diff --git a/docs/sources/operations/bloom-filters.md b/docs/sources/operations/bloom-filters.md index 4704adc8e1d9..6d7ae93066a5 100644 --- a/docs/sources/operations/bloom-filters.md +++ b/docs/sources/operations/bloom-filters.md @@ -15,6 +15,7 @@ aliases: {{< admonition type="warning" >}} This feature is an [experimental feature](/docs/release-life-cycle/). Engineering and on-call support is not available. No SLA is provided. Note that this feature is intended for users who are ingesting more than 75TB of logs a month, as it is designed to accelerate queries against large volumes of logs. +Query acceleration via Bloom filters is enabled for select Grafana Cloud customers ingesting more that 75TB of logs a month. {{< /admonition >}} Loki leverages [bloom filters](https://en.wikipedia.org/wiki/Bloom_filter) to speed up queries by reducing the amount of data Loki needs to load from the store and iterate through.