You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user-guide/management/aggregation-cache.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,8 @@ This page explains what Streaming Aggregation is and shows how to use it to impr
52
52
53
53
---
54
54
55
-
## How it work
55
+
## How does it work?
56
+
56
57
57
58
**First run: partitioning and caching aggregate factors** <br>
58
59
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
64
65
65
66
---
66
67
67
-
## How it handles late-arriving data
68
+
69
+
## How does it handle late-arriving data?
70
+
68
71
To handle late-arriving data, OpenObserve applies a delay window before marking aggregation results as eligible to cache.
69
72
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.
70
73
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
126
129
## Cacheability of Queries
127
130
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.
128
131
132
+
---
133
+
129
134
## Supported aggregate functions
130
135
The following aggregates are directly supported for caching:
131
136
@@ -147,6 +152,8 @@ This page explains what Streaming Aggregation is and shows how to use it to impr
0 commit comments