topic Re: Configure New Communication Endpoint for ActiveGate in Open Q&A

Configure New Communication Endpoint for ActiveGate

hqlee — Thu, 20 Feb 2025 08:03:50 GMT

Hi all,

In my environment, OneAgents are trying to connect using the ActiveGate's domain name and private IP, which are the automatically detected endpoints. However, since the hosts and ActiveGates are in different VPCs, they cannot reach the ActiveGate's private IP or domain name—they can only communicate via its public IP.

Is there a way to configure the ActiveGate to accept OneAgent traffic through its public IP by adding it as a communication endpoint?

Re: Configure New Communication Endpoint for ActiveGate

Babar_Qayyum — Thu, 20 Feb 2025 06:09:37 GMT

Hello @hqlee

In this scenario, the OneAgent must be regarded as an external entity that connects to the Cluster ActiveGates via the public IP, facilitating integration with the current IT environment. For further information regarding the Pure Dynatrace Managed configuration and its integration with the existing IT landscape, please refer to the following links. Additionally, instructions for configuring OneAgent communication settings are provided.

https://docs.dynatrace.com/managed/shortlink/managed-deployment-scenarios#scenario-3-integration-with-existing-it-landscape

https://docs.dynatrace.com/managed/shortlink/oneagentctl#oneagent-communication

Regards,

Babar

Re: Configure New Communication Endpoint for ActiveGate

hqlee — Mon, 24 Feb 2025 08:56:13 GMT

Hi @Babar_Qayyum ,

Thanks for the information. I got it working by applying dnsEntryPoint as shown in the documentation below.

https://docs.dynatrace.com/docs/shortlink/oneagent-reverse-proxy#configure-after-installation