Skip to content

Doc: Tutorial showing cardinality capping and its impact #2902

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
cijothomas opened this issue Apr 4, 2025 · 2 comments · May be fixed by #2946
Open

Doc: Tutorial showing cardinality capping and its impact #2902

cijothomas opened this issue Apr 4, 2025 · 2 comments · May be fixed by #2946
Assignees
Milestone

Comments

@cijothomas
Copy link
Member

Cardinality capping is a relatively difficult topic to understand. A lot of users make incorrect assumptions about the topic. To make life easier, we need to write a full tutorial explaining the concept, and how OTel's approach to reporting overflow can be (and should be) used by users when querying metrics.

I plan to use Aspire dashboard tool for the tutorial, as that is the only OpenSource tool that natively understand's Otel's overflow attribute.
dotnet/aspire#7784

Topics to cover:

  1. What is cardinality limit?
  2. How OTel enforces the limit?
  3. What attributes are subject to the cap (more importantly, what is not subject to cap)
  4. How users should plan for cardinality limit?
  5. How delta vs cumulative influences cardinality limit.
  6. How to leverage overflow signal, to avoid making incorrect decisions based on Metric data. (Most important!)
@cijothomas cijothomas self-assigned this Apr 4, 2025
@cijothomas cijothomas added this to the 0.30 milestone Apr 4, 2025
@cijothomas
Copy link
Member Author

https://github.com/open-telemetry/opentelemetry-rust/pull/2901/files PR adding Cardinality Capping feature.

@scottgerring
Copy link
Contributor

I don't know anything about cardinality capping and would love to use my beginner's mind to review this when you're done.

@cijothomas cijothomas linked a pull request Apr 29, 2025 that will close this issue
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 a pull request may close this issue.

2 participants