ActiveGate purposes and functionality
An ActiveGate can be used for three different use cases, which we refer to as purposes:
- Route OneAgent traffic to Dynatrace, monitor cloud environments, or monitor remote technologies using extensions
- Run Synthetic monitors from a private location
- Route z/OS traffic to Dynatrace
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
Functionality | Module name | Supported in | Supported in |
Message Routing | OneAgent routing | ![]() | ![]() |
Buffering and compression | OneAgent routing | ![]() | ![]() |
Authentication | OneAgent routing | ![]() | ![]() |
Accessing sealed networks | OneAgent routing | ![]() | ![]() |
Memory dumps | Memory dumps | ![]() | — |
AWS monitoring | AWS | ![]() | — |
Cloud Foundry monitoring | Cloud Foundry | ![]() | — |
Kubernetes/OpenShift monitoring | Kubernetes | ![]() | ![]() |
Azure monitoring | Azure | ![]() | — |
Monitoring using an ActiveGate extension | Extensions 1.0, Extensions 2.0 | ![]() | — |
Oracle database insights | Database insights | ![]() | — |
Monitoring virtualized infrastructure | VMware | ![]() | — |
Dynatrace API | REST API | ![]() | — |
Log Monitoring | Log Monitoring | ![]() | — |
Metric ingestion | HTTP Metric API | ![]() | — |
OpenTelemetry trace ingestion | OTLP Ingest | ![]() | — |
Real User Monitoring | Beacon forwarder | ![]() | — |
Functionality available for ActiveGates running synthetic monitors from a private location
Functionality | Module name | Supported in | Supported in |
Execute private HTTP monitors | Synthetic | ![]() | — |
Execute private browser monitors | Synthetic | ![]() | — |
Functionality available for ActiveGates routing z/OS traffic to Dynatrace
Functionality | Module name | Supported in | Supported in |
Route z/OS traffic to Dynatrace | zRemote | ![]() | — |