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)
  • Copy
  • Fill window

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",
)
  • Copy
  • Fill window

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)
  • Copy
  • Fill window

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)
  • Copy
  • Fill window

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_measurement
Tag key
host
_field_value
2021-01-01T00:00:00Z2021-01-02T00:00:00Z2021-01-01T00:00:00Zfoohost1bar1.2
Time range start
2021-01-01T00:00:00Z
Time range stop
2021-01-02T00:00:00Z
Timestamp
2021-01-01T01:00:00Z
Measurement name
foo
Tag value
host1
Field key
bar
Field value
1.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!


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.

Read more

InfluxDB 3 Core and Enterprise are now in Beta

InfluxDB 3 Core and Enterprise are now available for beta testing, available under MIT or Apache 2 license.

InfluxDB 3 Core is a high-speed, recent-data engine that collects and processes data in real-time, while persisting it to local disk or object storage. InfluxDB 3 Enterprise is a commercial product that builds on Core’s foundation, adding high availability, read replicas, enhanced security, and data compaction for faster queries. A free tier of InfluxDB 3 Enterprise will also be available for at-home, non-commercial use for hobbyists to get the full historical time series database set of capabilities.

For more information, check out: