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

​How OneAgent select endpoint?



When we discuss the how to deploy multiple Security Gateway, almost all customers asked us how OneAgent connects Security Gateway and SaaS tenant. We have faced this question many times. So, we would like to understand correctly that.

We suppose that OneAgent and SecurityGateway work as follows. Could you tell me whether it is correct?

  1. The installer of Security Gateway includes the endpoint(tenant URL). So, Security Gateway can connect SaaS tenant without configuration.
  2. Security Gateway sends load status of itself to the SaaS tenant.
  3. The list of endpoints is maintained by SaaS tenant. When a new Security Gateway is installed to the environment, the Security Gateway add to the endpoint list.
  4. When SaaS tenant gets the load status of Security Gateway, the priority of the endpoint list is set based on the load status. Lower load Security Gateway is the higher priority. And the SaaS tenant is the lowest.
  5. The installer of OneAgent needs to be downloaded from SaaS tenant and includes the endpoint list. And the OneAgent connect to the highest priority endpoint after installation.
  6. OneAgent get the endpoint list from SaaS tenant and reconnect to the highest priority endpoint on the new endpoint list every 5 minutes.

Noah Kobayashi



Hi Noah,

1. Yes this is included

2. There is load status for resources of the SGW presented in dynatrace

3. I assume this is if you add/remove nodes in a cluster. The SGW is aware of new nodes remvoed/added. For SaaS dynatrace is already doing this for you so no need to worry about nodes. You can configure SGW for multiple environments, however.

4. No all the nodes are treated equally, same for SGWs in that respect. There is no "load balancing" feature if there is >1SGW available for the OneAgent to talk back to.

Points 5 and 6 I think are addressed in point 4. Since we are sending back to the DNS dynatrace is managing there is not a requirement for prioritisation.

In short, the OneAgent will treat all SGW's as equal if it can talk with them (if not tries another or cluster direct). The components at the moment are not location aware. You can control this on a network level (blocking comms). In the future, location awareness will come into place and a OneAgent will have a preferred local SGW.

Hope that helps, but please let me know if I have misunderstood the points here.


Featured Posts