Skip to content
/ docs Public

Conversation

@tobim
Copy link
Member

@tobim tobim commented Jan 8, 2026

Summary

Documents the new options argument for the summarize operator that enables
periodic emission of aggregation results at fixed intervals:

  • Added frequency parameter documentation for setting emission intervals
  • Added mode parameter documentation (reset, cumulative, update modes)
  • Added usage examples for each emission mode

Related PRs

Documents the new `options` argument for the summarize operator that enables
periodic emission of aggregation results at fixed intervals. Covers:

- `frequency` parameter for setting emission interval
- `mode` parameter with reset, cumulative, and update modes
- Usage examples for each mode

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@github-actions github-actions bot added the reference Reference documentation label Jan 8, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 8, 2026

🚀 Preview deployed!

Visit the preview at: https://tenzir-docs-preview-153.surge.sh

This preview will be updated automatically on new commits.

@mavam mavam force-pushed the main branch 2 times, most recently from 52a0bca to 429deec Compare January 11, 2026 14:04
tobim added a commit to tenzir/tenzir that referenced this pull request Jan 25, 2026
This PR adds frequency-based emission to the summarize operator,
enabling periodic output of aggregation results at fixed intervals
instead of only at the end of input. This enables streaming use cases
where you want real-time updates on aggregations.

The feature is controlled via the `options` named argument:

```tql
summarize count(this), src_ip, options={frequency: 5s, mode: "reset"}
```

Three emission modes are supported:

- **reset** (default): Reset aggregations after each emission, providing
per-interval metrics
- **cumulative**: Accumulate values across emissions, providing running
totals
- **update**: Accumulate values but only emit when they change from the
previous emission, reducing noise in monitoring scenarios

The operator always emits final results when the input stream ends,
regardless of the frequency setting.

## Related PRs

- Documentation: tenzir/docs#153
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

reference Reference documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants