InfluxDB stores data whose time of measurement is central to its meaning, such as sensor readings, application metrics or operational events. Applications write those observations and query them to understand changes and trends. It is useful when time-series data is a primary workload rather than an incidental field in ordinary records. InfluxDB's major versions and editions differ substantially, so identify the actual product before choosing clients, query syntax or a Kubernetes package.
Current guidance
The historical link is to the deprecated community stable/influxdb chart. Current InfluxData documentation describes InfluxDB 3 Core as an open-source time-series database with a different architecture and product boundary from older deployments. Identify whether an existing system is InfluxDB 1, 2 or 3 before selecting an image or chart. InfluxData announced a September 15, 2026 switch of influxdb:latest to InfluxDB 3 Core; pin the intended version or digest to avoid an accidental major-version change.
The InfluxDB 3 Core guide documents object-storage or local-disk persistence and compatibility with older write APIs. Write compatibility does not prove that queries, tasks, authentication, retention policies or dashboards migrate unchanged. Inventory the query language and API used by each collector, application and visualization, then validate representative historical and recent-data queries.
Core and Enterprise expose different capabilities; the current product guide places high availability and other features in the Enterprise offering. Choose the edition and recovery design before scaling Kubernetes replicas. Rehearse export, restore and ingestion interruption using the exact intended version, and verify any limits important to the required historical query range. The old chart’s successful installation or a reachable documentation page cannot establish current support for its bundled image.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
InfluxDB is an open-source time series database developed by InfluxData. It is written in Go and optimized for fast, high-availability storage and retrieval of time series data in fields such as operations monitoring, application metrics, Internet of Things sensor data, and real-time analytics. It also has support for processing data from Graphite.
Features
- Built-in HTTP API so you don’t have to write any server-side code to get up and running.
- Data can be tagged, allowing very flexible querying.
- SQL-like query language.
- Simple to install and manage, and fast to get data in and out.
- It aims to answer queries in real-time. That means every data point is indexed as it comes in and is immediately available in queries that should return in < 100ms.
Technical overview
InfluxDB has no external dependencies[6] and provides a SQL-like language with builtin time-centric functions for querying a data structure composed of measurements, series, and points. Each point consists of several key-value pairs called the fieldset and a timestamp. When grouped together by a set of key-value pairs called the tagset, these define a series. Finally, series are grouped together by a string identifier to form a measurement.
Values can be 64-bit integers, 64-bit floating points, strings, and booleans.
Points are indexed by their time and tagset.
Retention policies are defined on a measurement and control how data is downsampled and deleted.
Continuous Queries run periodically, storing results in a target measurement.
High Performance
InfluxDB is a high-performance data store written specifically for time series data. It allows for high throughput ingest, compression and real-time querying of that same data. InfluxDB is written entirely in Go and it compiles into a single binary with no external dependencies. It provides write and query capabilities with the command line interface, the built-in HTTP API, a set of client libraries (like Go, Java, and Javascript to name a few) and with plugins for common data formats such as Telegraf, Graphite, Collected, and OpenTSDB.
SQL-Like Queries
InfluxDB provides InfluxQL as a SQL-like query language for interacting with your data. It has been lovingly crafted to feel familiar to those coming from other SQL or SQL-like environments while also providing features specific to storing and analyzing time series data. InfluxQL also supports regular expressions, arithmetic expressions, and time series specific functions to speed up data processing.
Downsampling and Data Retention
InfluxDB can handle millions of data points per second. Working with that much data over a long period of time can create storage concerns. InfluxDB will automatically compact the data to minimize your storage space. In addition, you can easily downsample the data; keeping the high precision raw data for only a limited time, and storing the lower precision, summarized data for much longer or forever. InfluxDB offers two features, Continuous Queries (CQ) and Retention Policies (RP), that help you automate the process of downsampling data and expiring old data.
Sources & further reading
Spotted something that needs another look?
Help improve this page →