App Server Agents Supported Environments

This page provides an aggregated view of the supported environments for the App Server agents.

App Server agents have been tested successfully on AWS Outposts using these instructions: Install App Server Agents

Java Agent

This page lists the application environments and versions supported by the AppDynamics Java Agent.

Java Agent Supported Platforms

In the following tables, note that:

• A dash ("-") in a table cell indicates that this column is not relevant or not supported for that particular environment.
• In cases where no version is provided, assume that all versions are supported. Contact AppDynamics Sales for confirmation.
• For environments that require additional configuration, a separate table describing or linking to configuration information follows the support matrix.
• For environments supported by AppDynamics End User Monitoring, see Supported Environments and Versions - Web EUM.
• For environments supported by AppDynamics Server Visibility, Machine Agent Requirements and Supported Environments.

JVM Support

The AppDynamics Java Agent uses the standard JVM Tool Interface (JVMTI) mechanism allowing it to instrument any software running on a JVM supporting this mechanism.

AppDynamics certifies the successful operation of the basic mechanisms of instrumentation used by the agent on the following Java runtimes.  These capabilities are supported on both JRE or full JDK installations.

Where the agent supports the following advanced memory monitoring features, they are listed for the JVM: Object Instance Tracking (OIT), Automatic Leak Detection (ALD), Content Inspection (CI), and Access Tracking (AT).

Unless listed on this page, builds downloaded from other sources are not officially supported.

JVM	OS	Memory Monitoring Features
AdoptOpenJDK 8, 9, 10, 11, 12, 13, 14, 15, 16 ( supported for both Hotspot and OpenJ9 JVMs)	Linux, Windows, MacOS	OIT (supported only for Hotspot JVM), ALD, CI, AT
Amazon Corretto 8, 11, and 17	Linux, Windows	OIT, ALD, CI, AT
Azul Zing 15.x.	Linux x64	OIT, ALD
Azul Zulu OpenJDK 8, 9, 10, 11, 13, 14, 15, 16, 17 JDK11 is supported from 4.5.6 onwards JDK13 is supported from 4.5.15 onwards JDK14 is supported from 20.4.0 onwards JDK15 is supported from 20.10.0 onwards JDK16 is supported from 21.4.0 onwards JDK17 is supported from 21.11.0 onwards	Linux, Windows	OIT, ALD, CI, AT
JVM - BellSoft Liberica JDK 8, 11, 16, and 17	Linux, Windows, MacOS	OIT, ALD
GraalVM 20.0.0, 20.2.0, 21.1.0, 21.3.0	Linux, Windows, MacOS	OIT, ALD, CI, AT
HP OpenVMS
IBM JVM 1.8.x	AIX, HP-UX, Linux, Solaris, Windows, z/OS	ALD, CI Object instance tracking, automatic leak detection, and custom memory structure monitoring are not supported with the AppDynamics IBM Java Agent. IBM JVMs can be instrumented with the AppDynamics Sun Java Agent to work around this limitation; however, this only enables automatic leak detection and custom memory structure monitoring. Object instance tracking is not available. Working around this limitation can result in negative performance impact and is not recommended. In such cases, the IBM JVM needs to be restarted to enable custom memory structure monitoring.
Oracle Rockit JVM 28.1+	Linux Intel 64, Windows
Oracle/Sun JVM 8, 9, 10, 11, 12, 13, 14, 15, 16, 17 JDK11 is supported from 4.5.6 onwards JDK12 is supported from 4.5.11 onwards JDK13 is supported from 4.5.15 onwards JDK14 is supported from 20.4.0 onwards JDK15 is supported from 20.10.0 onwards JDK16 is supported from 21.4.0 onwards JDK17 is supported from 21.11.0 onwards	Solaris Sparc 64, Windows, Linux	OIT, ALD, CI, AT Content Inspection and Access Tracking require a JVM restart.
Oracle OpenJDK 8, 9, 10, 11, 12, 13, 14, 15, 16, 17 Oracle OpenJDK builds supported above are those that can be downloaded from https://jdk.java.net/.  OpenJDK11 is supported from 4.5.6 onwards OpenJDK12 is supported from 4.5.11 onwards JDK13 is supported from 4.5.15 onwards JDK14 is supported from 20.4.0 onwards JDK15 is supported from 20.10.0 onwards JDK16 is supported from 21.4.0 onwards JDK17 is supported from 21.11.0 onwards	Solaris Sparc 64, Windows, Linux	OIT, ALD

