InfluxDB internals
This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.
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 storage engine
An overview of the InfluxDB storage engine architecture.
InfluxDB file system layout
The InfluxDB file system layout depends on the operating system, package manager, or containerization platform used to install InfluxDB.
Data retention in InfluxDB
The InfluxDB retention service checks for and removes data with timestamps beyond the defined retention period of the bucket the data is stored in.
InfluxDB runtime
Learn how to collect Go runtime profiling and tracing information to help with InfluxDB performance analysis and debugging.
InfluxDB shards and shard groups
Learn the relationships between buckets, shards, and shard groups. InfluxDB organizes time series data into shards when storing data to disk. Shards are grouped into shard groups.
InfluxDB system buckets
InfluxDB system buckets contain time series data used by and generated from the InfluxDB monitoring and alerting system and the task engine.
InfluxDB OSS metrics
Get metrics about the workload performance of an InfluxDB OSS instance.
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.