Documentation

Sort and limit data with Flux

This page documents an earlier version of InfluxDB OSS. InfluxDB 3 Core is the latest stable version.

Use the sort()function to order records within each table by specific columns and the limit() function to limit the number of records in output tables to a fixed number, n.

If you’re just getting started with Flux queries, check out the following:

Example sorting system uptime

The following example orders system uptime first by region, then host, then value.

from(bucket:"db/rp")  |> range(start:-12h)  |> filter(fn: (r) =>  r._measurement == "system" and  r._field == "uptime"  )  |> sort(columns:["region", "host", "_value"])

The limit() function limits the number of records in output tables to a fixed number, n. The following example shows up to 10 records from the past hour.

from(bucket:"db/rp")  |> range(start:-1h)  |> limit(n:10)

You can use sort() and limit() together to show the top N records. The example below returns the 10 top system uptime values sorted first by region, then host, then value.

from(bucket:"db/rp")  |> range(start:-12h)  |> filter(fn: (r) =>  r._measurement == "system" and  r._field == "uptime"  )  |> sort(columns:["region", "host", "_value"])  |> limit(n:10)

You now have created a Flux query that sorts and limits data. Flux also provides the top() and bottom() functions to perform both of these functions at the same time.


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