Documentation

InfluxDB data schema

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!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, 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

InfluxDB Cloud powered by TSM