JVM Application Server and Framework Support

AppDynamics supports the use of the Java Agent to instrument any application component running on a supported JVM, irrespective of how that component is built. The power of the AppDynamics platform is that it can automatically discover the topology and behavior of complex enterprise applications without requiring deep technical knowledge of the application's underlying code.

Frequently, Java-based systems employ standard framework code to implement business logic. Automatic instrumentation of framework code relies on knowledge of the business logic and programming patterns employed by the framework. AppDynamics instrumentation targets processing hand-offs between components, called entry points and exit points, either within the JVM or between JVMs. This includes hand-offs between frameworks in cases where multiple frameworks are being used together. This section covers the capabilities for frameworks for which AppDynamics provides automatic detection rules.

Monitoring application components built using frameworks not listed here may require custom configuration. The custom configuration may involve, for example, custom POJO entry or exit points. If you understand how the application behaves internally, you can easily configure this type of instrumentation. For more complex configuration tasks, contact customer support to discuss how to engage the AppDynamics customer success organization.

JVM Language Frameworks Support

No additional configuration is required for these frameworks.

Java Framework Support

The Java Agent supports these Java frameworks. Some require additional configuration as indicated in the Configuration Notes column.  

Java Agent OpenTelemetry Framework Support

Application Servers

The Java Agent supports the following application servers. Some require additional configuration. Click the link on the server or OSGi Runtime for information about additional requirements or related configuration topics. The agent usually discovers application servers as an entry point.

Servlet 3.x detection is not supported.

PaaS Providers

Message Oriented Middleware Support

The Java Agent supports the following message oriented middleware environments. Some require additional configuration as indicated in the Configuration Notes column. Message oriented middleware servers are usually found by the Java Agent as an entry point.

JDBC Drivers and Database Servers Support

The Java Agent supports these JDBC driver and database server environments. AppDynamics can follow transactions using these drivers to the designated database.

Notes:

• Type II is a C or OCI driver
• Type IV is a thin database client and is a pure Java driver

NoSQL/Data Grids/Cache Servers Support

The Java Agent supports these NoSQL, data grids and cache server environments. Some require additional configuration. Click the link on the database, data grid or cache name in the following support matrix for information about additional configuration required or related configuration topics. 

RPC/Web Services API/HTTP Client Support

The Java Agent supports these RPC, web services or API framework types. Some require additional configuration as indicated in the Configuration Notes column.

Business Transaction Error Detection

The Java Agent supports the following logging frameworks for business transaction error detection:

• Apache Log4j and Log4j 2 
• java.util.logging
• Simple Logging Facade for Java (SLF4J)
  Support for the following method has been added: public void error(String format, Object... argArray)
• Logback

To instrument other types of loggers, see Error Detection.

.NET Agent

Supported Runtime Environments

This section lists the environments where the .NET Agent does some automatic discovery after little or no configuration. See Browser RUM Supported Environments for additional supported environments.

Out-of-process IIS applications should be instrumented as standalone applications.

OS Versions

All versions of Windows (x86/x64) and Linux (x64) operating systems (OS) supported by the target runtime and operating system vendor. 

Runtimes

• Microsoft .NET Frameworks
  • 3.5 SP1
    
  • 4.6.2
    
  • 4.7.x
    
  • 4.8
    
• Microsoft .NET Core and Microsoft .NET
  

  • Microsoft .NET Core 3.1

  • Microsoft .NET 6.0

