open-telemetry / open-telemetry/sig-developer-experience
Support dynamic enrichment and customization for telemetry collected by instrumentation libraries
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 7
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 3
Description
Some of the issues raised in spec and semconv are related to interaction between application and instrumentation code (or different layers of instrumentations):
- classifying errors - it's context-dependent
- enriching telemetry - e.g. add specific attributes to metric depending on the specific context call is made in.
- suppressing all nested instrumentations or duplicates in certain scope
See https://github.com/open-telemetry/opentelemetry-specification/issues/4131#issuecomment-2302625979 for the context.
Such customizations are sometimes possible for spans (using SpanProcessors), but not in general possible for metrics.
I'd like to propose tackling this issue in scope of the devex project.
Contributor guide
No contributing guide indexed for this repository
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 with the linked OpenTelemetry specification issue and its referenced comment, then compare the current customization options for spans and metrics described here. Define the supported scope for error classification, telemetry enrichment, and suppression across application and instrumentation layers; done requires an agreed design for the DevEx project.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100