Documentation

influxdb.select() function

influxdb.select() is a user-contributed function maintained by the package author.

influxdb.select() is an alternate implementation of from(), range(), filter() and pivot() that returns pivoted query results and masks the _measurement, _start, and _stop columns. Results are similar to those returned by InfluxQL SELECT statements.

Function type signature
(
    from: string,
    m: A,
    start: B,
    ?fields: [string],
    ?host: string,
    ?org: string,
    ?stop: C,
    ?token: string,
    ?where: (
        r: {
            D with
            _value: E,
            _time: time,
            _stop: time,
            _start: time,
            _measurement: string,
            _field: string,
        },
    ) => bool,
) => stream[F] where A: Equatable, F: Record

For more information, see Function type signatures.

Parameters

from

(Required) Name of the bucket to query.

start

(Required) Earliest time to include in results.

Results include points that match the specified start time. Use a relative duration, absolute time, or integer (Unix timestamp in seconds). For example, -1h, 2019-08-28T22:00:00Z, or 1567029600. Durations are relative to now().

stop

Latest time to include in results. Default is now().

Results exclude points that match the specified stop time. Use a relative duration, absolute time, or integer (Unix timestamp in seconds). For example, -1h, 2019-08-28T22:00:00Z, or 1567029600. Durations are relative to now().

m

(Required) Name of the measurement to query.

fields

List of fields to query. Default is[].

Returns all fields when list is empty or unspecified.

where

Single argument predicate function that evaluates true or false and filters results based on tag values. Default is (r) => true.

Records are passed to the function before fields are pivoted into columns. Records that evaluate to true are included in the output tables. Records that evaluate to null or false are not included in the output tables.

host

URL of the InfluxDB instance to query.

See InfluxDB OSS URLs or InfluxDB Cloud regions.

org

Organization name.

token

InfluxDB API token.

Examples

Query a single field

import "contrib/jsternberg/influxdb"

influxdb.select(from: "example-bucket", start: -1d, m: "example-measurement", fields: ["field1"])

Query multiple fields

import "contrib/jsternberg/influxdb"

influxdb.select(
    from: "example-bucket",
    start: -1d,
    m: "example-measurement",
    fields: ["field1", "field2", "field3"],
)

Query all fields and filter by tags

import "contrib/jsternberg/influxdb"

influxdb.select(
    from: "example-bucket",
    start: -1d,
    m: "example-measurement",
    where: (r) => r.host == "host1" and r.region == "us-west",
)

Query data from a remote InfluxDB Cloud instance

import "contrib/jsternberg/influxdb"
import "influxdata/influxdb/secrets"

token = secrets.get(key: "INFLUXDB_CLOUD_TOKEN")

influxdb.select(
    from: "example-bucket",
    start: -1d,
    m: "example-measurement",
    fields: ["field1", "field2"],
    host: "https://us-west-2-1.aws.cloud2.influxdata.com",
    org: "example-org",
    token: token,
)

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