Supported connectivity schemes for ActiveGates

Based on your specific use case and requirements, the possible connectivity schemes for ActiveGates, OneAgents, and Dynatrace Server are depicted below.

ActiveGate connectivity scheme

ActiveGates are sorted with the following hierarchy:

  • Level 1—Environment ActiveGates
  • Level 2—Cluster ActiveGates
  • Level 3—Embedded ActiveGates

ActiveGates can only send data to higher hierarchy levels. It is impossible to send data to the same or lower level of the hierarchy.

The connectivity depends on the network zones configuration. A network zone instructs ActiveGates and OneAgents to communicate with ActiveGates from the same zone. If it is not possible, ActiveGate or OneAgent tries to connect to another ActiveGate. To organize these fallback connections, all ActiveGates are sorted to the priority groups.

Environment ActiveGate connectivity

  • Group 1—ActiveGates from the same network zone.
  • Group 2—ActiveGates from the alternative network zone.
  • Group 3—ActiveGates from the default network zone.
  • Group 4—All other ActiveGates.

In every group, ActiveGates are further prioritized depending on the type:

  • Index 1—Embedded ActiveGates
  • Index 2—Cluster ActiveGates

ActiveGate priority

The preferable ActiveGate is the one with lowest possible index. For load balancing, an Environment ActiveGate rotates through all available endpoints of ActiveGates with the lowest possible index.

If the preferable ActiveGate is not available, Environment ActiveGate tries the next higher index, until a connection is established. In that case, Environment ActiveGate will regularly check in the background for availability of ActiveGates with a lower index.

Unconfigured ActiveGates

Environment ActiveGates with no network zone configured (that includes all ActiveGates from the Default network zone) work as if the network zone doesn't exist. Such ActiveGates try to connect to the first available ActiveGate based on the following priority:

  • Index 1—Embedded ActiveGates
  • Index 2—Cluster ActiveGates

For load balancing, after a few minutes they try to switch to the next responding ActiveGate of the lowest possible index.

OneAgent connectivity

  • Group 1—ActiveGates from the same network zone.
  • Group 2—ActiveGates from the alternative network zone.
  • Group 3—ActiveGates from the default network zone.
  • Group 4—All other ActiveGates.

In every group, ActiveGates are further prioritized depending on the type:

  • Index 1—Environment ActiveGates
  • Index 2—Cluster ActiveGates
  • Index 3—Embedded ActiveGates

ActiveGate priority

OneAgents are load-balanced to use an ActiveGate with the lowest possible index. That is, if several ActiveGates with the low index are available, OneAgents will try to switch between the available ActiveGates on a regular basis.

If the preferable ActiveGate is not available, OneAgent tries the next higher index, until a connection is established. In that case, OneAgent will regularly check in the background for availability of ActiveGates with a lower index.

Multi-environment ActiveGate can have only one zone that is valid across all connected environments.

Unconfigured OneAgents

OneAgents with no network zone configured (that includes all OneAgents from the Default network zone) work as if the network zone doesn't exist.

Such OneAgents try to connect to any ActiveGate in a random order and choose the first responding Environment ActiveGate. For load balancing, after a few minutes they try to switch to the next responding Environment ActiveGate.

Managed If no Environment ActiveGate can be reached, OneAgents connect to the first responding Cluster ActiveGate. For load balancing, after a few minutes they try to switch to the next responding Cluster ActiveGate. In that case, OneAgent traffic goes to the Managed cluster uncompressed.