Documentation

Query first and last values

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

Use first() or last() to return the first or last record in an input table.

data
    |> first()

// OR

data
    |> last()

By default, InfluxDB returns results sorted by time, however you can use the sort() function to change how results are sorted. first() and last() respect the sort order of input data and return records based on the order they are received in.

first

first() returns the first non-null record in an input table.

Given the following input:

_time_value
2020-01-01T00:01:00Z1.0
2020-01-01T00:02:00Z1.0
2020-01-01T00:03:00Z2.0
2020-01-01T00:04:00Z3.0

The following function returns:

|> first()
_time_value
2020-01-01T00:01:00Z1.0

last

last() returns the last non-null record in an input table.

Given the following input:

_time_value
2020-01-01T00:01:00Z1.0
2020-01-01T00:02:00Z1.0
2020-01-01T00:03:00Z2.0
2020-01-01T00:04:00Z3.0

The following function returns:

|> last()
_time_value
2020-01-01T00:04:00Z3.0

Use first() or last() with aggregateWindow()

Use first() and last() with aggregateWindow() to select the first or last records in time-based groups. aggregateWindow() segments data into windows of time, aggregates data in each window into a single point using aggregate or selector functions, and then removes the time-based segmentation.

Given the following input:

_time_value
2020-01-01T00:00:00Z10
2020-01-01T00:00:15Z12
2020-01-01T00:00:45Z9
2020-01-01T00:01:05Z9
2020-01-01T00:01:10Z15
2020-01-01T00:02:30Z11

The following function returns:

|> aggregateWindow(every: 1h, fn: first)
_time_value
2020-01-01T00:00:59Z10
2020-01-01T00:01:59Z9
2020-01-01T00:02:59Z11
|> aggregateWindow(every: 1h, fn: last)
_time_value
2020-01-01T00:00:59Z9
2020-01-01T00:01:59Z15
2020-01-01T00:02:59Z11

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