Wavefront includes an implementation of the HoltWinters algorithm, which supports prediction based on existing data. It’s especially useful if your data are highly seasonal. Our implementation includes parameters to specify history length, season length, and sample rate. The alpha
, beta
, and gamma
parameters let you finetune how aggressive the smoothing is. See Exponential Smoothing and other internet resources for info about the algorithm.
See Expanding Wavefront Predictive Analytics  See the Future with HoltWinters Algorithm for indepth discussion of an example.
Overview
HoltWinters triple exponential smoothing is a form of time series analysis that’s used primarily for periodic or seasonal data. Its main strength is catching the overall trend of data over time while maintaining the structure of the data’s seasons.
If you use the hw()
function on a time series with a set periodicity, the function can predict the next event of interest, and, for example, send an alert.
For example, assume that at certain times of the day a set of virtual machines experiences peak load. You could set up an alert for that event, or assign additional CPU and memory to them. If the peak load time changes, for example, because daylight saving time ends, the hw()
function can catch up and adjust the alert or resources.
Syntax and Parameters
The function has the following syntax:
hw(<history_length>, <season_length>, <sampling_rate>, <expression>[, <alpha>, <beta>, <gamma>])
The function has three required and three optional parameters:
Parameter  Description 

history_length  Amount of data that we use to smooth the underlying time series and to forecast. History length is expressed as time before the left side of the widow, so that hw(4w, ...) looks at the last 4 weeks of data before the query starts. If the chart window looks only at future data points, the history length is interpreted as the amount of time before the present instead of the amount of time before the left side of the window.

season_length  Length of one season of data. You need at least two full seasons of data to run the HoltWinters algorithm. 
sampling_rate  Rate at which the function summarizes the points in the underlying expression, similar to the align() function. The sampling rate always uses the average of all points in the time window as the summarization strategy. To use a different summarization strategy, wrap the underlying expression with align() .
For example,
hw(4h, 1h, 1m, align(1m, ts(cpu.usage.idle)))

expression  The time series on which you want to run the HoltWinters algorithm. 
alpha, beta, gamma  Optional coefficients that the HoltWinters algorithm uses to determine how stable and how reactive its forecast is. The values range between 0 and 1, with smaller numbers weighing historical data more, and larger numbers weighing recent data more.
If you don't specify these parameters, the algorithm uses an optimization method called NelderMead. Because NelderMead finds local optima the same query might return two different results if the function is run twice. See Optional Parameters below for details.

Optional Parameters to HoltWinters
Alpha, beta, and gamma are optional parameters that the HoltWinters algorithm uses to determine how stable and how reactive its forecast is.

Alpha affects the weighted average of the points themselves. The weight of every point decays exponentially the further back the point is. When a new point is added to the weighted average, the weight of the new point is alpha, and the weight of the old average is
(1 – alpha)
. Therefore, higher values of alpha cause the algorithm to weight newer points more, making the forecast more reactive and less stable. 
Beta affects the weighted average of the slopes between consecutive points. The algorithm uses an exponentially decaying weighted average of the slope between every two consecutive points, similar to the raw value of the points. This weighted average is calculated in the same way as the weighted average for alpha. Each time a new point is added, the slope between it and the last point is factored in with a weight of beta, while the old weighted average now has weight
(1 – beta)
. Therefore, higher values of beta cause the algorithm to weight the most recent slope higher, making the forecast more reactive and less stable. 
Gamma affects the weighted average of the seasonal offsets. HoltWinters captures seasonal data by measuring the average offset of a given point into a season from the average value of that season. For example, assume history length is four weeks, season length is one week, and sampling rate is one day. Then across the four weeks of history, there is an average amount that each day differs from the average value of the week it occurs in.
Like the alpha and beta, this average is a weighted average, with newer offsets having higher weights. Each time a new point is processed, it impacts the average offset from the season average by a factor of gamma, while the old weighted average offset has a weight of
(1 – gamma)
. Therefore, higher values of gamma cause the algorithm to weight newer points more, making the forecast more reactive and less stable.