yCrash Server Configurations

The yc-360 script configuration alone is sufficient to run M3. However, additional server-level settings are available to provide greater flexibility and control based on your operational needs. These optional server configurations allow you to fine-tune data handling, alerting behavior, retention policies, and execution workflows to better align with your environment and governance requirements. The available server-level settings are listed below.

Additional Settings:

Argument	Description	Default
observationPeriod	Defines how long M3 observes system metrics before deciding whether an incident should be triggered. For more details, refer here	6mins
coolingPeriod	Sets a waiting period after an incident is triggered to prevent the same issue from generating repeated alerts within a short time. For more details, refer here	24hrs
monitorGC	Controls whether M3 monitors Garbage Collection (GC) behavior and detects GC-related anomalies. For more details, refer here	false
monitorThread	Controls whether M3 monitors thread activity and detects thread-related performance issues. For more details, refer here	false
Reduce False Positive Incidents	To reduce false positive incidents, noise and avoid unnecessary incident generation, M3 provides configuration options to discard non-actionable or low-severity events. 1. Log Error Discard Settings 2. Discard Settings	-
Notifications & Integrations	Get notified proactively by integrating M3 with supported notification and alerting tools. For more details, refer here.	-