strong-supervisor
Version:
supervisor and monitor for node.js applications
57 lines (41 loc) • 2.59 kB
Plain Text
usage: %MAIN% [options] [command ...]
Options:
-h,--help Print this message and exit.
-v,--version Print version and exit.
-C,--control <CTL> Control endpoint for process runner (default `%ADDR%`).
Commands:
status Report status of cluster workers, the default.
set-size <N> Set cluster size to N workers.
stop Stop, shutdown all workers and stop controller.
restart Restart, restart all workers.
ls [DEPTH] List application dependencies.
objects-start <ID> Start tracking objects on ID.
objects-stop <ID> Stop tracking objects on ID.
Object metrics are published, see the `--metrics` option to `sl-run`.
cpu-start <ID> [TIMEOUT] Start CPU profiling on ID.
TIMEOUT is the optional watchdog timeout, in milliseconds. In watchdog
mode, the profiler is suspended until an event loop stall is detected;
i.e. when a script is running for too long. Only supported on Linux.
cpu-stop <ID> [NAME] Stop CPU profiling on ID, save as "NAME.cpuprofile".
CPU profiles must be loaded into Chrome Dev Tools. The NAME is optional,
profiles default to being named `node.<PID>.cpuprofile`.
heap-snapshot <ID> [NAME] Snapshot heap objects for ID, save as
"NAME.heapsnapshot".
Heap snapshots must be loaded into Chrome Dev Tools. The NAME is
optional, snapshots default to being named `node.<PID>.heapshapshot`.
patch <ID> <FILE> Apply patch FILE to ID.
env-get [ID] Get the complete environment of the specified
process. If no target is specified the default is 0,
the cluster master process.
env-set <K1=V1...> Set environment variables in master and worker.
Changes are live without process restart.
env-unset <KEYS...> Unset environment variables in master and workers.
Changes are live without process restart.
dbg-start <ID> Enable DevTools Debugger backend in the target
worker.
dbg-stop <ID> Disable DevTools Debugger backend in the target
worker.
dbg-status <ID> Get the status of DevTools Debugger in the target
worker.
Commands specific to a worker ID accept either a process ID or cluster worker
ID, and use an ID of `0` to mean the cluster master.