OneAgent platform and capability support matrix

This page describes which capabilities are supported by OneAgent on different operating systems and platforms.


GA
Generally available and fully supported.

Preview
These features are in the final stages of development and are ready to be previewed. Preview features aren't production-ready and they aren't officially supported.

Future
A feature or technology support that is either on the roadmap or may be considered on-demand.

Not planned
A feature or technology support that Dynatrace does not currently plan to pursue.
n/a
Not applicable

Operating systems

The tables below contain information about the supported OneAgent capabilities for various supported operating systems. Note that Alpine Linux is supported in containers only, see Alpine Linux (musl libc) based containers.

Code modules

1
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
PHP
1
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
Apache, IHS
1
1
n/a
NGINX
1
n/a
n/a
n/a
n/a
Microsoft IIS
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a

IBM technologies

IBM App Connect Enterprise
n/a
n/a
IBM Integration Bus
n/a
n/a
IBM CICS
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a
IBM IMS
n/a
n/a
n/a
n/a
n/a
n/a
n/a
n/a

OneAgent SDK

OneAgent SDK for C/C++
OneAgent SDK for Java
OneAgent SDK for .NET
n/a
n/a
n/a
n/a
n/a
OneAgent SDK for Node.js
n/a
n/a
OneAgent SDK for Python
n/a
n/a
1

We added support for Python, C++, and other runtimes via OpenTelemetry instead of the Dynatrace SDK (which is Dynatrace-proprietary). This is available on any platform.

Other modules

OS module1
n/a
Network module
n/a
Log module
n/a
Extension module
n/a
JMX extensions
Extension Execution Controller3
1

OS module is required for out-of-the-box infrastructure alerting capabilities.

2

Log module support is limited to custom log sources, no log auto-detection is performed.

3

Extension Execution Controller is an interface providing support for local metric ingestion and local Dynatrace Extensions. For more information, see Metric ingestion and Extensions.

Features

Auto-update of all modules
n/a
Auto-injection of code modules
n/a1
Universal injection of code modules
Auto-injection for containers
n/a
Non-privileged
n/a
n/a
1

Global auto-injection isn't possible for AIX. Instead, use the universal injection approach, as described on the AIX OneAgent installation page.

Enterprise cloud platforms

The tables below contain information about the supported OneAgent capabilities for various supported Cloud platforms.

Cloud Foundry application-only also applies to SAP Cloud.

OneAgent deployment via container (OneAgent Operator) on OpenShift and Kubernetes has some limitations compared to standard OneAgent installation.

Code modules

1

Out-of-the-box infrastructure alerting capabilities are not supported for application-only code modules.

OneAgent SDK

Other modules

OS module
n/a
n/a
n/a
Network module
n/a
n/a
n/a
Log module
1
1
1
Extension module
n/a
n/a
n/a
1

This is supported today via Dynatrace's FluentD integration

Features

Auto-update of all modules
n/a
n/a
n/a
Auto-injection of code modules
n/a
n/a
n/a
Universal injection of code modules
Auto-injection for containers
n/a
n/a
n/a
Non-privileged
n/a
n/a
n/a
n/a
n/a
n/a
n/a

Cloud application platforms

The tables below contain information about the supported OneAgent capabilities for supported Cloud application platforms.

Code modules

1

Both 64-bit ARM (AWS Graviton2 processors) and 64-bit x86 architectures are supported.

2

Both Google Cloud Run execution environments are supported, with some restrictions.

Features

Auto-injection of code modules

Auto-injection automatically injects code modules into monitored applications in a completely transparent and automatic fashion that requires no manual configuration or intervention. This approach to deep monitoring is supported for Windows (Docker only) and Linux. Among other things, auto-injection also automatically injects code modules into Docker, containerd, CRI-O, and Cloud Foundry Garden containers. This means that you don't have to change any container images on monitored platforms to gain full insights.

Universal injection of code modules

Universal injection allows Dynatrace to inject code modules into applications in a unified way across multiple platforms, in situations where auto-injection isn't available. This applies to AIX and Solaris as well as to Cloud Foundry application-only, OpenShift application-only, Kubernetes application-only, Heroku, Google App Engine, AWS Fargate, and AWS App Runner.

The feature is described on the AIX/Solaris OneAgent installation page. It is also part of the OpenShift application-only/Kubernetes application-only integration and the container platforms Google App Engine and AWS Fargate.

Outside of these specific use cases, this feature isn't to be used directly!

The Cloud Foundry buildpack integrations and Dynatrace Heroku buildpack use this transparently under the hood without any need for manual intervention or configuration.

Any form of undocumented injection (for example, older forms of manual injection) aren't supported.

Alpine Linux (musl libc) based containers

Dynatrace supports Alpine Linux (musl libc) based containers on monitored Linux x86_64 hosts. This includes OpenShift, Kubernetes and Cloud Foundry installations and all forms of Docker environments. In these environments Dynatrace OneAgent automatically injects the code modules into the applications running inside the container.

Alpine Linux is also supported in OpenShift application only and Kubernetes application only integrations as well as when pushing Docker images to Cloud Foundry and Heroku. This happens via the universal injection.

Dynatrace OneAgent doesn't support direct installation in Alpine based Linux systems.

Dynatrace OneAgent doesn't support monitoring binaries built against GNU C Library (glibc) running on Alpine based Linux systems using gcompat library.

OneAgent deployment via Dynatrace Operator

Dynatrace Operator deploys the OneAgent to Kubernetes or OpenShift clusters through a containerized approach. There are some limitations associated with deploying OneAgent via Dynatrace Operator. These include:

  • The auto-update mechanism of modules is disabled for container rollouts. However, Dynatrace Operator ensures the restart of OneAgent pods to receive OneAgent updates.
  • Auto-injection of code-modules is disabled for native (i.e., non-containerized) processes.
  • JMX extensions aren't supported for technologies outside of containers

For a detailed overview of limitations, see Set up Dynatrace OneAgent as a Docker container.