ActiveGate purposes and functionality

  • 4-min read

An ActiveGate can be used for three different use cases, which we refer to as purposes:

Each purpose comes with a different subset of functional modules. Modules should not be mixed between purposes—such re-configuration is not supported.

Functionality available for the routing-monitoring ActiveGates

1

Log ingest API endpoint is supported on containerized ActiveGate in a number of supported Kubernetes flavours when provisioned with Dynatrace Operator. Since ActiveGate uses file buffers, persistent storage is recommended to prevent data loss during restarts or rescheduling

Functionality available for ActiveGates running synthetic monitors from a private location

Functionality available for ActiveGates with the zRemote module