Differences between containerized and host-based ActiveGates
- Latest Dynatrace
- 1-min read
ActiveGate deployed on a host using an installer—depending on a selected purpose—consists of multiple processes delivering several functionalities. The container image covers only a subset of that, provided by the core ActiveGate process.
Purposes
An ActiveGate container image currently supports only a subset of routing and monitoring as well as private synthetic.
For a complete overview, see ActiveGate purposes and functionality.
| Installer | Container | |
|---|---|---|
OneAgent routing |
|
|
API |
|
|
Infrastructure Monitoring |
|
|
Cloud monitoring |
|
|
Extensions |
|
|
Synthetic monitors |
|
|
ZRemote |
|
|
Auto-update
ActiveGate auto-update is supported only for host-based ActiveGates deployed using an installer.
In Kubernetes environments, ActiveGate updates are managed by the container runtime.
ActiveGate is updated automatically on pod restart whenever there is a new version available, unless the image already specifies a certain version.