Hosts

• Managed Standalone Applications
• Managed Windows Services
• Microsoft IIS
• Microsoft SharePoint 2010, 2013 as services running inside IIS

Microsoft Windows Azure

• Azure App Services on Windows in the Azure Portal
  • Web Apps
  • Web Jobs
  • API Apps
  • Container Services
  For Azure App Services, certain infrastructure monitoring features are not supported, those include: CLR crash reporting, machine snapshots, and Windows performance counter monitoring.
• Azure Cloud Services
  • Web Roles
  • Worker Roles

Automatically Discovered Business Transactions

The .NET Agent discovers business transactions for the following frameworks by default. The agent enables detection without additional configuration.

* The .NET Agent automatically discovers entry points for ASP.NET web forms with the Async property set to "true" in the Page directive.

Supported Loggers for the .NET Agent

• Log4Net
• NLog
• System Trace
• Windows Event Log
• Loggers on .NET Core that implement the Microsoft.Extensions.Logging.ILogger API

If you are using a different logger, see Error Detection.

Remote Service Detection

The .NET Agent automatically detects these remote service types. The agent enables detection by default. You do not need to perform extra configuration.

* The agent discovers asynchronous transactions for the Microsoft .NET 4.5 framework. See Asynchronous Exit Points for .NET.

Supported Windows Azure Remote Services

Cache Clients

Data Storage Detection

The .NET Agent automatically detects the following data storage types. The agent enables detection by default. You do not need to perform extra configuration.

* The agent discovers asynchronous transactions for the Microsoft .NET 4.5 framework. See Asynchronous Exit Points for .NET.

Supported ADO.NET Clients

AppDynamics can monitor any ADO.NET client version and type. Clients we've tested include the following:

* Microsoft, SQL Server, and Windows are registered trademarks of Microsoft Corporation in the United States and other countries.

Other Backends

• ADO.NET backend calls (SqlClient, MySql, SQLite, PostgreSQL)
• EntityFramework

.NET Agent Frameworks for OpenTelemetry

Limitations

• Tier network dashboard not supported on .NET Core / .NET runtime
• Node memory not supported on Linux

• Cisco Secure Application does not support .NET Framework

• Cisco Secure Application does not support single file deployment

Unsupported .NET Features

• Assembly trimming 
• Assembly unloadability 

• Trim self-contained deployments, and executables

Node.js Agent

This page provides an overview of supported environments for the Node.js Agent.

The Node.js Agent is supported on RedHat and Docker Hub.

Node.js Agent Versions

• Node.js version less than 6.x: 
• • This version of AppDynamics agent supports Node.js versions 6.0 and above.
  • For older versions of Node.js, use the AppDynamics agent 4.5.11 by installing with npm install appdynamics@4.5.11.
• Node.js version less than 8.x on Mac: 
  • This version of AppDynamics agent on Mac OS supports Node.js >= 8.0.
  • For older versions of Node.js, use the AppDynamics agent 4.5.11 by installing with npm install appdynamics@4.5.11.

Operating Systems

• Alpine Linux Docker >= 3.7 on 64-bit platform
• Linux distribution based on glibc 2.5 and later and the x86/x86-64 architecture
• Mac OS X >= 10.8, x86/x86-64 architecture
• Windows Server 2012 R2 and later on 64-bit platform with Node.js >= 0.12.0

Transaction Naming

HTTP Exit Points

See Node.js Documentation for the Node.js HTTP client library.

Database Exit Points

• NoSQL
  AppDynamics displays NoSQL databases as Remote Services.

PHP Agent

PHP Agent Support

PHP Versions

PHP Agent supports these versions of PHP:

• 7.0
• 7.1
• 7.2
• 7.3
• 7.4
• 8.0

PHP ZTS Agent supports these versions of PHP:

• 7.2
• 7.3
• 7.4

PHP Web Servers

