You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 SDK level cardinality limit is the limit on the number of metric points during a collection cycle, not measurements.
The SDK level cardinality limit applies to metrics (e.g. each metric can have its own cardinality limit).
The SDK simply does not see metric streams. Metric streams are observed by the receiver (e.g. collector, backend).
Concrete examples will be provided in the spec, which will help the reader to understand these terms.
The text was updated successfully, but these errors were encountered:
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
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.
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: