InfluxDB data schema
API token hashing is enabled by default in InfluxDB OSS 2.9.0
Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.
For more information, see Token hashing.
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:
- To view raw data when exploring metrics with InfluxDB
- To return query results in annotated CSV syntax
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:
annotationresulttable
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!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.