By default, OneAgent runs in Full-Stack monitoring mode, giving you complete visibility across hosts, processes, and services. If you prefer a lighter approach, you can switch to one of the two alternative modes that focus on essential infrastructure metrics:
You can define a default monitoring mode before installing OneAgent. This will change the default Full-Stack monitoring mode on the OneAgent deployment page (for Linux, Windows, and AIX operating systems) and in the
Discovery & Coverage app (when deploying OneAgent from the Install OneAgent page).
To define a default monitoring mode
The selected value will be set as a default value for the chosen OneAgent deployment mode.
You can turn on Infrastructure monitoring mode at the host level, either during or after OneAgent installation.
To turn on Infrastructure monitoring mode during OneAgent installation, use the --set-monitoring-mode=infra-only parameter.
For more information, see the OneAgent installation documentation that's specific to your environment.
To turn on Infrastructure monitoring mode after OneAgent installation, use one of these options:
Hosts Classic and open a host overview page.--set-monitoring-mode=infra-only parameter.builtin:host.monitoring as the schemaId and create your configuration object using POST an object.Process injection provides you with additional data for Infrastructure Observability. Process injection is enabled by default.
If you run your OneAgent as a container with Infrastructure monitoring mode enabled, process injection will not be performed.
Infrastructure monitoring mode enables you to monitor any infrastructure component and backing service written in Java. You can monitor backing services supported by default (for example, Kafka or ActiveMQ), and you can also build your own custom JMX and PMI extensions for infrastructure components and use them in Infrastructure monitoring mode.
Additionally, with process injection, Infrastructure monitoring mode provides runtime metrics for:
We don't recommend turning off auto-injection, but if you're required to do so due to strict security requirements, you can choose among various options. Turning off auto-injection also prevents Dynatrace from discovering vulnerabilities or live debugging in your environment, even if you enable Application Security or Live Debugger. You can turn off automatic injection at the host or environment level.
Hosts Classic and open a host overview page.Use the OneAgent command line interface to set the --set-auto-injection-enabled=false parameter.
If you use oneagentctl to turn off automatic injection, you won't be able to control auto-injection in Infrastructure monitoring mode using the Dynatrace web UI at Settings > Monitoring > Monitored technologies or OneAgent monitoring configuration API.
You can turn off process injection for particular process groups using custom process monitoring rules.
Custom process monitoring rules give you fine-grained control over which processes OneAgent injects into, with an approach that scales easily within large environments. You don’t need to adjust your system configuration, and a few rules can cover thousands of processes.
For more information, see Process deep monitoring.
You can disable the collection on JMX/PMI and runtime metrics, which will result in disabling auto-injection in Infrastructure monitoring mode.
You can also turn off selected extensions collecting the metrics at the environment level.
Go to Settings > Monitoring > Monitored technologies.
When you turn off auto-injection, you can find such hosts using the Auto-injection filter on the Deployment Status page or OneAgent on a host - GET a list of hosts with OneAgent details.
oneagentctl.Run the OneAgent on a host - GET a list of hosts with OneAgent details call with the autoInjection parameter set to DISABLED_MANUAL. The returned payload contains the list of OneAgents with auto-injection disabled after OneAgent installation via either the Dynatrace web UI or oneagentctl.
You can turn on Discovery mode at the host level, either during or after OneAgent installation.
To turn on Discovery mode during OneAgent installation, use the --set-monitoring-mode=discovery parameter.
For more information, see the OneAgent installation documentation that's specific to your environment.
To turn on Discovery mode after OneAgent installation, use one of these options:
Hosts Classic and open a host overview page.--set-monitoring-mode=discovery parameter.For Application Security and Live Debugger to work in Discovery mode, code-module injection is required. Code-module injection is disabled by default.
After turning on Discovery mode, you can turn on the code-module injection for a single host.
For details on how Application Security works in Discovery mode, see Application Security: Discovery mode.