Documentation

query.inBucket() function

query.inBucket() is experimental and subject to change at any time.

query.inBucket() queries data from a specified InfluxDB bucket within given time bounds, filters data by measurement, field, and optional predicate expressions.

Function type signature
(  bucket: string,  measurement: A,  start: B,  ?fields: [string],  ?predicate: (  r: {  C with  _value: D,  _time: time,  _stop: time,  _start: time,  _measurement: string,  _field: string,  },  ) => bool,  ?stop: E, ) => stream[{  C with  _value: D,  _time: time,  _stop: time,  _start: time,  _measurement: string,  _field: string, }] where A: Equatable

For more information, see Function type signatures.

Parameters

bucket

(Required) InfluxDB bucket name.

measurement

(Required) InfluxDB measurement name to filter by.

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

fields

Fields to filter by. Default is [].

predicate

Predicate function that evaluates column values and returns true or false. Default is (r) => true.

Records (r) are passed to the function. Those that evaluate to true are included in the output tables. Records that evaluate to null or false are not included in the output tables.

Examples

Query specific fields in a measurement from InfluxDB

import "experimental/query"  query.inBucket(  bucket: "example-buckt",  start: -1h,  measurement: "mem",  fields: ["field1", "field2"],  predicate: (r) => r.host == "host1", )

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