minimalTouch

The minimalTouch argument is designed to minimize the runtime impact of the yc-360 script on the target JVM or application. When enabled, yc-360 avoids collecting artifacts that are known to introduce CPU overhead or cause observable performance spikes, making it suitable for highly sensitive or production-critical environments.

This mode is especially useful when the application is already under high load and diagnostic data must be collected with minimal interference.

What Happens When minimalTouch Is Enabled?

When minimalTouch=true, yc-360 disables or restricts the following operations:

GC log capture via jstat

When GC logging is not already enabled in the target application, the yc-360 script relies on the jstat tool for continuous GC sampling. In minimalTouch mode, this sampling is skipped to avoid periodic CPU spikes caused by JVM attach/detach operations.

Heap substitute data collection

The heap substitute data is skipped, as it can trigger heap walking and introduce noticeable CPU overhead.

Heap dump capture

Full heap dump generation is disabled, even if the -hd (heap dump) argument is explicitly provided.

Note:

If both -hd and -minimalTouch are specified, minimalTouch takes precedence, and heap dump capture will be skipped.

Example (YAML):

options:
  minimalTouch: true

Example (CLI):

./yc -minimalTouch