Query InfluxDB

To query data from InfluxDB using Flux, use from() and range. Provide the following parameters to each function:

  • from():
    • bucket or bucketID: InfluxDB bucket name or bucket ID to query.
  • range():
    • start: Earliest time to return results from.

InfluxDB requires queries to be time-bound, so from() must always be followed by range().

from(bucket: "example-bucket")
    |> range(start: -1h)

Query InfluxDB Cloud or 2.x remotely

To query InfluxDB Cloud or 2.x remotely, provide the following parameters in addition to bucket or bucketID.

    bucket: "example-bucket",
    host: "http://localhost:8086",
    org: "example-org",
    token: "mYSup3r5Ecr3T70keN",

Query InfluxDB 1.x

To query InfluxDB 1.x, use the database-name/retention-policy-name naming convention for your bucket name. For example, to query data from the autogen retention policy in the telegraf database:

from(bucket: "telegraf/autogen")
    |> range(start: -30m)

To query the default retention policy in a database, use the same bucket naming convention, but do not provide a retention policy:

from(bucket: "telegraf/")
    |> range(start: -30m)

Results structure

from() and range() return a stream of tables grouped by series (measurement, tag set, and field). Each table includes the following columns:

  • _start: Query range start time (defined by range())
  • _stop: Query range stop time (defined by range())
  • _time: Data timestamp
  • _measurement: Measurement name
  • _field: Field key
  • _value: Field value
  • Tag columns: A column for each tag where the column label is the tag key and the column value is the tag value

Columns with the underscore prefix

Columns with the underscore (_) prefix are considered “system” columns. Some Flux functions require these columns.

Example InfluxDB query results

Hover over highlighted text to view description.


Structure results like InfluxQL

InfluxQL returns each field as a column where the column label is the field key and the column value is the field value. To structure results similarly with Flux, use pivot() or schema.fieldsAsCols() to pivot fields into columns.

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.