When do I need to install an ActiveGate?

Dynatrace offers two types of ActiveGate: Environment ActiveGate and Cluster ActiveGate. If you use Dynatrace SaaS, you only need to install an Environment ActiveGate. Dynatrace Managed deployments typically require both ActiveGate types, though the most important type for Dynatrace Managed deployments is the Cluster ActiveGate. For Dynatrace Managed deployments, see additional ActiveGate use cases for Dynatrace Managed.

An Environment ActiveGate can be

  • Classic - runs on a virtual or physical host and has multiple modules (except for the Synthetic module, which can't coexist with other modules)
  • Cloud-native - runs in a container and has only one module

ActiveGate purposes

When you install an ActiveGate, you must select one of the three available ActiveGate purposes:

The modules for each purpose are described below.

Route OneAgent traffic to Dynatrace, monitor cloud environments, or monitor remote technologies with extensions

Note: Cloud-native ActiveGates are limited to one module per container.

  • Message routing classic cloud-native

ActiveGate knows about the runtime structure of your Dynatrace environment and routes messages from OneAgents to the correct server endpoints.

  • Buffering and compression classic cloud-native

ActiveGate collects messages from OneAgent instances and builds bulks, which are then sent in compressed form to Dynatrace Server. This means network overhead could be considerably reduced, depending on the number of OneAgents communicating with the ActiveGate and on the amount of data transferred by OneAgents.

  • Authentication classic cloud-native

ActiveGate authenticates OneAgent requests (SSL handshake and environment ID authentication).

  • Access sealed networks classic cloud-native

In case OneAgents don't have access to the internet, you should install an ActiveGate to serve as a single access point, rather than opening the firewall for multiple hosts running OneAgents. This approach greatly reduces the effort of managing and maintaining firewall and/or proxy configuration settings.

  • Store memory dumps classic

Dynatrace supports both automatic and manual capture and analysis of memory dumps on monitored hosts. Memory dumps need to be stored in a centralized location for download and analysis. Since such dumps are often large and can contain sensitive data, Dynatrace doesn't allow you to upload dumps to the Dynatrace cluster in the cloud. Instead you should set up an ActiveGate and configure it to serve as a host for memory dumps. The Dynatrace UI provides you with download URLs for the ActiveGate REST API that serves the dumps.

  • Control load distribution of AWS monitoring classic

AWS service monitoring is a resource-intensive task. Therefore, to monitor more than 2,000 AWS resources, you must install an ActiveGate and configure AWS monitoring.

  • Monitor Cloud Foundry classic

To connect your Cloud Foundry foundations to Dynatrace, you're required to install an ActiveGate instance to complement Cloud Foundry process- and host-level metrics collected by Dynatrace OneAgent with additional metadata and metrics pulled from the Cloud Foundry API. This integration allows you to use the Cloud Foundry overview page as well as the automatic detection of your Cloud Foundry organizations in addition to other Cloud Foundry process properties like space, space ID, application, application ID, and instance index.

  • Monitor Kubernetes/OpenShift classic cloud-native

To connect your Kubernetes/OpenShift clusters to Dynatrace to take advantage of the dedicated Kubernetes/OpenShift overview page, you need to run an ActiveGate in your environment (version 1.163+).

  • Monitor Azure classic

To integrate Azure monitoring data, a dedicated ActiveGate is required to poll metadata and metrics from Azure APIs. This integration enables monitoring of Azure Services (especially for cloud services where we can't install OneAgent) and also monitoring through the Dynatrace UI.

  • Monitor using an ActiveGate extension classic

With ActiveGate extensions, you can extend Dynatrace monitoring to any remote technology that exposes an interface, where OneAgent installation is not an option. For example, PaaS technologies, network devices, or cloud technologies. ActiveGate extensions (aka remote plugins) are executed on ActiveGates and can acquire metrics and topology information from remote sources, thereby fully integrating remote technology monitoring into Dynatrace Smartscape and problem detection. Currently, this capability is offered only by Environment ActiveGates.

  • Monitor virtualized infrastructure classic

An ActiveGate can poll your vCenter or standalone ESXi hosts to obtain information about all important resources that ESXi servers provision to your virtual machines (for example, CPU usage, memory consumption, and data-store related activity on your VMware platform). To acquire this information, Dynatrace needs a component installed in your environment that has access to the vCenter API.

Run synthetic monitors from a private location

Synthetic-enabled ActiveGates are more demanding in terms of hardware requirements. See System and hardware requirements for synthetic-enabled ActiveGates.

  • Execute private HTTP monitors classic

For HTTP monitors, an ActiveGate or a group of ActiveGates can act as a private Synthetic location. The HTTP monitor will then be executed via the specified ActiveGate(s).

  • Execute private browser monitors classic

For browser monitors, an ActiveGate or a group of ActiveGates can act as a private Synthetic location. With browser monitors executed on the ActiveGate or ActiveGates, you can check the availability of internal resources that are inaccessible from outside your network.

To run browser monitors from a private location, you must first satisfy the engine dependencies, before you install the ActiveGate. See Create a private Synthetic location for detailed instructions.

Route z/OS traffic to Dynatrace

  • zRemote code module classic

To monitor a mainframe environment you need an ActiveGate with built-in zRemote code module. The zRemote code module aggregates measurements from all z/OS code modules and sends it to Dynatrace through an ActiveGate, installed on a different host.