Documentation

holtWinters() function

holtWinters() applies the Holt-Winters forecasting method to input tables.

The Holt-Winters method predicts n seasonally-adjusted values for the specified column at the specified interval. For example, if interval is six minutes (6m) and n is 3, results include three predicted values six minutes apart.

Seasonality

seasonality delimits the length of a seasonal pattern according to interval. If the interval is two minutes (2m) and seasonality is 4, then the seasonal pattern occurs every eight minutes or every four data points. If your interval is two months (2mo) and seasonality is 4, then the seasonal pattern occurs every eight months or every four data points. If data doesn’t have a seasonal pattern, set seasonality to 0.

Space values at even time intervals

holtWinters() expects values to be spaced at even time intervales. To ensure values are spaced evenly in time, holtWinters() applies the following rules:

  • Data is grouped into time-based “buckets” determined by the interval.
  • If a bucket includes many values, the first value is used.
  • If a bucket includes no values, a missing value (null) is added for that bucket.

By default, holtWinters() uses the first value in each time bucket to run the Holt-Winters calculation. To specify other values to use in the calculation, use aggregateWindow to normalize irregular times and apply an aggregate or selector transformation.

Fitted model

holtWinters() applies the Nelder-Mead optimization to include “fitted” data points in results when withFit is set to true.

Null timestamps

holtWinters() discards rows with null timestamps before running the Holt-Winters calculation.

Null values

holtWinters() treats null values as missing data points and includes them in the Holt-Winters calculation.

Function type signature
(
    <-tables: stream[A],
    interval: duration,
    n: int,
    ?column: string,
    ?seasonality: int,
    ?timeColumn: string,
    ?withFit: bool,
    ?withMinSSE: bool,
) => stream[B] where A: Record, B: Record

For more information, see Function type signatures.

Parameters

n

(Required) Number of values to predict.

interval

(Required) Interval between two data points.

withFit

Return fitted data in results. Default is false.

column

Column to operate on. Default is _value.

timeColumn

Column containing time values to use in the calculating. Default is _time.

seasonality

Number of points in a season. Default is 0.

withMinSSE

Return minSSE data in results. Default is false.

minSSE is the minimum sum squared error found when optimizing the holt winters fit to the data. A smaller minSSE means a better fit. Examining the minSSE value can help understand when the algorithm is getting a good fit versus not.

tables

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

Examples

Use holtWinters to predict future values

import "sampledata"

sampledata.int()
    |> holtWinters(n: 6, interval: 10s)

View example input and output

Use holtWinters with seasonality to predict future values

import "sampledata"

sampledata.int()
    |> holtWinters(n: 4, interval: 10s, seasonality: 4)

View example input and output

Use the holtWinters fitted model to predict future values

import "sampledata"

sampledata.int()
    |> holtWinters(n: 3, interval: 10s, withFit: true)

View example input and output


Was this page helpful?

Thank you for your feedback!


InfluxDB OSS 2.9.0: API tokens are hashed by default

Stronger token security in InfluxDB OSS 2.9.0 — tokens are hashed on disk by default. Existing tokens are hashed on first startup and can’t be recovered afterward. Capture any plaintext tokens you still need before you upgrade.

View InfluxDB OSS 2.9.0 release notes

Hashed tokens authenticate exactly like unhashed tokens — clients and integrations keep working.

Also new in 2.9.0:

  • Configurable backup compression
  • Restore support for backups containing hashed tokens
  • Tighter Edge Data Replication queue validation
  • Flux upgrade
  • Compaction reliability improvements

Key enhancements in Explorer 1.9

Explorer 1.9 is now available with InfluxQL support, an AI-assisted Flux to SQL converter (beta), and new live sample data simulators.

View Explorer 1.9 release notes

Explorer 1.9 includes new features and improvements that make it easier to query, visualize, and manage data.

Highlights:

  • Flux to SQL converter (beta): Convert Flux queries to SQL with an AI-assisted converter.
  • InfluxQL support: Query data with InfluxQL in the Data Explorer and dashboards, and save and load InfluxQL queries.
  • InfluxQL visualizations: Render line and bar charts from InfluxQL results with per-tag series grouping.
  • Query error history: Review a history of query errors in the query tool.
  • Live sample data simulators: Generate continuous live sample data with new bird data and signal generator simulators.

For more details, see Explorer 1.9 release notes

InfluxDB 3.10 is now available

InfluxDB 3 Core 3.10 adds an automatic catalog format upgrade, a configurable query-concurrency limit, and processing engine improvements.

Key updates in InfluxDB 3 Core 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • --max-concurrent-queries: limit concurrent queries (adjustable at runtime).
  • GET /ready endpoint for readiness probes.
  • Processing engine: cross-database queries and trigger lockdown flags.

For more information, see the InfluxDB 3 Core release notes.

InfluxDB 3.10 is now available

InfluxDB 3 Enterprise 3.10 adds automated backup and restore, row-level deletions, and user management, with an automatic catalog format upgrade and performance preview improvements.

Key updates in InfluxDB 3 Enterprise 3.10:

  • Catalog format upgrade: the on-disk catalog automatically upgrades from format v2 to v3 on first 3.10 startup. Migration is one-way—back up your catalog before upgrading.
  • Automated backup and restore (beta)
  • Row-level deletions
  • User management (authentication and RBAC) — preview
  • Performance preview improvements

Backup and restore, row-level deletions, and the performance preview require the Enterprise storage engine upgrade (opt-in beta). Beta and preview features are subject to breaking changes and aren’t recommended for production use.

For more information, see the InfluxDB 3 Enterprise release notes

Telegraf Enterprise is now generally available

Telegraf Enterprise is now generally available, along with Telegraf Controller v1.0.

Telegraf Enterprise combines Telegraf Controller, a centralized management console for Telegraf, with official support from InfluxData. Manage configurations, monitor fleet health, and operate tens of thousands of Telegraf agents from a single system.

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On September 15, 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