open-telemetry / open-telemetry/opentelemetry-python
Mechanism to configure views with opentelemetry-instrument
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Views are intended to be the main configuration mechanism for metrics instrumentation. For example, dropping a metric or metrics from a given instrumentation. We need a mechanism to specify view configuration with the opentelemetry-instrument auto instrumentation agent. Concerns:
- There has been a lot of community discussion around configuration. If we do implement something, there may be a formal spec later on.
- Maybe check what java agent is doing here
One alternative would be identifying the major use cases and adding simple config flags which we convert to views for auto instrumentation.
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 Java agent's approach to view configuration and the community discussion about configuration. Identify the major auto-instrumentation use cases and compare a view-based mechanism with simple configuration flags; done requires an agreed mechanism that can accommodate a future formal specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100