yc-360 Script Execution Modes

The yc-360 script is a lightweight utility designed to be executed on all production servers that require monitoring. It captures a comprehensive set of troubleshooting artifacts—such as GC logs, thread dumps, netstat, vmstat, iostat, and more—and transmits them to the yCrash server for analysis.

The yc-360 script supports multiple execution modes tailored for various monitoring needs. Choose the mode that best fits your needs to learn how to configure and execute the script.

1. On-demand Mode

In this mode, the script is manually invoked with the target application’s process ID (PID) or unique process token. It captures all diagnostic artifacts and automatically uploads them to the yCrash server for immediate analysis.

Learn how to run the yc-360 script in On-demand Mode.

2. Only-capture Mode

Similar to On-demand Mode, this mode captures the same artifacts—but saves them locally as a ZIP file instead of uploading them. The archive can later be manually uploaded to the yCrash server for analysis.

Learn how to run the yc-360 script in Only-capture Mode.

3. Micro-metrics Monitoring (M3) Mode

In this mode, the script runs as a background daemon, periodically sending lightweight system metrics (every 3 minutes, by default) to the yCrash server. It proactively predicts application failures—such as OutOfMemoryErrors—and automatically triggers full artifact capture upon anomaly detection, enabling root cause analysis.

Learn how to run the yc-360 script in Micro-metrics Monitoring (M3) Mode.

4. API Mode

The script runs continuously and exposes an HTTP-based API. This allows external monitoring tools (e.g., New Relic, AppDynamics, Dynatrace) to programmatically trigger the yc-360 script to capture 360-degree artifacts based on observed issues.

Learn how to run the yc-360 script in API Mode.