• Home
  • Technology support
  • Runtimes
  • Java
  • Out-of-memory (OOM) and out-of-threads (OOT) events and alerting

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

  1. In the Dynatrace menu, go to Settings and select Preferences > OneAgent features.
  2. Find and turn on Enable Out-Of-Memory and Out-Of-Thread Detection for Kubernetes and PaaS installations [Opt-In].
  3. 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 event for high GC total collection time:

    • Metric key: builtin:tech.jvm.memory.gc.collectionTime
    • Threshold: > 40%
Related topics
  • Metric events for alerting

    Learn about metric events in Dynatrace

  • Static thresholds

    Learn about the fixed thresholds used by Dynatrace to determine when a detected slowdown or error-rate increase justifies the generation of a new problem event.