Documentation

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.

from(
    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.

_start_stop_time_measurementhost_field_value
2021-01-01T00:00:00Z2021-01-02T00:00:00Z2021-01-01T00:00:00Zfoohost1bar1.2
2021-01-01T00:00:00Z2021-01-02T00:00:00Z2021-01-01T01:00:00Zfoohost1bar1.6
2021-01-01T00:00:00Z2021-01-02T00:00:00Z2021-01-01T02:00:00Zfoohost1bar2.1
_start_stop_time_measurementhost_field_value
2021-01-01T00:00:00Z2021-01-02T00:00:00Z2021-01-01T00:00:00Zfoohost2bar1.2
2021-01-01T00:00:00Z2021-01-02T00:00:00Z2021-01-01T01:00:00Zfoohost2bar1.7
2021-01-01T00:00:00Z2021-01-02T00:00:00Z2021-01-01T02:00:00Zfoohost2bar2.1

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!


Linux Package Signing Key Rotation

All signed InfluxData Linux packages have been resigned with an updated key. If using Linux, you may need to update your package configuration to continue to download and verify InfluxData software packages.

For more information, see the Linux Package Signing Key Rotation blog post.

InfluxDB Cloud backed by InfluxDB IOx

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by IOx, this is the correct documentation.

If powered by TSM, see the TSM-based InfluxDB Cloud documentation.

InfluxDB Cloud backed by InfluxDB TSM

All InfluxDB Cloud organizations created on or after January 31, 2023 are backed by the new InfluxDB IOx storage engine which enables nearly unlimited series cardinality and SQL query support. Check the right column of your InfluxDB Cloud organization homepage to see which InfluxDB storage engine you’re using.

If powered by TSM, this is the correct documentation.

If powered by IOx, see the IOx-based InfluxDB Cloud documentation.

State of the InfluxDB Cloud (IOx) documentation

The new documentation for InfluxDB Cloud backed by InfluxDB IOx 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.