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
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Describe the bug
Some metrics don't follow Otel semantic conventions
Steps to reproduce
Nothing to reproduce. The problem lies in the specification of the receiver itself.
What did you expect to see?
Metrics should use brackets (
{}
) for units that count objects, and not1
which is reserved for fractions and ratios:saphana.license.limit
==> unit{licenses}
(or empty)What did you see instead?
Some metrics improperly use unit
1
which is reserved for fractions and ratios:saphana.license.limit
saphana.license.peak
What version did you use?
Main branch
What config did you use?
N/A
Environment
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: