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 for alerting
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 [Opt-In].
- Select Save changes.
Create metric events for alerting
After you enable detection, create two metric events for alerting in case of high GC activity.
Use the following values:
-
Metric event for high GC suspension time:
- Metric key:
builtin:tech.jvm.memory.gc.suspensionTime
- Threshold: > 25%
- Metric key:
-
Metric event for high GC total collection time:
- Metric key:
builtin:tech.jvm.memory.gc.collectionTime
- Threshold: > 40%
- Metric key: