This alert detects high JVM CPU utilization, indicating that the application may be under heavy load or experiencing inefficiencies that impact performance. Customization Guidance: Threshold: The default threshold is set at 80% CPU utilization. Adjust this based on typical usage patterns and acceptable performance limits for your application. Monitoring Period: A monitoring period of 10 minutes helps identify sustained high CPU usage. Adjust based on the nature of your application’s workload. Notification Frequency: Balance between receiving timely alerts and avoiding alert fatigue. Adjust according to the criticality of CPU monitoring for your operations. Action: When this alert is triggered, review active processes and application load. Consider optimizing resource-heavy code or scaling resources if needed.

This alert detects high heap memory usage, which could lead to potential OutOfMemoryError events and application instability. Customization Guidance: Threshold: The default is set at 80% of max heap memory used. Adjust this according to your application’s memory behavior and headroom requirements. Monitoring Period: A 10-minute window helps catch sustained high usage. Adjust for shorter or longer observation periods as needed. Notification Frequency: Adjust based on the importance of memory stability to avoid excessive notifications. Action: Investigate which processes are using memory heavily and consider tuning the JVM’s memory allocation or code optimization.

This alert detects non high heap memory usage, which could lead to potential OutOfMemoryError events and application instability. Customization Guidance: Threshold: The default is set at 80% of max non heap memory used. Adjust this according to your application’s memory behavior and headroom requirements. Monitoring Period: A 10-minute window helps catch sustained high usage. Adjust for shorter or longer observation periods as needed. Notification Frequency: Adjust based on the importance of memory stability to avoid excessive notifications. Action: Investigate which processes are using memory heavily and consider tuning the JVM’s memory allocation or code optimization.

This alert identifies when the number of executing threads in the JVM exceeds an expected threshold, which could indicate thread contention or resource saturation. Customization Guidance: Threshold: The default is set at 20000 runnable threads. Modify based on your application’s normal thread count. Monitoring Period: Monitor over a 10-minute period to catch prolonged thread increases. Thread States: Customize to monitor different thread states (e.g., blocked, waiting) if needed. Notification Frequency: Set notification intervals to ensure prompt alerting without overwhelming teams. Action: Investigate thread dumps to find bottlenecks or excessive thread creation.

This alert tracks the rate of class loading and unloading, which can indicate potential classloader issues if unusually high. Customization Guidance: Threshold: Default is 500 classes loaded/unloaded in 10 minutes. Adjust based on typical classloading activity. Monitoring Period: A 10-minute window helps identify rapid class loading/unloading. Notification Frequency: Balance timely alerts with alert fatigue by setting appropriate notification thresholds. Action: Investigate code changes or classloader configurations that might be causing high class loading/unloading rates.

This alert tracks the rate of class Unloading, which can indicate potential classloader issues if unusually high. Customization Guidance: Threshold: Default is 100 classes unloaded in 10 minutes. Adjust based on typical classloading activity. Monitoring Period: A 10-minute window helps identify rapid class loading/unloading. Notification Frequency: Balance timely alerts with alert fatigue by setting appropriate notification thresholds. Action: Investigate code changes or classloader configurations that might be causing high class unloading rates.