Skip to content

Windows: the opentelemetry-instrument wrapper does not preserve parent-child process relationship #3512

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
karolz-ms opened this issue May 16, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@karolz-ms
Copy link

Describe your environment

OS: Windows 11
Python version: 3.12.10
Package version: 1.33.0

What happened?

See repro & expected

Steps to Reproduce

  1. Programmatically start a Python program via opentelemetry-instrument wrapper.
  2. Observe the process hierarchy.

Expected Result

The started program should stay in the process tree, e.g.

launcher program (grandparent)
   |--> opentelemetry-instrument.exe (parent)
              |--> started program (child)

The telemetry wrapper should keep running (forwarding stdin/stdout/stderr and CTRL_C to the started program as necessary).

Actual Result

The started program is not part of the launched program process tree. opentelemetry-instrument.exe process exits immediately after the started program is launched.

Additional context

This behavior breaks development tools like .NET Aspire, which rely on the fact that child processes are part of the same process tree to discover all children and clean them up during shutdown.

Would you like to implement a fix?

None

@karolz-ms karolz-ms added the bug Something isn't working label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant