Documentation

LIMIT and SLIMIT clauses

Use LIMIT to limit the number of rows returned per InfluxQL group. Use SLIMIT to limit the number of series returned in query results.

LIMIT clause

The LIMIT clause limits the number of rows to return from each InfluxQL group. If the query doesn’t include a GROUP BY clause, the entire result set is considered a single group. If a query groups data by time, limits are applied after aggregate and selector operations are applied to each time window.

Syntax

SELECT_clause FROM_clause [WHERE_clause] [GROUP_BY_clause] [ORDER_BY_clause] LIMIT N

Arguments

  • N: Maximum number of points to return from each InfluxQL group. If N is greater than the number of points in a group, all points from the group are returned.

Examples

The following examples use the Home sensor sample data.

Limit the number of rows returned

Limit the number of rows returned from each InfluxQL group

SLIMIT clause

InfluxQL is being rearchitected to work with the InfluxDB 3 storage engine. This process is ongoing and some InfluxQL features, such as SLIMIT are still being implemented. For more information, see InfluxQL feature support.


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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