open-telemetry / open-telemetry/opentelemetry-python
Clarify support for forking process models
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
https://opentelemetry-python.readthedocs.io/en/latest/examples/fork-process-model/README.html indicates that BatchSpanProcessor does not support forking process models, including those used by Gunicorn and uWSGI. However those docs (https://github.com/open-telemetry/opentelemetry-python/pull/1609) pre-date other changes which appear to have added support for forking process models, including:
- https://github.com/open-telemetry/opentelemetry-python/pull/2242, and
- https://github.com/open-telemetry/opentelemetry-python/pull/2277
which seem specifically targetted at resolving the described issues.
What is the current expected state of support for the various forking models?
Either way, updating the docs to clarify the actual situation would be appreciated.
Possibly related issues:
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 fork-process-model README and review pull requests 1609, 2242, and 2277 to establish what support was intended for Gunicorn, uWSGI, and other forking models. Check the related issues 2767, 2837, 675, and 676 for unresolved cases, then update the documentation to state the current expected support clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100