Documentation

truncateTimeColumn() function

truncateTimeColumn() truncates all input time values in the _time to a specified unit.

Truncate to weeks

When truncating a time value to the week (1w), weeks are determined using the Unix epoch (1970-01-01T00:00:00Z UTC). The Unix epoch was on a Thursday, so all calculated weeks begin on Thursday.

Function type signature
(<-tables: stream[{B with _time: C}], unit: duration, ?timeColumn: A) => stream[{B with _time: C, _time: time}] where C: Timeable

For more information, see Function type signatures.

Parameters

unit

(Required) Unit of time to truncate to.

Example units:

  • 1ns (nanosecond)
  • 1us (microsecond)
  • 1ms (millisecond)
  • 1s (second)
  • 1m (minute)
  • 1h (hour)
  • 1d (day)
  • 1w (week)
  • 1mo (month)
  • 1y (year)

timeColumn

Time column to truncate. Default is _time.

Note: Currently, assigning a custom value to this parameter will have no effect.

tables

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

Examples

Truncate all time values to the minute

import "sampledata"

sampledata.int()
    |> truncateTimeColumn(unit: 1m)

View example input and output


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