I was reading through some Kapacitor documentation about the WindowNode. Specifically with the WindowNode, there’s two properties:
period(): Time range of collected data
every(): Frequency window is passed to the next node in pipe
Both of these make sense, but I was a little curious about the practicality of the example in the docs:
stream |window() .period(10m) .every(5m) |httpOut('recent')
The docs explain what this is doing, but not why:
This example emits the last 10 minute period every 5 minutes to the pipeline’s httpOut node. Because every is less than period, each time the window is emitted it contains 5 minutes of new data and 5 minutes of the previous period’s data.
If this were your script, what would the advantage be of having overlapping data in the stream? Is there a concern of some of it being dropped? I was curious and wanted to get a better understanding of why someone would want to do this.