open-telemetry / open-telemetry/opentelemetry-python
Implement general mechanism to handle signal-specific environment variables
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
yeah, good catch, I think we have the same problem in Trace, will open a new issue to fix that there too.
Originally posted by @ocelotl in https://github.com/open-telemetry/opentelemetry-python/pull/2968#discussion_r1009726328
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
Review the linked pull-request discussion and inspect how signal-specific environment variables are currently handled, including the Trace signal mentioned in the issue. Identify the affected entry points before defining a general mechanism; done means the behavior is consistently specified for the relevant signals and its scope is agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100