-
Notifications
You must be signed in to change notification settings - Fork 888
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
Clarify metric stream, point and cardinality limit #3866
Labels
Comments
jack-berg
added
the
triaged-accepted
The issue is triaged and accepted by the OTel community, one can proceed with creating a PR proposal
label
Feb 14, 2024
This was referenced Feb 26, 2024
Merged
carlosalberto
pushed a commit
that referenced
this issue
Mar 13, 2024
Related to #3866. The cardinality limit section in the SDK spec uses "metric event" and "event" which could be confusing (especially considering we already have span events and event API...). Given we already have "measurement" clearly defined in the API spec, this PR helps to align on the terminology.
austinlparker
added
triage:accepted:ready-with-sponsor
and removed
triaged-accepted
The issue is triaged and accepted by the OTel community, one can proceed with creating a PR proposal
labels
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What are you trying to achieve?
The current specification mentioned Metric, Metric Point, Metric Stream and Timeseries, but not all of them are clearly defined. This has caused confusion, for example #3856.
I plan to make a series of changes to clarify these terms and correct the existing usage in the spec:
The text was updated successfully, but these errors were encountered: