open-telemetry / open-telemetry/opentelemetry-ruby
Document interaction between View attribute filtering and Exemplars
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
Per spec PR #5073 and the spec compliance matrix update in #5077: when a View filters out attributes, the dropped attributes may still appear on Exemplars, because Exemplars retain measurement attributes that are filtered by aggregation or View configuration.
This behavior is non-obvious and worth documenting in user-facing SDK docs. The .NET docs were updated in opentelemetry-dotnet#7270 and could serve as a reference.
The compliance matrix tracks which SDKs document this:
https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the user-facing Ruby SDK documentation and the behavior described in spec-compliance-matrix.md, then use opentelemetry-dotnet#7270 as the reference example. Done means the Ruby docs clearly explain that View-filtered attributes may still appear on Exemplars.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100