It is a Dynatrace Managed with no Cluster ActiveGate, but the Dynatrace Managed has been exposed to public on port 443.
The cluster itself cannot directly handle mobile beacons: https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-managed/installation/managed-deployment-scenarios/#scenario-2-pure-dynatrace-managed-setup
Thanks. It is for the testing of mobile app, so at least for now all users are only from load injection tool, not around the globe.
So, in this case, can I use Environment AG instead of Cluster AG? I am wondering have you try it before?
In this case, I would try to change the value of DTX Beacon URL to be https://<Environment_AG_URL>:9999 after enable the firewall to allow 9999.
An ActiveGate that has a beaconforwarder running needs to be installed (I'm not that familiar with the different AG flavours, but based on my knowlege a cluster AG is needed), then the configuration to use should be displayed correctly - please use the displayed configuration and don't try to stitch something together.