Apache 2.2 and 2.4 in these modes:

• prefork mode using mod_php
• worker MPM mode using mod_fastcgi with php-fpm or mod_fcgid with php-cgi

Any web server compatible with php-fpm.

Operating Systems

Any Linux distribution based on glibc>=2.12 or GLIBCXX_>=3.4.19 and the x86 64-bit architecture.

The PHP agent does not support Power Architecture.

PHP Frameworks and Protocols

Framework/Protocol	Version < PHP 8	Version >= PHP 8	Entry Point Type
Drupal	7		Drupal
Drupal	8	9.1+	PHP MVC
WordPress	3.4+, 4.x, 5.x	5.6+	Wordpress
Zend	1, 2, 3	3+	PHP MVC
CodeIgniter	2.x, 3.x, 4.x	3+	PHP MVC
FuelPHP	1.5x, 1.6x, 1.8x	1.8.2	PHP MVC
Magento	1.5, 1.6, 1.7, 2.3		PHP MVC
Symfony	1, 2, 3, 4	5.2+	PHP MVC
CakePHP	2.x, 3.x, 4.x	4+	PHP MVC
Laravel	5.7, 6, 8, 9.x	6.20.+	PHP MVC
HTTP			PHP Web
CLI			PHP CLI

PHP 8 supports the framework versions only from the mentioned versions. The versions below these are not supported.

If your PHP framework is not listed here, the agent detects your entry points as PHP Web and names the business transactions based on the first two segments of the URI — the default naming convention for PHP Web transactions. So it is still possible to monitor applications on unsupported frameworks. Laravel BTs are detected as symfony, as laravel itself is built on top of symfony.

There are few limitations of the PHP Agent. The PHP Agent does not:

• Support Zend Monitor
• Officially support plug-ins that encrypt and, or obfuscate PHP code such as Zend Guard or ionCUBE Loader
• Support compatibility with the Xdebug module
• Support the pcntl_fork function which forks the child/sub-processes

Transaction Naming

Framework/Environment	Default Transaction Naming
Drupal	page callback name
Wordpress	template name
PHP MVC Frameworks	controller:action
PHP Modular MVC Frameworks	module:controller:action
PHP Web	URI
PHP Web Service	service name.operation name
PHP CLI	last two segments of the script's directory path plus the name of the script

Virtual host prefixing is available for all supported entry point types except PHP CLI.

PaaS Providers

PaaS Provider	Buildpack
Pivotal Cloud Foundry	https://github.com/Appdynamics/php-buildpack See http://docs.pivotal.io/appdynamics/index.html for information about integration with PCF.

Exit Points

Supported HTTP Exit Points
curl/curl-multi*
drupal_http_request()
fopen(), file_get_contents()
Zend_HTTP_Client::request()

^*The total time reported for a curl/multi_curl request in the Controller is the same as reported by the function curl_getinfo. Also, we report the the following execution metrics in the exit call details for the curl/multi_curl request which are included in the total time:

•  namelookup_time
• connect_time
• pretransfer_time
• redirect_time

Supported Database Exit Points
MySQL old native driver (removed for PHP 7)
MySQLi Extension*
OCI8
PDO
PostgreSQL accessed via PDO and pgsql extensions

^* mysqli_multi_query is not supported.

Supported Cache Exit Points
Memcache
Memcached
Predis 0.8.5 and 1.1.1, on PHP versions 7.0 and higher
Phpredis 4.1

Although Predis is a full PHP client library, the PHP Agent supports Predis as an exit point only, not as an entry point.

Supported Web Service Exit Points
PHP SOAPClient
NuSOAP 0.9.5

Supported Message Queue Exit Points
RabbitMQ

RabbitMQ support requires the amqp extension.

Opcode Cache Compatibility

Alternative PHP Cache (APC)

Python Agent

Python Agent Support

Python Versions

The Python agent supports these Python versions:

