Documentation

Flux

Related to "Filters"

filter() function

filter() filters data based on conditions defined in a predicate function (fn).

hourSelection() function

hourSelection() filters rows by time values in a specified hour range.

range() function

range() filters rows based on time bounds.

geo.filterRows() function

geo.filterRows() filters data by a specified geographic region with the option of strict filtering.

geo.gridFilter() function

geo.gridFilter() filters data by a specified geographic region.

geo.strictFilter() function

geo.strictFilter() filters data by latitude and longitude in a specified region.

query.filterFields() function

query.filterFields() filters input data by field.

query.filterMeasurement() function

query.filterMeasurement() filters input data by measurement.

query.fromRange() function

query.fromRange() returns all data from a specified bucket within given time bounds.

© 2025 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, 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