-
Notifications
You must be signed in to change notification settings - Fork 525
doc: on how to set right cardinality limit #2998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2998 +/- ##
=====================================
Coverage 81.1% 81.1%
=====================================
Files 126 126
Lines 24794 24794
=====================================
Hits 20131 20131
Misses 4663 4663 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
the cardinality limit to 1,000. Delta temporality allows the SDK to reset | ||
after each export, accommodating different attribute combinations across | ||
intervals without accumulating state. | ||
* **Example 2:** For web applications with known Request Per Second (RPS) rates, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have some concerns about using this example. It might be confusing to people who rely on metrics to calculate RPS in the first place.
above), use the same calculation approach as cumulative temporality. | ||
* For dynamic scenarios where not all combinations appear in every export cycle, | ||
base the limit on expected total measurements within a single interval. | ||
* **Example 1:** If your application generates at most 1,000 distinct attribute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about putting the examples along with their respective scenarios?
- When all possible attribute combinations are known... Use Example1 here
- For dynamic scenarios where not all combinations appear in every export cycle, ... Use Example 2 here
Overall doc is still WIP, but adding some more useful information about setting right cardinality limit.