Beginning in February 2020, AppDynamics switched from Semantic Versioning to Calendar Versioning for some agents and the first deployments of SaaS Controllers. In March 2020, the entire product suite will use Calendar Versioning.


Skip to end of metadata
Go to start of metadata

This page provides an aggregated view of the supported environments for the app server agents.

.NET Agent Support

Supported Runtime Environments

This section lists the environments where the .NET Agent does some automatic discovery after little or no configuration.

OS Versions

  • Microsoft Windows Server 2008 (32-bit and 64-bit)
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2016
  • Microsoft Windows 7, 8, 8.1, 10

Microsoft .NET Frameworks

Microsoft .NET Framework versions 2.0, 3.0, 3.5, 4.0, 4.5, 4.5.2, 4.6, 4.7 on the following runtime environments:

  • Microsoft IIS versions 6.0, 7.0, 7.5, 8.0, 8.5, 10
  • Managed Windows Services
  • Managed Standalone Applications
  • Microsoft SharePoint 2010, 2013 as services running inside IIS
  • Microsoft ASP.NET Core 2.0/2.1 for Windows
  • Microsoft ASP.NET Core 2.2 for Windows is supported for .NET Agent versions 4.5.7 and later
  • Microsoft ASP.NET Core 3.1 for Windows is supported for .NET Agent versions 20.3 and later

Microsoft Windows Azure

  • Azure App Services for .NET 4.6 environments in the Azure Portal
    • Web Apps
    • Web Jobs
    • API Apps
    • Container Services
    For Azure App Services, the .NET Machine Agent disables certain .NET Machine Agent infrastructure monitoring features: CLR crash reporting, machine snapshots, and Windows performance counter monitoring.
  • Azure Cloud Services
    • Web Roles
    • Worker Roles

Unsupported Frameworks

  • Microsoft .NET versions 1.0, 1.1
  • Unmanaged native code

Automatically Discovered Business Transactions

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

Type

Custom Configuration Options?

Downstream Correlation?

ASP.NET*

Yes

Yes

ASP.NET MVC 2
ASP.NET MVC 3
ASP.NET MVC 4
ASP.NET MVC 5

Yes

Yes

ASP.NET Core on the full frameworkYesYes

Open Web Interface for .NET (OWIN) web API

YesYes

.NET Remoting

No

See Enable Correlation for .NET Remoting.

Windows Communication Foundation (WCF)

No

Yes

Web Services including SOAP

No

Yes

Message Queues



Apache ActiveMQ NMS framework and related MQs

No

Yes

IBM WebSphere MQ

No

Yes

Microsoft Message Queuing (MSMQ)NoYes
Microsoft Service Bus / Windows Azure Service BusNoYes
NServiceBus over MSMQ or RabbitMQ transportNoYes
RabbitMQYesYes

TIBCO Enterprise Message Service

No

Yes

TIBCO Rendezvous

No

Yes

Windows Azure QueueNoNo

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

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

Remote Service Detection

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

Type

Custom Configuration Options?

Async Detection?*

Downstream Correlation?

Directory Services, including LDAP

No

No

N/A

HTTP

Yes

See Asynchronous Exit Points for .NET.

Yes

MongoDB: C# and .NET MongoDB Driver version 1.10, 2.0NoSee Asynchronous Exit Points for .NET.N/A

.NET Remoting

Yes

No

See Enable Correlation for .NET Remoting.

WCF

Yes

See Asynchronous Exit Points for .NET.

Yes

WCF Data Services

Yes

No

No

Web Services, including SOAP

Yes

See Asynchronous Exit Points for .NET.

Yes

Azure Service Fabric Remoting v1 and v2—for the .NET Microservices Agent---
Data Integration


Microsoft BizTalk Server 2010, 2013NoYesSee Correlation Over Microsoft BizTalk.

Message Queues




Apache ActiveMQ NMS framework and related MQs

Yes

No

Yes

IBM WebSphere MQ (IBM XMS)

Yes

No

Yes

Microsoft Message Queuing (MSMQ)

Yes

See MSMQ Backends for .NET

See MSMQ Backends for .NET

Microsoft Service Bus / Windows Azure Service Bus

No

Async exit points only

Yes

NServiceBus over MSMQ or RabbitMQ transportNoSee NServiceBus Backends for .NETYes
RabbitMQSee RabbitMQ Backends for .NETNoYes

TIBCO Enterprise Message Service

Yes

No

Yes

TIBCO Rendezvous

Yes

No

Yes

Windows Azure Queue

No

No

No

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

Supported Windows Azure Remote Services

Type

Customizable Configuration?

Downstream Correlation?

Azure Blob

No

No

Azure Queue

No

No

Microsoft Service Bus

No

Yes

Cache Clients

Type

Customizable Configuration?

Async Detection?*

AppD for Databases?

StackExchange.RedisNoYesNo


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.

Type

Customizable Configuration?

Async Detection?*

AppD for Databases?

ADO.NET (see supported clients below)

Yes

Yes

No

Windows Azure Blob Storage

No

Yes

No

Windows Azure File StorageNoYesNo
Windows Azure Table StorageNoYesNo

* 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:

Database Name

Database Version

Client Type

Oracle

10, 11, 12

ODP.NET

Oracle

10, 11, 12

Microsoft Provider for Oracle

MySQL

5.x

Connector/Net and ADO.NET

Microsoft SQL Server*

2005, 2008, 2012

ADO.NET

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




Node.js Agent Support

