What are the external IPs that the Publicly available IP address of the cluster active gate need to talk to?

[matthew_k]

Hello, what are the external IPs that the Publicly available
IP address of the cluster active gate need to talk to? Just confirming, this
will be port 9999, correct?

[sia_h]

Hi Matt,

Yes, port 9999 is indeed required for outbound. What IPs you should allow depends entirely on what you want to allow. If you're going to use Synthetic, then you should allow the IPs of the Synthetic nodes that you're going to use to communicate with the Cluster ActiveGate. If you're using Agentless monitoring on a publicly available web application - then I assume all IPs should be able to send traffic to the Cluster ActiveGate.

Sia

[matthew_k]

Thank you Sia, if we want the old Dynatrace Synthetic (Gomezplatform) and the new OneAgent synthetics, are they the same? If yes, we would need to find the Gomez IP?

[sia_h]

From my understanding, Classic Synthetic nodes are not used in Dynatrace Managed and will not make use of the Cluster ActiveGate.

[jalpeshs]

Hi Matt,

We have Dynatarce Managed and entire setup and users are in same Environment so why do we need Public IP Address ?

Thanks & Regards,

Jalpesh

[skrystosik · Accepted solution]

Public endpoint is needed when you are using agentless rum monitoring or mobile rum monitoring (in aproaches where RUM data are sent directly to dynatrace). In such option you don't need to expose whole DT cluster, you can do it only with ActiveGate.

Be aware that if, for mobile applications you have instrumented API web server, you can change application settings for sending beacons there (the same like it was in Appmon). But when you have mobile app monitored without backend it's not possible.

Sebastian