Skip to content

Commit c8be674

Browse files
Fixed headings and formatting issues (#136)
1 parent 183af40 commit c8be674

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

docs/user-guide/management/aggregation-cache.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,8 @@ This page explains what Streaming Aggregation is and shows how to use it to impr
5252

5353
---
5454

55-
## How it work
55+
## How does it work?
56+
5657

5758
**First run: partitioning and caching aggregate factors** <br>
5859
When an aggregation query runs for the first time, OpenObserve divides the requested time range into fixed-size partitions. Each partition is processed separately. Instead of storing the final aggregates, OpenObserve caches the factors required to compute the aggregate. For example, it caches sums and counts, which can later be combined to produce averages.
@@ -64,7 +65,9 @@ This page explains what Streaming Aggregation is and shows how to use it to impr
6465

6566
---
6667

67-
## How it handles late-arriving data
68+
69+
## How does it handle late-arriving data?
70+
6871
To handle late-arriving data, OpenObserve applies a delay window before marking aggregation results as eligible to cache.
6972
The system compares the query time with the end of the selected time range. If the end of the range falls within the delay window, the result is not cached. This ensures that results include all delayed records before being stored.
7073
The delay window is configured through the environment variable `ZO_CACHE_DELAY_SECS`. The default value is 300 secs (5 minutes). You can adjust this value to match the ingestion delay in your environment. For example, if logs typically arrive with up to 10 minutes of delay, set the variable to 600 secs.
@@ -126,6 +129,8 @@ This page explains what Streaming Aggregation is and shows how to use it to impr
126129
## Cacheability of Queries
127130
Not all queries can benefit from aggregation cache. For a query to be cacheable, OpenObserve must be able to store and safely merge intermediate results across partitions.
128131

132+
---
133+
129134
## Supported aggregate functions
130135
The following aggregates are directly supported for caching:
131136

@@ -147,6 +152,8 @@ This page explains what Streaming Aggregation is and shows how to use it to impr
147152
- [approx_topk](https://openobserve.ai/docs/sql-functions/approximate-aggregate/approx-topk/)
148153
- [approx_topk_distinct](http://openobserve.ai/docs/sql-functions/approximate-aggregate/approx-topk-distinct/)
149154

155+
---
156+
150157
=== "How to use"
151158

152159
## How to use streaming aggregation

0 commit comments

Comments
 (0)