Dynatrace provides ready-made alerts for common Kubernetes issues across clusters, nodes, namespaces, workloads, and persistent volume claims. Each alert is either a health alert, which triggers a Problem investigation, or a warning signal, which flags a potential issue without opening a Problem. For details on this severity model, see Health alerts and warning signals.
This page lists every ready-made Kubernetes alert together with its severity, recommended defaults, de-alert timing, and detection logic.
To review or adjust your Kubernetes alert configuration
You can also open alert configuration directly from a cluster or namespace in
Kubernetes. For a full walkthrough of all configuration levels (environment, cluster, namespace), see Alert on common Kubernetes misconfigurations and detect anomalies with Kubernetes metrics.
With the latest Dynatrace upgrade, Kubernetes alerts that previously raised a problem have been reclassified as warning signals. This reclassification is automatic and applies to all environments - it doesn't require any configuration change.
Independently, recommended defaults are available for all environments. They define which alerts are enabled and their detection thresholds, but they are not applied automatically — your current configuration isn't affected until you explicitly apply them under
Settings > Analyze and alert > Alerts > Kubernetes.
Each alert has two independent dimensions:
In the alert reference tables below:
The following alerts are currently disabled and become enabled with Critical severity when you apply the recommended defaults. Review them before applying, since they'll start opening problems.
| Alert | Trigger condition |
|---|---|
Detect stuck deployments | Stops progressing ≥ 3 min; within 5 min |
Detect workloads without ready pods | No ready pods ≥ 10 min; within 15 min |
Detect pod backoff events | Event-based |
Detect pod eviction events | Event-based |
| Alert | Problem type | Enabled (recommended) | Detection threshold (recommended) | Severity | De-alerts after | Calculation |
|---|---|---|---|---|---|---|
Availability | Yes | Not ready ≥10 min; within 15 min | Health alert | 10 minutes | Cluster readyz metric | |
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Node CPU requests / Node CPU allocatable | |
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Node memory requests / Node memory allocatable | |
Resource | No | >90% pods / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of ready pods / Sum of allocatable pods | |
Availability | Yes ¹ | Not available ≥20 min; within 30 min | Warning signal ¹ ² | 10 minutes | Dynatrace API monitoring availability |
Detect monitoring issues has no associated metric or DQL expression — it monitors whether Dynatrace's own API-based monitoring of the cluster is available, not a cluster condition.
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Alert | Problem type | Enabled (recommended) | Detection threshold (recommended) | Severity | De-alerts after | Calculation |
|---|---|---|---|---|---|---|
Availability | Yes ¹ | Not ready ≥10 min; within 20 min | Warning signal ¹ ² | 10 minutes | Node condition metric filtered by 'not ready' | |
Error | Yes ¹ | Problematic ≥10 min; within 20 min | Warning signal ¹ ² | 10 minutes | Nodes condition metric | |
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of node CPU requests / Sum of node CPU allocatable | |
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of node memory requests / Sum of node memory allocatable | |
Resource | No | >90% pods / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of running pods on node / Node pod limit |
Detect problematic node conditions triggers on any of the following: ContainerRuntimeProblem, ContainerRuntimeUnhealthy, CorruptDockerOverlay2, DiskPressure, FilesystemCorruptionProblem, FrequentContainerdRestart, FrequentDockerRestart, FrequentGcfsSnapshotterRestart, FrequentGcfsdRestart, FrequentKubeletRestart, FrequentUnregisterNetDevice, GcfsSnapshotterMissingLayer, GcfsSnapshotterUnhealthy, GcfsdUnhealthy, KernelDeadlock, KubeletProblem, KubeletUnhealthy, MemoryPressure, NetworkUnavailable, OutOfDisk, PIDPressure, ReadonlyFilesystem.
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Alert | Problem type | Enabled (recommended) | Detection threshold (recommended) | Severity | De-alerts after | Calculation |
|---|---|---|---|---|---|---|
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of resource quota CPU used / Sum of resource quota CPU requests | |
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of resource quota CPU used / Sum of resource quota CPU limits | |
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of resource quota memory used / Sum of resource quota memory requests | |
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of resource quota memory used / Sum of resource quota memory limits | |
Resource | No | >90% / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of resource quota pods used / Sum of resource quota pods limit |
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Alert | Problem type | Enabled (recommended) | Detection threshold (recommended) | Severity | De-alerts after | Calculation |
|---|---|---|---|---|---|---|
Error | Yes ¹ | ≥1 restart per 3 min; within 5 min | Warning signal ¹ ² | 15 minutes | Container restarts metric | |
Error | Yes ¹ | Stops progressing ≥3 min; within 5 min | Health alert ¹ | 10 minutes | Workload condition metric filtered by 'not progressing' | |
Resource | Yes ¹ | ≥1 pod stuck ≥10 min; within 15 min | Warning signal ¹ ² | 10 minutes | Pods metric filtered by phase 'Pending' | |
Resource | Yes ¹ | Termination stopped ≥10 min; within 15 min | Warning signal ¹ ² | 10 minutes | Pods metric filtered by status 'Terminating' | |
Error | Yes ¹ | No ready pods ≥10 min; within 15 min | Health alert ¹ | 10 minutes | Sum of non-failed pods − Sum of non-failed, non-ready pods | |
Error | No | >30% non-ready; within 60 min | Warning signal ² | 10 minutes | Sum of non-failed pods − Sum of non-failed, ready pods | |
Resource | No | >90% / ≥10 min; within 15 min | Warning signal ² | 10 minutes | Sum of workload working set memory / Sum of workload memory limits | |
Resource | No | >90% / ≥10 min; within 15 min | Warning signal ² | 10 minutes | Sum of workload working set memory / Sum of workload memory limits | |
Resource | No | >100% throttled / ≥20 min; within 30 min | Warning signal ² | 10 minutes | Sum of workload CPU throttled / Sum of workload CPU limits | |
Error | Yes ¹ | Event-based | Warning signal ¹ ² | 15 minutes | Out-of-memory kills metric | |
Error | Yes ¹ | Event-based | Warning signal ¹ ² | 60 minutes | Event metric filtered by reason and workload kind | |
Error | Yes ¹ | Event-based | Health alert ¹ | 15 minutes | Event metric filtered by reason | |
Error | Yes ¹ | Event-based | Health alert ¹ | 60 minutes | Event metric filtered by reason | |
Error | Yes ¹ | Event-based | Warning signal ¹ ² | 60 minutes | Event metric filtered by reason |
BackoffLimitExceeded, DeadlineExceeded, or PodFailurePolicy, for Jobs and CronJobs only.BackOff — check for pods with status ImagePullBackOff or CrashLoopBackOff.Evicted.Preempted or Preempting.| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Alert | Problem type | Enabled (recommended) | Detection threshold (recommended) | Severity | De-alerts after | Calculation |
|---|---|---|---|---|---|---|
Resource | No | ≤100 MiB remaining / ≥3 min; within 5 min | Warning signal ² | 10 minutes | Kubelet volume stats available bytes metric | |
Resource | Yes ¹ | <3% available / ≥3 min; within 5 min | Warning signal ¹ ² | 10 minutes | Volume stats available bytes / Volume stats capacity bytes |
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
| Type | Expression |
|---|---|
Metric expression |
|
DQL |
|
Kubernetes