Documentation

date.sub() function

date.sub() subtracts a duration from a time value and returns the resulting time value.

Function type signature
(d: duration, from: A, ?location: {zone: string, offset: duration}) => time where A: Timeable

For more information, see Function type signatures.

Parameters

from

(Required) Time to subtract the duration from.

Use an absolute time or a relative duration. Durations are relative to now().

d

(Required) Duration to subtract.

location

Location to use for the time value.

Examples

Subtract six hours from a timestamp

import "date"

date.sub(from: 2019-09-16T12:00:00Z, d: 6h)// Returns 2019-09-16T06:00:00.000000000Z

Subtract six hours from a relative duration

import "date"

option now = () => 2022-01-01T12:00:00Z

date.sub(d: 6h, from: -3h)// Returns 2022-01-01T03:00:00.000000000Z

Subtract two days from one hour ago

A time may be represented as either an explicit timestamp or as a relative time from the current now time. sub can support either type of value.

import "date"

option now = () => 2021-12-10T16:27:40Z

date.sub(from: -1h, d: 2d)// Returns 2021-12-08T15:27:40Z

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