How does synthetic ActiveGate work and on which port does it upstream the data to the cluster?

[gilles_djimi-ex]

From what I understood, synthetic ActiveGate are used for certain tasks that the Dynatrace bot are unable to performs. And these tasks are running within a private location.

I read from the documetation which port are in use by the different active gate (https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-activegate/configuration/wh... ). However I didn't found any information about the synthetic-enable active gate. So my question is quite simple can anyone tells me:

- How does synthetic activegate works ?

- On which port are they operating ( from themselves to the cluster and from where are they receiving data ) ?

- Does they needs public IP address

Just for information I'am using Dynatrace managed.

[Radoslaw_Szulgo · Accepted solution]

Cluster ActiveGate can run synthetic monitors from a private location. A synthetic-enabled ActiveGate is used exclusively to run synthetic monitors. The clean ActiveGate installation set to Synthetic monitoring will disable all other ActiveGate features, including communication with OneAgents.

Cluster ActiveGate executes Synthetic checks from the browser embedded on the host. Results in form of beacon is transferred to the Cluster on port 443 - or whatever else is configured on the node. It’s actually the address of AG installed at node.

This illustration might help you understand communication flow: https://www.dynatrace.com/support/help/shortlink/managed-deployment-scenarios#scenario-2-pure-dynatr...

Cluster ActiveGate typically listens on port 9999. Executes calls to any synthetic path you have set up. See also other ports here: https://www.dynatrace.com/support/help/shortlink/activegate-network-ports

Hope it helps!

[Radoslaw_Szulgo]

And no, it does not require public IP to execute private monitors.