Enable Loki bloom filters to accelerate needle-in-haystack log queries

domain: grafana.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Confirm your ingestion volume and deployment mode justify bloom filters — this is an experimental feature intended for large, fully microservice Loki deployments, not single-binary setups
  2. Enable `bloom_build.enabled: true` and `bloom_gateway.enabled: true` in the relevant component configs
  3. Enable per-tenant bloom creation via `limits_config.bloom_creation_enabled` and related per-tenant bloom settings
  4. Deploy the Bloom Planner and Bloom Builder components to build blocks, and the Bloom Gateway to serve filtering requests to the index gateway
  5. Run queries that filter on high-cardinality structured metadata fields (e.g. trace IDs) and confirm reduced query latency
  6. Monitor bloom build lag and storage usage since blocks are built asynchronously

Known gotchas

Related routes

Ingest and query Loki structured metadata instead of embedding high-cardinality fields in log labels
grafana.com · 6 steps · unrated
Write Loki LogQL queries using log pipeline stages and metric queries to extract and aggregate structured fields from logs
grafana.com · 5 steps · unrated
Read Haystack entities from the 75F platform by filter or by id
support.75f.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans