open-telemetry / open-telemetry/opentelemetry-python
Run OTel scenarios without Docker
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Is your feature request related to a problem?
Running an OpenTelemetry scenario (e.g. an instrumented Python server, a client, and a Collector/Docker), then gathering the telemetry it produces, is a common requirement for testers, developers, and learners. Could this be made easier?
Describe the solution you'd like
Would like to be able to define all of the inputs of an OpenTelemetry scenario, point a tool at it, then have the outputs (telemetry) be available in the same place.
Describe alternatives you've considered
There is manual setup, and there's tooling like https://github.com/open-telemetry/opentelemetry-python/tree/main/tests/opentelemetry-docker-tests/tests and https://github.com/signalfx/splunk-otel-python/tree/main/tests/integration, which require Docker.
Additional context
I have a working prototype here.
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 reading the prototype PR linked in the issue, then compare it with tests/opentelemetry-docker-tests/tests and tests/integration. Define how scenarios specify their inputs and where telemetry outputs are collected; done means an OpenTelemetry scenario can run without Docker and expose its telemetry in one place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- observability-sre, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100