ActiveGate purposes and functionality
- Latest Dynatrace
- 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
| Functionality | Module name | x86-64 host-based deployment on Linux and Windows | s390 host-based deployment on Linux | arm64 host-based deployment on Linux | Containerized deployment |
|---|---|---|---|---|---|
OneAgent routing |
|
|
|
| |
OneAgent routing |
|
|
|
| |
OneAgent routing |
|
|
|
| |
OneAgent routing |
|
|
|
| |
Memory dumps |
|
|
|
| |
AWS |
|
|
|
| |
Cloud Foundry |
|
|
|
| |
Kubernetes |
|
|
|
| |
Azure |
|
|
|
| |
Extensions |
|
|
|
| |
Database insights |
|
|
|
| |
VMware |
|
|
|
| |
REST API |
|
|
|
| |
Log Monitoring |
|
|
| ||
HTTP Metric API |
|
|
|
| |
OTLP Ingest |
|
|
|
| |
OTLP Ingest |
|
|
|
| |
Log Monitoring |
|
|
| ||
Beacon forwarder |
|
|
|
| |
Debugging |
|
|
|
|
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