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!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2