[BUG] salt.utils.tracing eagerly imports OpenTelemetry when tracing is disabled
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
salt.utils.tracing unconditionally imports the entire OpenTelemetry SDK at module load, even when tracing.enabled is False (the default). Because salt.utils.tracing is imported by every daemon entry point (salt.master, salt.minion, salt.channel.client, salt.channel.server, salt.utils.event, salt.netapi.rest_cherrypy.app, salt.utils.reactor), every Python process in the salt fleet pays the OTel import cost, regardless of whether tracing is used.
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 salt.utils.tracing module and checking how it is imported by salt.master, salt.minion, salt.channel.client, salt.channel.server, salt.utils.event, salt.netapi.rest_cherrypy.app, and salt.utils.reactor. Done means the OpenTelemetry SDK is not imported when tracing.enabled is False, while tracing remains available when enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100