ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #influxdb
Learn how InfluxDB continuous queries automate downsampling, keep raw data intact, and improve query performance—complete with a step‑by‑step example and practical verification tips.
Stop wasting disk space on raw time-series data. Learn how to use InfluxDB downsampling to preserve long-term trends while reducing storage costs and query latency.
Identify and fix InfluxDB disk bloat and query lag caused by infinite retention policies or oversized shard groups with a step‑by‑step diagnostic guide.
When data disappears or queries fail, a common culprit is an incorrectly set bucket retention policy. This guide walks through the symptoms, diagnostic steps, and fixes for retention‑policy misconfigurations in InfluxDB 2.x.
Learn how to combine InfluxDB retention policies with continuous queries to keep high‑resolution recent data while automatically downsampling older points for efficient long‑term storage.
When InfluxDB deletes data it removes entire shards, not individual points. Aligning shard group duration with retention policies lets you age data efficiently while keeping I/O low and disk usage predictable.
Learn how to balance disk usage and historical visibility in InfluxDB by choosing between simple bucket retention and Flux-based downsampling tasks.
Scenario When the query-concurrency-limit setting is enabled in InfluxDB 2.7 to restrict simultaneous Flux query execution, users report increased latency for certain analytical queries that previously completed within sub‑second times. Goal Determine whether the observed latency increase stems from the query scheduler hitting the concurrency limit or from h
InfluxDB 2.x replaces the 1.x retention policy model with a bucket-based retention system, creating an unresolved compatibility question for users upgrading existing databases. The documented upgrade path does not automatically migrate retention policy names as bucket labels, leaving the mapping of original policy identifiers to new bucket names as a decisio