Showing results for 
Show  only  | Search instead for 
Did you mean: 

Public Synthetic requirements for Managed




In a Managed environment, do we need to set up a Cluster ActiveGate in order to be able to see and select the public (Dynatrace hosted) locations when creating a Synthetic monitor?




DynaMight Pro
DynaMight Pro


The Cluster ActiveGate requires:

  • A publicly available IP address
  • A domain name with a valid SSL certificate, since external communication is only supported in a secure manner using HTTPS (port 443). This domain must be different from the domain of the Dynatrace web UI. You can choose to provide a domain and a SSL certificate on your own or let Dynatrace do this for you. Dynatrace can generate a domain and a valid SSL certificate on your behalf.


Alanata a.s.

DynaMight Pro
DynaMight Pro

Even more important. It's required as endpoint to receive the data from the public locations.
Agentless Real User Monitoringmobile-app monitoring, and synthetic monitors all use the same endpoint to transmit monitoring data to Dynatrace.

You do not need to, but it's advisable to deploy behind a load balancer, especially when you deploying more than one CAG's. See the link ratislav shared.


Kind regards, Frans Stekelenburg                 Certified Dynatrace Associate |, Dynatrace Partner

Hi guys,

I believe that execution command is sent to Mission Control that coordinate the run on public location and the public location is sending the execution outcomes thru the CAG to DTMC. 

Question is if we get timeout on demand execution where can we see the error is it from DTMC --> MC / Public location --> CAG --> DTMC?

Is there a log we can get from somewhere? 



dynatrace certificated professional - dynatrace master partner - Matrix Soft Ware Division - Israel

@Yosi_Neuman  you are right about the flow.

Afaik there is no log on the cluster ag, but if you have any sort of reverse proxy / load balancer, then you can check if the response arrived.

See my post about public endpoints, where you can find the URLs where synthetic monitored send data to managed cluster. Common reasons for not receiving synthetic data include WAF on the reverse proxy or incorrect certificate. 

Certified Dynatrace Master | Alanata a.s., Slovakia, Dynatrace Master Partner

Dynatrace Leader
Dynatrace Leader

Alternatively, chat/ Support can quickly check the response the public location is getting and provide that back to you. 

Synthetic SME and community advocate.

Featured Posts