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!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: