Skip to content
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

[batchprocessor] Update metric units #10658

Merged
merged 4 commits into from
Aug 13, 2024

Conversation

crobert-1
Copy link
Member

Description

1 isn't an informative metric unit. I've made a best-guess attempt at updating metric units, feedback is very necessary here, the units are not very clear here. I attempted to match the unit with metric descriptions.

Semantic conventions for reference.

Link to tracking issue

Fixes #10652

@crobert-1 crobert-1 requested review from a team and mx-psi July 17, 2024 23:30
Copy link

codecov bot commented Jul 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.64%. Comparing base (643c17e) to head (d1862bd).

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #10658   +/-   ##
=======================================
  Coverage   91.64%   91.64%           
=======================================
  Files         406      406           
  Lines       19001    19001           
=======================================
  Hits        17414    17414           
  Misses       1227     1227           
  Partials      360      360           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@mx-psi mx-psi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any way we can ensure consistency in the units used for all components? Maybe having a common list or guidelines about this?

@codeboten
Copy link
Contributor

Is there any way we can ensure consistency in the units used for all components? Maybe having a common list or guidelines about this?

I suspect we'll have better guidelines in the near future with open-telemetry/oteps#259, but maybe we can start a doc in this repo until the otep lands?

@codeboten
Copy link
Contributor

Opened #10695 to provide guidelines around units

codeboten pushed a commit that referenced this pull request Jul 30, 2024
#### Description
Update telemetry units to be more clear. Related to
#10658, we
may be blocked here waiting for official units to use.

Note: I've kept [one
metric](https://github.com/open-telemetry/opentelemetry-collector/blob/7d5b1ba387e4e171e25bfeea9b70d6fdfbe08fab/cmd/mdatagen/internal/samplereceiver/metadata.yaml#L110)
with the unit "1", as it's not meant to be meaningful, just to show a
metric that's disabled by default.

Since this code is internal and only used for tests, from what I can
tell, I don't believe we need a changelog entry.

#### Link to tracking issue
Fixes
#10653
Copy link
Contributor

github-actions bot commented Aug 6, 2024

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Aug 6, 2024
@github-actions github-actions bot removed the Stale label Aug 13, 2024
@codeboten codeboten merged commit 3f4f0d0 into open-telemetry:main Aug 13, 2024
49 checks passed
@github-actions github-actions bot added this to the next release milestone Aug 13, 2024
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.

Review metadata.yaml units for internal telemetry: processor/batchprocessor
3 participants