Documentation

InfluxDB data schema

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

InfluxDB data elements are stored in time-structured merge tree (TSM) and time series index (TSI) files to efficiently compact stored data.

InfluxDB also provides a tabular data schema that includes the following:

The tabular data schema is used for the following:

Annotation rows

Annotation rows describe column properties, for example:

  • #group
  • #datatype
  • #default

Header row

The header row defines column labels that describe data in each column, for example:

  • table
  • _time
  • _value
  • _field
  • _measurement
  • tag key names (without underscore prefix): tag-1, tag-2

Data rows

Each data row contains the data specified in the header row for one point.

Other columns

In addition to the columns in each data row (specified in the header row), the following columns are optional:

  • annotation
  • result
  • table

Group keys

Determine the contents of output tables in Flux by grouping records that share common values in specified columns. Learn more about grouping your data with Flux.


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 2026, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2