Skip to content

Commit f5121bd

Browse files
committed
tweak delta
1 parent 6bed9e1 commit f5121bd

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/metrics.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -604,15 +604,15 @@ However, if you know that certain combinations will never occur (for example, if
604604
##### Choosing the Right Limit for Delta Temporality
605605

606606
Delta metrics reset their aggregation state after every export interval. This
607-
approach enables more efficient memory utilization by focusing on attributes
608-
observed during each interval rather than tracking all possible combinations.
609-
610-
* For scenarios with predictable attribute combinations (as in the fruit
611-
example), you can use the same calculation method as with cumulative
612-
temporality.
613-
* Delta temporality particularly excels when dealing with high-cardinality
614-
dimensions like `user_id`, where the active set changes dynamically over time
615-
and only a subset is active during any given export interval.
607+
approach enables more efficient memory utilization by focusing only on attributes
608+
observed during each interval rather than maintaining state for all combinations.
609+
610+
* **When attributes are low-cardinality** (as in the fruit example), simply use the same
611+
calculation method as with cumulative temporality.
612+
* **When high-cardinality attribute(s) exist** like `user_id`, leverage Delta temporality's
613+
"forget state" nature to set a much lower limit based on active usage patterns.
614+
This is where Delta temporality truly excels - when the set of active values
615+
changes dynamically and only a small subset is active during any given interval.
616616

617617
###### Example - High Cardinality Attribute Scenario
618618

0 commit comments

Comments
 (0)