Get started with InfluxDB Clustered

Limited availability

InfluxDB Clustered is currently 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.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster hosted and managed on your own infrastructure and is the platform purpose-built to collect, store, and query time series data. It is powered by the InfluxDB 3.0 storage engine which provides a number of benefits including nearly unlimited series cardinality, improved query performance, and interoperability with widely used data processing tools and platforms.

Time series data is a sequence of data points indexed in time order. Data points typically consist of successive measurements made from the same source and are used to track changes over time. Examples of time series data include:

  • Industrial sensor data
  • Server performance metrics
  • Heartbeats per minute
  • Electrical activity in the brain
  • Rainfall measurements
  • Stock prices

This multi-part tutorial walks you through writing time series data to your InfluxDB cluster, querying, and then visualizing that data.

Key concepts before you get started

Before you get started using InfluxDB, it’s important to understand how time series data is organized and stored in InfluxDB and some key definitions that are used throughout this documentation.

Data organization

The InfluxDB Clustered data model organizes time series data into databases and measurements. A database can contain multiple measurements. Measurements contain multiple tags and fields.

  • Database: Named location where time series data is stored. A database can contain multiple measurements.
    • Measurement: Logical grouping for time series data. All points in a given measurement should have the same tags. A measurement contains multiple tags and fields.
      • Tags: Key-value pairs that provide metadata for each point–for example, something to identify the source or context of the data like host, location, station, etc. Tag values may be null.
      • Fields: Key-value pairs with values that change over time–for example, temperature, pressure, stock price, etc. Field values may be null, but at least one field value is not null on any given row.
      • Timestamp: Timestamp associated with the data. When stored on disk and queried, all data is ordered by time. A timestamp is never null.

Schema on write

When using InfluxDB, you define your schema as you write your data. You don’t need to create measurements (equivalent to a relational table) or explicitly define the schema of the measurement. Measurement schemas are defined by the schema of data as it is written to the measurement.

Important definitions

The following definitions are important to understand when using InfluxDB:

  • Point: Single data record identified by its measurement, tag keys, tag values, field key, and timestamp.
  • Series: A group of points with the same measurement, tag keys and values, and field key.
  • Primary key: Columns used to uniquely identify each row in a table. Rows are uniquely identified by their timestamp and tag set. A row’s primary key tag set does not include tags with null values.
Example InfluxDB query results

name: weather


Tools to use

Throughout this tutorial, there are multiple tools you can use to manage and interact with your InfluxDB cluster. Examples are provided for each of the following:

InfluxDB client libraries

InfluxDB v1 and v2 client libraries are language-specific clients that interact with the InfluxDB HTTP v1 and v2 API. Examples for client libraries are not provided in this tutorial, but these can be used to perform actions outlined in this tutorial.


InfluxDB Clustered requires authentication using tokens.

There are two types of tokens:

  • Database token: A token that grants read and write access to InfluxDB databases.

  • Management token: A short-lived (1 hour) Auth0 token used to administer your InfluxDB cluster. These are generated by the influxctl and do not require any direct management. Management tokens authorize a user to perform tasks related to:

    • Account management
    • Database management
    • Database token management
    • Pricing

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:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.