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
- Install the zRemote module for z/OS monitoring
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 | x86-64 host-based deployment on Linux and Windows | s390 host-based deployment on Linux | Containerized deployment |
|---|---|---|---|---|
OneAgent routing |
|
|
| |
OneAgent routing |
|
|
| |
OneAgent routing |
|
|
| |
OneAgent routing |
|
|
| |
OTLP Ingest |
| — |
| |
Memory dumps |
|
| — | |
AWS |
|
| — | |
Cloud Foundry |
|
| — | |
Kubernetes |
|
|
| |
Azure |
|
| — | |
Extensions 1.0, Extensions 2.0 |
| — | — | |
Database insights |
|
| — | |
VMware |
|
| — | |
REST API |
|
| — | |
Log Monitoring |
|
| — | |
HTTP Metric API |
|
| — | |
OTLP Ingest |
|
| — | |
Beacon forwarder |
|
| — |
Functionality available for ActiveGates running synthetic monitors from a private location
| Functionality | Module name | x86-64 host-based deployment on Linux and Windows | s390 host-based deployment on Linux | Containerized deployment |
|---|---|---|---|---|
Synthetic |
| — | — | |
Synthetic |
| — | — |