Documentation

tail() function

tail() limits each output table to the last n rows.

tail() produces one output table for each input table. Each output table contains the last n records before the offset. If the input table has less than offset + n records, tail() outputs all records before the offset.

Function type signature
(<-tables: stream[A], n: int, ?offset: int) => stream[A]

For more information, see Function type signatures.

Parameters

n

(Required) Maximum number of rows to output.

offset

Number of records to skip at the end of a table table before limiting to n. Default is 0.

tables

Input data. Default is piped-forward data (<-).

Examples

Output the last three rows in each input table

import "sampledata"

sampledata.int()
    |> tail(n: 3)

View example input and output

Output the last three rows before the last row in each input table

import "sampledata"

sampledata.int()
    |> tail(n: 3, offset: 1)

View example input and output


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