open-telemetry / open-telemetry/opentelemetry-java
Add scope attributes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 58
Description
Scopes have attributes. We need to extend our data model to support this, which is particularly important metrics and for the event api where a scope attribute called event.domain seems likely to be required.
There are a number of small things to do for scope attributes to be supported:
- Extend
InstrumentationScopeInfowith attributes #4696 - Extend
TracerBuilderto optionally specify attributes #4711 - Extend
MeterBuilderto optionally specify attributes #4711 - Extend
LogEmitterBuilderto optionally specify attributes #4711 - Serialize scope attributes in OTLP #4712
- Serialize scope attributes in zipkin
- Serialize scope attributes in jaeger
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 remaining checklist items for TracerBuilder, MeterBuilder, and LogEmitterBuilder, then inspect the existing InstrumentationScopeInfo and OTLP serialization work. Check how the Zipkin and Jaeger serializers handle scope data. Done means scope attributes can be supplied through the builders and are serialized for the remaining exporters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100