Skip to content

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

cijothomas
Copy link
Member

Overall doc is still WIP, but adding some more useful information about setting right cardinality limit.

@cijothomas cijothomas requested a review from a team as a code owner May 23, 2025 01:13
Copy link

codecov bot commented May 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.1%. Comparing base (bf22aeb) to head (9303e40).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@cijothomas cijothomas changed the title Add doc on how to set right cardinality limit doc: on how to set right cardinality limit May 23, 2025
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,
Copy link
Contributor

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
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants