open-telemetry / open-telemetry/opentelemetry-python-contrib
Make protobuf compatible with 3 and 4 for opentelemetry-exporter-prometheus-remote-write
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 1.1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 16
Description
Based on the latest release of open-telemetry for python it is possible to generate proto to be compatible with 3 and 4.
https://github.com/open-telemetry/opentelemetry-python/releases/tag/v1.15.0
I would really like to have the same compatibility for contrib packages.
https://github.com/open-telemetry/opentelemetry-python/pull/3070
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 with the opentelemetry-exporter-prometheus-remote-write package and compare its protobuf generation setup with the linked opentelemetry-python release and pull request. Identify the generated-protobuf compatibility change required there, then verify that the exporter works with both protobuf 3 and 4.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100