• Linux: Python 3.6, 3.7, 3.8, 3.9, and 3.10
• Alpine Linux: Python 3.6, 3.7, 3.8, 3.9, and 3.10

Operating Systems

The Python agent operates on:

• Linux distribution based on glibc 2.12+ and x86 64-bit architecture
• Alpine Linux (3.13+) distribution based on musl 1.2.2+ and x86 64-bit architecture

The Python agent does not support Power Architecture.

Python Frameworks and Protocols

Python Agent supports:

• ASGI supported frameworks such as FastAPI
• WSGI supported frameworks such as Django, Flask, CherryPy, Bottle, and Pyramid 
• Tornado

You can configure the agent to instrument any WSGI-based and ASGI-based application or framework as Python Web, including but not limited to those listed below.

At present, the Python agent fully supports exception detection in Django, Flask, CherryPy, Bottle, Pyramid, Tornado, and FastAPI frameworks. Other frameworks and custom applications may install exception handlers that effectively hide some exceptions from the agent. In such cases, the agent will only detect exceptions during exit calls, missed exceptions that are propagated to the WSGI or ASGI middleware, and exceptions reported via the custom business transaction API.

ASGI-Based Framework	Version	Notes
FastAPI	0.72.0 - 0.82.0	Only HTTP endpoints are supported

WSGI-Based Frameworks	Version	Notes
WSGI	1.0	Entry point type: Python web Default transaction naming: the first two segments of the URI
Bottle	0.12.19
CherryPy	18.6.1
Django	3.1.6
Flask	1.1.2
PasteDeploy	2.1.0
Pyramid	2.0
mod_wsgi	4.7.1

Miscellaneous Frameworks	Version	Notes
Tornado	3.2 - 4.5,  5.x (without asyncio), and 6.0	Entry point type: Python web Default transaction naming: the first two segments of the URI

Database Exit Points

Supported Database Exit Points	Version
cx_Oracle	5.1.x
MongoDB	3.1+
MySQL-Python
mysqlclient
MySQL Connector/Python
Psycopg 2
PyMySql
TorMySql

HTTP Exit Points

Supported HTTP Exit Points
httplib*
httplib2
requests
urllib
urllib2
urllib3
tornado.httpclient

^* The agent detects calls to any external library built on top of httplib. Therefore, backend calls to such services, such as, boto, dropbox, python-twitter are detected and displayed as HTTP exit calls.

Cache Exit Points

Supported Cache Exit Points
Memcache
Redis-py

Apache Web Server Agent

Apache Server Agent Support

Apache Web Servers

Supported Apache Web Server Version
Apache HTTP Server 2.2.x Apache HTTP Server 2.4.x IBM HTTP Server >= 7.0 Oracle HTTP Server >= 11g

Operating Systems

• Any Linux distribution based on glibc >= 2.12
•  RHEL5 is not supported from 20.x onwards. Support is applicable for glibc2.5+ ( RHEL6 or later).

If you encounter an ELF warning message, it may be related to the incorrect version of glibc. Verify that your operating system has the suitable glibc version.

The Apache Web Server agent does not support Power Architecture.

Automatically Discovered Business Transactions

The Apache Agent automatically discovers the following business transactions:

Type	Custom Configuration Options	Downstream Correlation
Web (HTTP)	Yes	Yes

By default the agent excludes requests for the following static file types:

bmp
cab
class
conf
css
doc
gif
ico

jar
jpeg
jpg
js
mov
mp3
mp4
pdf

png
pps
properties
swf
tif
txt
zip

Remote Service Detection

Apache Modules

The Apache Agent automatically detects loaded Apache modules as remote services. The agent excludes a list of common modules from detection.

Show the list of excluded modules...

core.c

http_core.c

mod_access_compat.c

mod_actions.c

mod_alias.c

mod_allowmethods.c

mod_appdynamics.cpp

mod_auth_basic.c

mod_auth_digest.c

mod_authn_alias.c

mod_authn_anon.c

