Is there any way to disable auto restart of Oneagent post server reboot?

[SachinJindal]

Is there any way to disable auto restart of Oneagent post server reboot?

[ChadTurner]

If you turn off monitoring via the Dynatrace UI that should solve your problem 

[SachinJindal]

possible to perform using command line? so the init services which are responsible for start doesnt do anything if we disable.

[Julius_Loman · Accepted solution]

@SachinJindal you can stop oneagent from being started by modifying the systemd unit file (Linux) / configuring the sysv (Linux) or using services (Windows).

What is the use case here you are trying to solve? I'd not recommend disabling the startup of oneagent and prefer the UI or API method which @ChadTurner suggests.

Agent disabled in Dynatrace does not perform any actions except for sending heartbeats to Dynatrace.

[SachinJindal]

just wanted to stop the Dynatrace for quite some days  and it shouldnt startup if Servers are rebooted assuming we dont have DT UI access

[Julius_Loman]

Then only way is to modify the startup of the agent itself. Not a great idea, since you can manage it from Dynatrace UI/API afterwards.
Anyway, I don't recommend shutting down OneAgent unless there are really very good reasons. I recommend to either get access to the UI/API so you can manage it from there. Doing manual startup changes is discouraged in general.

[ChadTurner]

You can also leverage the Services portal (Assuming you have SaaS access) which lives outside your Dynatrace UI to enable/disable the oneagent. 

[richard_guerra]

Hello, Assuming Linux OS -

The doc page is here: Stop/restart OneAgent on Linux but this doesn't answer your specific question directly.

OneAgent is installed as a system service, so you can use systemctl commands to disable or enable, example:

   $ sudo systemctl disable oneagent.service

   $ sudo systemctl enable oneagent.service

You'll need 'root' - with related complications. If you have root, then I'd anticipate you should be familiar with systemctl, hence please consider above advice to disable/enable from cluster side (which admittedly still lets OneAgent initiate at the OS service level).