Answer by Graeme W. ·
Indira,
There'll be a small increase in latency, sure, but it shouldn't be more than a few tens of milliseconds. It's just half the ping time between the data center and the cloud.
Depending on traffic, a Dynatrace Collector can support hundreds of agents.
Just to be completely clear, there's no local Dynatrace Server process in each data center, just a system running a Dynatrace Collector process. I'd advise against referring to that system as the DT Server, because of the possibility of confusion with the system running the Dynatrace Server process in the cloud.
With 20 agents, the requirements for the system running the Dynatrace Collector process will be modest, depending on the traffic volume, but it is best practice to run the Dynatrace Collector process on a dedicated system (or VM),
-- Graeme
Answer by Graeme W. ·
Indira,
You don't need multiple DT Servers. You can put a Dynatrace Collector in each data center and connect them all to a Dynatrace Server in the cloud.
If for some reason you want to keep the data for each data center separate, you can always create separate systems profiles for each data center.
Let us know if you want more details on this configuration.
-- Graeme
Answer by Indira P. ·
We are looking for some hybrid model for the DT in which we have collect and DT Server running in the diff customer datacenter and main DT Server in cloud connect with all our ITSM Tools.
in this i would like to know can the DT Server in customer end can report to main DT Server in cloud?? kindly provide me the clarity on this..
JANUARY 15, 3:00 PM GMT / 10:00 AM ET