[WIP] Otap enum attrs#3534
Draft
lquerel wants to merge 1 commit into
Draft
Conversation
Pull request dashboard statusStatus last refreshed: 2026-07-22 19:57:54 UTC.
This automated status or its linked feedback items may be incorrect. If something looks wrong, please report it with the result you expected. |
44 tasks
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #3534 +/- ##
==========================================
- Coverage 86.71% 86.70% -0.02%
==========================================
Files 789 790 +1
Lines 319633 320174 +541
==========================================
+ Hits 277179 277610 +431
- Misses 41930 42040 +110
Partials 524 524
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Not ready for review at all!
Change Summary
Refactor the OTAP receiver and exporter internal telemetry to use bounded, enum-based attributes, following the approach introduced for OTLP metrics.
This change:
What issue does this PR close?
How are these changes tested?
Are there any user-facing changes?
Yes. OTAP internal metric names and attribute sets have changed. Metrics now use bounded signal, outcome, and error.type dimensions and consistently follow the receiver.otap.* and exporter.otap.* naming conventions.
Changelog