mod_authn_core.c

mod_authn_dbd.c

mod_authn_dbm.c

mod_authn_default.c

mod_authn_file.c

mod_authn_socache.c

mod_authnz_ldap.c

mod_authz_core.c

mod_authz_dbd.c

mod_authz_dbm.c

mod_authz_default.c

mod_authz_groupfile.c

mod_authz_host.c

mod_authz_owner.c

mod_authz_user.c

mod_autoindex.c

mod_cache.c

mod_cache_disk.c

mod_cgi.c

mod_data.c

mod_dbd.c

mod_deflate.c

mod_dir.c

mod_disk_cache.c

mod_dumpio.c

mod_echo.c

mod_env.c

mod_expires.c

mod_ext_filter.c

mod_file_cache.c

mod_filter.c

mod_headers.c

mod_include.c

mod_info.c

mod_lbmethod_bybusyness.c

mod_lbmethod_byrequests.c

mod_lbmethod_bytraffic.c

mod_lbmethod_heartbeat.c

mod_log_config.c

mod_logio.c

mod_lua.c

mod_mem_cache.c

mod_mime.c

mod_mime_magic.c

mod_negotiation.c

mod_perl.c

mod_python.c

mod_remoteip.c

mod_reqtimeout.c

mod_rewrite.c

mod_setenvif.c

mod_slotmem_plain.c

mod_slotmem_shm.c

mod_so.c

mod_socache_dbm.c

mod_socache_memcache.c

mod_socache_shmcb.c

mod_speling.c

mod_ssl.c

mod_status.c

mod_substitute.c

mod_suexec.c

mod_systemd.c

mod_unique_id.c

mod_unixd.c

mod_userdir.c

mod_usertrack.c

mod_version.c

mod_vhost_alias.c

prefork.c

util_ldap.c

For End User Monitoring, the Apache Agent does not support automatic injection of the Javascript adrum header and footer to instrument web pages.

Third-Party Modules

The Apache Agent >= 20.5 requires the use of the latest version of SiteMinder 12.52 SP1 to eliminate a known bug in SiteMinder.

C++ Agent

C/C++ Supported Platforms

Operating Systems

• Any Linux distribution based on glibc >= 2.5 and the x86 32-bit or x86 64-bit architecture
• Windows Server >= 2012 R2
• Visual Studio >= 2015

To develop with the C++ SDK, you need Visual Studio >= 2015 . However, the SAP ABAP Agent on Windows leverages the same SDK and does not require development work.

You must install the Visual Studio C++ Redistributable; the full development environment is not required. 

Go Language Agent 

Go Supported Platforms

Language Support

All Go language versions are currently supported.

Operating Systems

• Any Linux distribution based on glibc >= 2.5, and the x86 32-bit or x86 64-bit architecture
• Mac OS X >= 10.8 on x86/x86-64 architecture

AppDynamics does not currently support Mac on Apple silicon (Apple M1 chip, ARM-based architecture). 

IIB Agent

IIB Agent Support

This page provides the supported versions, operating systems, and node types of the IIB agent. The AppDynamics IIB agent supports the Linux and AIX operating systems.

Operating Systems

The IIB agent supports these operating systems:

• Linux x86-64
• AIX v7.1 and v7.2

IIB Versions

The IIB Agent supports these versions of IIB for the Linux and AIX operating systems:

IIB Node Types

The agent can continue business transactions detected upstream at these node types:

• SOAPInput
• HTTPInput
• JMSInput
• MQInput

The agent can detect and tag exit calls for downstream correlation at these node types:

• SOAPRequest
• HTTPRequest
• JMSOutput, JMSReply
• MQOutput, MQReply

The agent can detect database backend calls for these node types:

• DatabaseRetrieve
• DatabaseRoute

All nodes are represented within AppDynamics Business Transactions as Threads. You can view the per node timings in the tree view of the Business Transaction dashboard and in the transaction snapshots.