process_runtime
Inspect JVM heap and GC, Node.js event loop, and per-process CPU and memory metrics to find the cause of pod memory growth or CPU saturation.
Instructions
Reports runtime metrics of the processes (Dynatrace PROCESS_GROUP_INSTANCE) running in a pod, a workload or a process group, or of one process. The technology is detected per process: JVM processes get heap usage, heap max, memory pools, GC suspension and GC time, and thread count; Node.js processes get V8 heap used / total, RSS, event loop utilization and latency; every process gets CPU usage and working set memory. Each metric is a summarised series (min / avg / max with its time / last / trend, and a table over time for the main ones).
Pass exactly one of pod, workload, process_group or process (id or name). Use it when pod_resources shows memory growth or CPU saturation and you need to know whether heap, GC or the event loop is the cause. Follow up with get_process for callers, callees and hosted services.
This tool runs through the Dynatrace Bridge browser extension in the user's logged-in browser. If it fails, report the error to the user; do not try to open browser tabs or use browser automation instead.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pod | No | The pod whose processes to analyse, as an entity id (CLOUD_APPLICATION_INSTANCE-1234567890ABCDEF) or a name. A name that matches several entities returns the candidates instead of guessing. | |
| process | No | A single process, as an entity id (PROCESS_GROUP_INSTANCE-1234567890ABCDEF) or a name. A name that matches several entities returns the candidates instead of guessing. | |
| time_to | No | Absolute end time, ISO 8601; without a zone it is read as UTC. Without time_from, the window starts minutes_lookback before this. Must not be in the future. | |
| workload | No | The workload whose processes to analyse, as an entity id (CLOUD_APPLICATION-1234567890ABCDEF) or a name. A name that matches several entities returns the candidates instead of guessing. | |
| time_from | No | Absolute start time, ISO 8601 (e.g. '2026-09-23T10:28:00Z'). A timestamp without a zone (Z or ±hh:mm) is read as UTC. Without time_to, the window runs from here to now. Must not be in the future. | |
| max_series | No | Maximum series summarised per metric, ranked by average. Default 10, at most 50. | |
| environment | No | Which Dynatrace environment to query, as named in the Dynatrace Bridge extension popup. Omit it for the default, the first environment configured there. The names are not listed here because the extension had not connected yet when this description was built; `dynatrace_bridge_status` lists them. | |
| process_group | No | A process group, as an entity id (PROCESS_GROUP-1234567890ABCDEF) or a name. A name that matches several entities returns the candidates instead of guessing. | |
| minutes_lookback | No | Window length in minutes. Default 120. With neither time_from nor time_to it means the last N minutes up to now; with only time_to it means the N minutes ending at time_to; ignored when time_from is given. The response header always shows the resolved absolute UTC window. |