Node.js Versions

  • The 4.5.11 Node.js agent supports Node.js v0.8, v0.10, v0.12, v4, v5, v6, v7, v8, v9, v10, and v11.
  • The 4.5.12+ Node.js agent supports Node.js v6, v7, v8, v9, v10, and v11. (v8, v9, v10, v11 on Mac).
  • The 4.5.21+ Node.js agent supports Node.js v8, v9, v10, v11 and v12.

For agent versions 4.5.12 and on the npm install will stop and print a message for the two scenarios listed:

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

Operating Systems

  • The agent is compatible with any Linux distribution based on glibc 2.5+
  • Mac OS X 10.8+ (Agent / Node.js version specific compatibility as noted) 
  • Windows Server 2008R2+ and newer for 64 bit applications for Node.js versions 0.12.0 and higher (Agent / Node.js version specific compatibility as noted)

Transaction Naming

Entry Type

Default Transaction Naming

Node.js Web

URI

HTTP Exit Points

Supported HTTP Exit Points

Node.js HTTP client library

See http://nodejs.org/api/http.html for information about the Node.js HTTP client library.

Database Exit Points

  • MongoDB - displayed as Remote Service
  • MySQL
  • PostgreSQL
  • Riak - displayed as HTTP backends
  • Couchbase
  • DynamoDB using the official AWS SDK driver
  • Cassandra

Cache Exit points

  • Memcached
  • Redis

PHP Agent Support

PHP Versions

PHP Agent supports the following versions of PHP:

  • 5.6
  • 7.0
  • 7.1
  • 7.2
  • 7.3
  • 7.4

PHP Web Servers

Apache 2.2 and 2.4 in the following 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.5+.

Mac OS X 10.9+

PHP Agent supports 32-bit operating system only on PHP 5.6.


PHP Frameworks and Protocols

Framework/Protocol

Version

Entry Point Type

Drupal

7

Drupal

Drupal8PHP MVC

WordPress 

3.4+, 4.x, 5.x

Wordpress

Zend

1, 2, 3

PHP MVC

CodeIgniter 

2.x, 3.x, 4.x

PHP MVC

FuelPHP 

1.5x, 1.6x, 1.8x

PHP MVC

Magento 

1.5, 1.6, 1.7

PHP MVC

Symfony  

1, 2, 3, 4

PHP MVC

CakePHP  

2.x, 3.x, 4.x

PHP MVC

Laravel5.7, 6PHP MVC

HTTP 


PHP Web

CLI
PHP CLI

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:

  • Monitor PHP applications in Zend Thread Safety (ZTS) mode. If you are using ZTS, AppDynamics suggests that you review your dependencies on ZTS to confirm that you actually need it, and if you do not, to switch to the non-ZTS mode
  • 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


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 Serviceservice name.operation name
PHP CLIlast 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 ProviderBuildpack
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 5.6 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 Support

Python Versions

  • The Python agent supports CPython 2.6, 2.7, 3.4, 3.5, 3.6, and 3.7.

Operating Systems

  • Any Linux distribution based on glibc 2.5+
  • Mac OS X 10.8+

Python Frameworks and Protocols

Framework/Protocol

Version

Entry Point Type

Default Transaction Naming

WSGI

1.0

Python Web

First two segments of URI

Tornado

3.2 - 4.5

Python Web

First two segments of URI

AppDynamics has tested the Python Agent on Tornado, Django, Flask, CherryPy, Bottle, and Pyramid.

You can configure the agent to instrument any WSGI-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, and Tornado frameworks. Other WSGI frameworks and custom WSGI 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, uncaught exceptions which are propagated to the WSGI server, and exceptions reported via the custom business transaction API.

WSGI-Based Frameworks

Notes

Bottle


CherryPy


Django


Flask


PasteDeploy


Pyramid


Database Exit Points

Supported Database Exit PointsVersion
cx_Oracle5.1.x
MongoDB3.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, and so on are detected and displayed as HTTP exit calls.

Cache Exit Points

Supported Cache Exit Points

Memcache

Redis-py

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.5+

Architectures

  • 32-bit
  • 64-bit

Automatically Discovered Business Transactions

The Apache Agent automatically discovers the following business transactions:

TypeCustom Configuration OptionsDownstream Correlation
Web (HTTP)YesYes

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.


C/C++ Agent Supported Platforms

Operating Systems

  • Any Linux distribution based on glibc 2.5+
  • Windows Server 2008 R2 and above
  • Visual Studio 2015, or later

Note

When developing with C++ SDK, Visual Studio 2015+is a definite requirement. However, when using SAP ABAP Agent on Windows, it leverages the same SDK without requiring any development work. Hence, the Visual Studio C++ Redistributable is required to be installed and not a full development environment. 

Go SDK Support

Operating Systems

  • Any Linux distribution based on glibc 2.5+
  • Mac OS X 10.8+

IIB Agent Support

This topic provides information about 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 the following operating systems:

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

IIB Versions

The IIB agent supports the following versions of IIB for the Linux and AIX operating systems:

  • Linux: IIB v9, IIB v10, and ACE v11
  • AIX: IIB v9 and IIB v10

IIB Node Types

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

  • SOAPInput
  • HTTPInput
  • JMSInput
  • MQInput

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

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

For MQ, we use the MQRFH2 message header to provide correlation. Any applications consuming MQ messages from IIB with the IIB agent must support the MQRFH2 header.


The agent can detect database backend calls for the following 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.

  • No labels