# captureCmd

Executes a custom diagnostic capture command instead of the yc-360 script's default capture logic. When this is set, the yc-360 script resolves the provided process token or PID and executes the specified script once per resolved process ID. The yc-360 script passes the target PID as an environment variable pid to the script

Type: string

Default: ""

How it works internally:

  • The yc-360 script resolves the provided process token (-p) into one or more PIDs.

  • For each PID, it sets an environment variable pid=(value)

  • It then executes the custom script using the system shell (/bin/sh -c)

  • Standard output and error streams from the script are logged by the yc-360 script.

Example (YAML):

options:
  p: buggyapp
  captureCmd: /opt/scripts/diagnostics.sh
1
2
3

Example (CLI):

/yc -p buggyapp -captureCmd "/opt/scripts/diagnostics.sh"
1

In this example, if buggyapp maps to two PIDs (e.g., 1234 and 2345), the yc-360 script will:

  • Set pid=1234 and execute /opt/scripts/diagnostics.sh

  • Then set pid=2345 and repeat the execution.

← cmdTimeout →