Out-of-memory (OOM) and out-of-threads (OOT) events and alerting
To set up out-of-memory (OOM) and out-of-threads (OOT) events for standalone/PaaS scenarios and cloud-native Full-Stack injections, follow the instructions below.
Enable the OneAgent feature
Create metric events
Enable the OneAgent feature
To enable out-of-memory (OOM) and out-of-threads (OOT) detection
- In the Dynatrace menu, go to Settings and select Preferences > OneAgent features.
- Find and turn on Enable Out-Of-Memory and Out-Of-Thread Detection for Kubernetes and PaaS installations.
- Select Save changes.
Create metric events
After you enable detection, create two metric events that will alert on high GC activity.
-
In the Dynatrace menu, go to Settings and select Anomaly detection > Metric events.
-
Select Add metric event.
-
Define the following two events.
We recommend setting alerts for long garbage collection times if either more than 40% of a minute (24 s) is spent in garbage collection or suspension is higher than 25% in 3 of 5 one-minute observation intervals.Metric event Metric key Threshold Violating samples Sliding window Dealerting samples High GC suspension time
builtin:tech.jvm.memory.gc.suspensionTime
25 %
3
5
5
High GC total collection time
builtin:tech.jvm.memory.gc.collectionTime
24 s
3
5
5
-
Select Save changes.