Hi @VH
In full-stack mode, OneAgent is designed to run with a very small footprint and to stay below well-defined resource limits so it won’t interfere with the host’s own workloads.
Memory usage
On a Linux host, the combined memory consumption of all OneAgent modules (process monitoring, network, logs, deep monitoring, etc.) typically stays in the range of a few hundreds of megabytes at most. The exact value depends on the number of monitored processes, technologies, and traffic volume, but it remains stable and predictable.
CPU usage
CPU consumption usually stays below 3–5% even under load. OneAgent continuously adapts its sampling and analysis work based on host conditions, so it avoids competing with application processes.
Built-in protection mechanisms
OneAgent includes automatic safeguards: if the host’s CPU becomes constrained or if the agent detects that its own activity could impact the server, it will throttle or deactivate certain analysis components. This ensures that monitored workloads always remain prioritized and that Dynatrace does not degrade the machine’s performance.
