Does network zone change require a code module restart?

[pahofmann]

When changing network zones, will code modules get the new configuration on the fly, or is a restart required for the monitored applications?

The Documentation for Network Zones states: Restart OneAgent monitored applications, so that they pick up the new instrumentation.

The Documentation for Remote Configuration Management states: Restarting the injected processes isn't necessary when changing the network zone assignment.

[ChadTurner]

I was under the impression that it was just the Oneagent that needed to be recycled since it contains the data for the communication routes with network Zones. Id love some clarity from Dynatrace. 

[pahofmann]

The code modules connect directly to the ag/cluster though, not to the OneAgent first. 

[bradley_danyo]

You will need a OneAgent restart when changing network zones

https://www.dynatrace.com/support/help/shortlink/network-zones-migration-deploy

[pahofmann]

That is the same documentation I linked above, the second documentation link says something else though, thus the questions 😉

[bradley_danyo]

Hi,

Yes, please see my below comment

Thanks

[bradley_danyo]

You don't need to do any process restart but you will need to restart OneAgent service for changes to take effect.  Generally speaking, it shouldn't be necessary to restart application after starting OneAgent service.

[jegron]

Regarding HostGroup it is apply - from a GUI point of view - to host and process without an application restart. But in documentation it is clearly mentioned that OA service AND all the monitored services restart is needed (https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/oneagent-configura...).

Maybe Dynatrace team could clarify documentation and this GUI Remote Configuration Management message (same for HostGroup and Network Zone) and explain why an application restart could be needed :