In case you don't want to use OneAgent inside a particular Java (or other) process, you can easily disable Dynatrace monitoring for individual hosts, process groups, or applications:
Hot cloning is generally not supported by OneAgent due to host ID generation requirements. When hot cloning a host with OneAgent installed, follow these steps to ensure proper functionality:
When you use the set parameters, you need to restart OneAgent service to apply changes. You can use the --restart-service parameter with the command that triggers the restart automatically. In some cases you'll also need to restart monitored applications. You can also use the restart parameter on its own, without other parameters. See an example command below.
./oneagentctl --set-proxy=my-proxy.com --restart-service
For more information, see OneAgent configuration via command-line interface.
If you use configuration management tools like Puppet or Ansible, you can alternatively stop the OneAgent service using the systemctl stop oneagent command.
If you stop OneAgent service, monitoring will be disabled until the service is restarted.
To start OneAgent again, use the systemctl start oneagent command.
Learn more about how Dynatrace interacts with your OS.