pranshuparmar / witrCLI + TUI
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

// witr
// Why is this running?

Something ownsport 8080.

witr traces any process, port, container, or file back to what started it. One question, answered as a chain instead of a PID you still have to look up.

> process > port > container > file
traceillustrative

$ witr port 8080

node server.js, pid 4821listener
 │
npm run dev, pid 4790parent
 │
docker-compose up, pid 3312container
 │
systemd unit dev-stack.serviceorigin

Chain content is illustrative. witr traces a process, port, container, or file back to what started it.

The answer is a chain

Knowing the pid is where the question starts. witr keeps walking until it reaches the thing a person actually configured.

Four entry points

Process, port, container, or file. Whichever end of the mystery you are holding, the trace runs the same direction.

CLI and TUI

One shape for scripts and log paste, another for the moment you are still poking at the machine.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
pranshuparmar/witrDesign study by Goose. Not affiliated with the project.