yc-360 Script Arguments and Configuration Options

This section describes the full list of arguments supported by the yc-360 script. These arguments can be passed via the command line or a YAML configuration file.

Argument	Description
a	Specifies the name of the application instance, used for tagging logs and incidents in the yCrash UI.
appLogs	Defines paths to application log files; each must include $AppName to associate logs with the right app in the report.
appLogLineCount	Limits the number of recent lines captured from each log file listed under appLogs.
appRuntime	This is a new argument that detects the runtime as .NET. This argument only to be used for .NET capturing. In the case Java, this is NOT required.
c	Path to a YAML file containing all script settings; the preferred method for configuring multiple arguments.
caCertPath	Path to a custom CA certificate file; used to verify SSL when connecting to yCrash server with self-signed certs.
captureCmd	Executes a custom script per resolved PID to capture diagnostics instead of default logic.
cmdTimeout	The cmdTimeout argument sets the maximum time the yc-360 script will wait for external tools like jstack to complete before terminating the operation.
d	Determines if captured artifacts should be deleted after uploading to yCrash server (default: true).
dotnetToolPath	This argument is used to locate the .NET command that is used to capture the artifacts from .NET target applications. This argument is only used if `appRuntime` is dotnet.
edScript	Path to a script that collects additional data beyond the default artifacts.
edDataFolder	Directory where the output files from the edScript are stored and collected by the script.
excludeTokens	List of tokens to exclude from m3 monitoring; useful to skip non-essential background processes.
gcCaptureCmd	Custom script to collect GC logs manually instead of using built-in logic.
gcCaptureMode	Command to dynamically determine the GC log path; must return a file path as stdout.
gcPath	Direct path to a GC log file already captured externally, to be uploaded as-is.
gcDuration	This flag basically is used to specify the duration or time in SECONDS while capturing the .NET artifacts. If this flag is skipped, then the .NET runtime will capture the Garbage collection for 30 seconds (default value).
hd	Enables automatic heap dump capture during the script execution.
hdCaptureCmd	Custom script for capturing heap dumps instead of the built-in logic.
hdCaptureMode	Command to locate or generate a heap dump dynamically; must output the file path.
hdPath	Direct path to a heap dump file already captured externally, to be uploaded as-is.
httpClientTimeout	Sets the maximum wait time for each HTTP request to the yCrash server.
j	Path to the JDK or JRE to be used by the script; defaults to JAVA_HOME if not set.
k	API key used to authenticate with yCrash server; required for all uploads.
kubernetes	Enables enrichment with Kubernetes context like pod and namespace metadata.
logFileMaxCount	Sets how many rotated log files to retain before older ones are deleted.
logFileMaxSize	Maximum log file size in bytes before log rotation occurs.
logFilePath	File path where yc-360 script should write internal logs; defaults to console output.
logLevel	Controls verbosity of yc-360 script logs (e.g., info, debug, error).
m3	Turns on micro-metrics mode, where lightweight monitoring runs in the background.
m3Frequency	Defines how often micro-metrics are collected (e.g., every 60 seconds).
minimalTouch	Enables low-overhead data collection by disabling operations that may introduce CPU or performance impact on the target application.
nodejsCaptureMode	Specifies how yc-360 captures diagnostics from a Node.js application. Choose between the yCrash hook for full diagnostics (default) or Node.js built-in signal-based reporting for hook-free capture.
nodejsGCLogPath	Specifies the path to the file containing your Node.js application's GC trace output for diagnostic collection. Required on Windows and optional on Linux/macOS, where yc-360 attempts to discover the output automatically.
nodejsReportSignal	Specifies the OS signal used to trigger a Node.js diagnostic report in Signal Mode. Applies only when nodejsCaptureMode=signal and is supported on Linux and macOS.
nodejsRuntimeDir	Specifies the directory where yc-360 looks for Node.js hook runtime files such as registration and authentication data. Use this option when the hook runtime files are stored outside the default system temp directory.
onlyCapture	Only collects and stores artifacts locally in ZIP format without uploading them.
p	Token or PID used to identify the Java process for artifact collection.
pingHost	Overrides default ping host used to validate outbound network access.
port	Port for running Action API service; set to -1 to disable.
processTokens	Maps specific Java processes to application names for better tag association.
s	URL of the yCrash server where artifacts are sent for analysis.
storagePath	Directory where output files and the final ZIP archive are stored.
tags	Custom tags used to label and filter incidents in the yCrash dashboard.
tdCaptureCmd	Custom script for capturing thread dumps in place of the built-in method.
tdCaptureDuration	Duration over which multiple thread dumps are collected at intervals.
tdCaptureMode	Command to dynamically generate thread dump path; must echo file path.
tdPath	Direct path to a thread dump file already captured externally, to be uploaded as-is.
verifySSL	Enables SSL certificate validation when connecting to yCrash server.
version	Prints the current version of the yc-360 script and exits.