This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
48 rates

This page provides an aggregated view of the system requirements for the Controller and agents. 

Supported Platform Matrix for the AppDynamics Controller

Controller Operating System Requirements

The Controller is supported on the following operating systems:

Linux (32 and 64-bit)

Microsoft Windows (32 and 64 bit)

  • Red Hat Enterprise Linux (RHEL) 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, and 7.0
  • CentOS 5.9, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, and 7.0
  • Fedora 14
  • Ubuntu 8, 12
  • Open SUSE 11.x
  • SUSE Linux Enterprise Server 12
  • Cloud: Amazon EC2, Rackspace, Azure
  • Windows Server 2003
  • Windows Server 2008, Windows Server 2008 R2
  • Windows Server 2012 R1 Standard and Datacenter, Windows Server 2012 R2 Standard and Datacenter
  • Windows 7 Pro
  • Windows 8

You can use the following file systems for Controller machines that run Linux:

  • ZFS
  • EXT4
  • XFS

Supported Web Browsers for the Controller UI

The AppDynamics UI is an HTML 5-based browser application that works best with the latest version of any modern browser. The Controller UI has been tested with the following browsers and versions:

  • IE 9+
  • Safari 6+
  • Chrome 16+
  • Firefox 6+
    Opera and older versions of Firefox, IE, and Safari browsers may still operate well but some features may not display as intended.

The Controller UI requires Flash Player 10 or greater; AppDynamics recommends version 11.

LDAPv3 Support

You can delegate Controller UI authentication and authorization to external directory servers that comply with LDAP (Lightweight Directory Access Protocol) version 3.

While the Controller should be able to work with any LDAPv3-compliant server, it has been verified against these LDAP products:

  • Microsoft Active Directory for Windows Server 2008 SP2+
  • OpenLDAP, 2.4+

Supported Platform Matrix for the Java Agent

This page documents known environments in which the Java Agent has been used to instrument applications. The Java Agent can target specific Java bytecode. This provides wide-ranging flexibility, so if an environment is not listed here, this does not preclude the Java Agent from being able to extract valuable performance metrics. Contact AppDynamics Sales for additional details.

Notes:

  • 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 Monitoring, Standalone Machine Agent Requirements and Supported Environments.

JVM Support

The AppDynamics Java Agent supports applications running with a JRE or a full JDK. These are the known JVM environments in which the Java Agent has been used to instrument applications. 

Vendor

Implementation

Version

Operating System

Object Instance
Tracking

Automatic Leak
Detection

Custom Memory Structures

      Content InspectionAccess TrackingRequires JVM Restart?

Oracle

Java HotSpot

7 Update 45+

Solaris Sparc 64, Windows, Linux

-

-

-

--
Oracle

Java SE
(Standard Edition) 

81Solaris Sparc 64, Windows, LinuxYesYesYesYesYes

BEA

JRockit

1.5

-

-

Yes

Yes

YesYes
BEAJRockit1.6, 1.7--YesYes--

Oracle

JRockit JVM

28.1+

Linux Intel 64 Windows

-

-

-

--

IBM

JVM

1.5.x, 1.6.x, 1.7.x

-

-

Yes, as noted2

Yes, as noted2,3

--

SUN

JVM

1.5, 1.6, 1.7

-

Yes

Yes

Yes

Yes-

Open Source

OpenJDK

1.6

Linux, windows, everywhere

-

Yes

-

--

HP

OpenVMS

-

-

-

-

-

--

Notes:

For examples of instrumenting new language constructs in Java SE 8, see Instrumenting Java 8 Constructs.    

Object instance tracking, automatic leak detection, and custom memory structure monitoring are not supported with the IBM Java Agent on an IBM JVM. It's possible to work around this limitation by using the Java Agent for the Sun and JRockit JVM on an IBM JVM, but doing so can result in a negative performance impact.  

For IBM JVMs, a restart is required after configuring the custom memory structure.  

JVM Language Frameworks Support

No additional configuration is required for these frameworks.

Vendor

JVM Language 
Framework

Version

Correlation/
Entry Points

Exit Points

Transports

Notes

Open Source /
Typesafe Reactive Platform

Akka Actor

2.1 – 2.3

Yes

Yes

Netty

Remoting exit/entry supported.

Persistence (experimental module in v2.3) is not currently supported.

Open Source

Groovy

-

Yes

Yes

 

 

Open Source /
Typesafe Reactive Platform

Play for Scala

2.1 – 2.3

Yes

-

HTTP over Netty

Includes framework specific entry points
Open Source /
Typesafe Reactive Platform
Spray toolkit (Spray.io)1.1.1YesYesHTTPEntry points are detected and configurable as servlet entry point and exit points as HTTP exits.

Pivotal

Grails

-

-

-

-

 

The Typesafe Reactive Platform is a JVM-based runtime and collection of tools used to build reactive applications. This includes ScalaPlayAkka, and Spray.io

Application Servers

These are the known application server environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the server or OSGi Runtime name in the following support matrix for information about additional configuration required or related configuration topics. Application servers are usually found by the Java Agent as an entry point.

Vendor

Application Server / 
OSGi Runtime

Version

SOA Protocol

RMI Supported

JMX

Entry Points

Apache

Felix

-

-

-

-

Yes

Apache

Sling

-

-

-

-

Yes

Apache

Tomcat

5.x, 6.x, 7.x, 8.x

-

-

Yes

 

Apache

Resin

1.x - 4.x

-

-

-

-

Adobe

Cold Fusion

8.x, 9.x

-

No

-

Yes

 

Equinox

-

-

-

-

Yes

Eclipse

Jetty

6.x, 7.x

-

-

-

-

IBM

InfoSphere

8.x

-

-

-

Yes

IBM

WebSphere  

6.1

JAX-WS

-

-

Yes

IBM

WebSphere  

7.x

JAX-WS

Yes, detect and correlate

Yes for WebSphere PMI

Yes

IBMWebSphere8.xJAX-WSYes, detect and correlate-Yes
Open SourceJBoss Wildfly (formerly JBoss Server)

4.x, 5.x, 6.x, 7.x, 8.x

 Yes Yes

Open Source

Liferay Portal

-

-

-

-

-

Sun/Oracle

GlassFish Enterprise Server

2.x

-

-

Yes

Yes

Oracle

GlassFish Server and 
GlassFish Server Open Source Edition

3.x, 4.x

-

-

Yes for AMX

Yes

Oracle and BEA

WebLogic Server

9.x+

JAX-WS

Yes, detect and correlate for 10.x

Yes

Yes

Red HatJBoss Enterprise Application Server 6.11, 6.2.0, 7.x Yes Yes
Software AGwebMethods9.5, 9.6---Yes
TibcoActiveMatrix BusinessWorks Service Engine5.x---Yes
 

Application Server (OC4J)

-

-

Yes, detect and correlate for 10.x

-

Yes

-

Grails, with Tomcat 7.x, Glassfish v3, 
Weblogic 12.1.1 (12c)

-

-

-

-

 

Notes:

  • Servlet 3.x detection is not supported.

Application Server Configuration

For application server environments that require additional configuration, this section provides some information and links to topics that help you configure the environment. Environments in the Application Server Support table that require additional configuration, link to the configuration table below. 

Application ServerConfiguration Notes

Apache Felix

Apache Sling
Apache Tomcat
Apache Resin
Apache Cold Fusion 
Equinox
Eclipse Jetty
IBM InfoSphere

IBM WebSphere

Sun GlassFish Enterprise Server

GlassFish JDBC connection pools can be manually configured using MBean attributes and custom JMX metrics

Oracle GlassFish Server (including GlassFish Server Open Source Edition)
Oracle and BEA WebLogic Server
Software AG webMethods
Tibco ActiveMatrix BusinessWorks Service Engine
Open source JBoss Wildfly
Red Hat JBoss Enterprise Application Server
Red Hat JBoss Web Server

Message Oriented Middleware Support

These are the known message oriented middleware environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the messaging server name in the following support matrix for information about additional configuration required or related configuration topics. Message oriented middleware servers are usually found by the Java Agent as an entry point.

Vendor

Messaging Server

Version

Protocol

Correlation/Entry Points

Exit Points

JMX

Configuration Notes
AmazonSimple Queue Service (SQS)--Yes (correlation only)Yes-

Apache

ActiveMQ

5.x+

JMS 1.x

Yes

Yes

Yes

 

Apache

ActiveMQ

5.x+

STOMP

No

-

Yes

 

Apache

ActiveMQ

5.8.x+

AMQP 1.0

No

-

Yes

Apache

ActiveMQ

5.x+

SOAP

Yes

-

Yes

Apache

Axis

1.x, 2.x

JAX-WS

Yes

Yes

-

Default exclude rules exist for Apache Axis, Axis2, and Axis Admin Servlets. See also:

Apache

Apache CXF

2.1

JAX-WS

Yes

Yes

-

 

Apache

Synapse

2.1

HTTP

Yes

Yes

-

Fiorano

Fiorano MQ

 

-

-

-

-

 

IBM

IBM Web Application Server (WAS)

6.1+, 7.x

Embedded JMS

-

Yes

-

No additional configuration is required. See also:

IBM

IBM MQ (formerly IBM WebSphere MQ)

6.x+

JMS

Yes

Yes

-

Open Source

Open MQ

-

-

-

-

-

 

Mulesoft

Mule ESB

3.4

HTTP

Yes

Yes

-

OracleJava Message Service 2.0JMSCorrelation of the listener
is disabled by default 
Yes  

Oracle

Oracle AQ

-

JMS

-

Yes

-

 

Oracle / BEA

WebLogic

9.x+

JMS 1.1

Yes

Yes

Yes

Progress

SonicMQ

-

-

-

-

-

 

Pivotal

RabbitMQ

-

HTTP

-

Yes

-

No additional configuration is required. See also:

Rabbit

RabbitMQ Spring Client

-

-

Yes

Yes

-

No addition configuration is required. See also:

Red HatHornetQ (formerly JBoss Messaging and JBoss MQ)-   Yes 
Red Hat

JBoss A-MQ

4.x+

-

-

-

Yes

 

Spring

Spring Integration

2.2.0

JMS

Yes

Yes

Yes

WSO2ESB4.7.0-YesYes-  

 

JDBC Drivers and Database Servers Support

These are the known JDBC driver and database server environments in which the Java Agent has been used to instrument applications. AppDynamics can follow transactions using these drivers to the designated database.

JDBC Vendor

Driver Version

Driver Type

Database Server

Database Version

Apache

10.9.1.0

Embedded or client

Derby

-

Apache

-

-

Cassandra

-

Progress

DataDirect

data connectivity for ODBC and JBDC driver access, data integration, and SaaS and cloud computing solutions

-

-

IBM

JDBC 3.0 version 3.57.82 or JDBC 4.0 version 4.7.85

DB2 Universal JDBC driver

DB2

9.x

IBM

JDBC 3.0 version 3.66.46 or JDBC 4.0 version 4.16.53

DB2 Universal JDBC driver

DB2

10.1

IBM

-

Type IV

Informix

-

Microsoft

4

Type II

MS SQL Server

2012*

Oracle MySQL, MySQL Community

5.x

Type II, Type IV

MySQL

5.x

Open Source

Connector/J 5.1.27

Type IV

MySQL

5.x

Open Source

-

Type IV

Postgres

8.x, 9.x

Oracle

9.x

Type II, Type IV

Oracle Database

8i+

Sybase

jConnect

Type IV

Sybase

-

Teradata  Teradata-

Notes:

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

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)
  • Logback

To instrument other types of loggers, see Configure Error Detection.

NoSQL/Data Grids/Cache Servers Support

These are the known NoSQL, data grids and cache server environments in which the Java Agent has been used to instrument applications. 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. 

Vendor

Database/Data Grid/Cache

Version

Correlation/Entry Points

JMX

Configuration Notes
AmazonDynamoDB -Custom Exit-
AmazonS3-Custom Exit-

Apache

Casandra (DataStax, REST) and Cassandra CQL3

1.x

Correlation

Yes

Apache

Lucene - Apache Solr

1.4.1

Entry Points

Yes

Red HatJBoss DataGrid---

 

JBoss Cache TreeCache

-

-

-

 

 JBoss Infinispan5.3.0+ Correlation  

Terracotta

EhCache

-

-

-

Open Source

Memcached

-

-

-

Open Source

MongoDB

-

-

-

Oracle

Coherence

3.7.1

Custom-Exit

Yes

 

 

 

 

-

-

 

Java Frameworks Support

These are the known Java framework environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the Java framework name in the following support matrix for information about additional configuration required or related configuration topics. 

Vendor

Framework

Version

SOA protocol (WebServices)

Auto Naming

Entry Points

Exit Points

Detection

Adobe

BlazeDS

-

HTTP and JMS adaptor

-

Yes

 

-

Adobe

ColdFusion

8.x, 9.x

-

-

Yes

-

Configuration required for transaction discovery

Apache

Cassandra with Thrift framework

-

-

-

Yes

Yes

Apache Thrift Entry and Exit points are detected

Apache

Struts

1.x, 2.x

-

-

Yes

 

Struts Actions are detected as entry points, struts invocation handler is instrumented

Apache

Tapestry

5

-

-

Yes

-

Not by default

 

Wicket

-

-

No

Yes

-

Not by default

Apple

WebObjects

5.4.3

HTTP

Yes

Yes

-

Yes

 

CometD

2.6

HTTP

Yes

Yes

--

Eclipse

RCP (Rich Client Platform)

-

-

-

-

-

-

Google

Google Web Toolkit (GWT)

2.5.1

HTTP

Yes

Yes

-

-

JBoss

JBossWS Native Stack

4.x, 5.x

Native Stack

-

-

-

-

Open Source

Direct Web Remoting (DWR)

-

-

-

-

-

-

Open Source

Enterprise Java Beans (EJB)

2.x, 3.x

-

-

Yes

-

-

Open Source

Grails

-

-

-

Yes

-

Not by default

Open Source

Hibernate JMS Listeners

1.x

-

-

-

-

-

Open Source

Java Abstract Windowing Toolkit (AWT)

-

-

-

-

-

-

Open Source

Java Server Faces (JSF)

1.x

-

Yes

Yes

-

Not by default

Open Source

Java Server Pages

2.x

-

Yes

-

-

Yes

Open Source

Java Servlet API

2.x

-

-

-

-

-

Open SourceJersey1.x, 2.xREST, JAX-RSYesYesNoNot by default
Open SourceWebSocket1.0 (Java EE 7, JSR-356)-

Yes,
BT Naming not configurable 

Yes, correlation
not supported
Yes

Detection is automatic

Oracle

Coherence with Spring Beans

2.x, 3.x

-

-

-

-

-

Oracle

Swing (GUI)

-

-

-

-

-

-

Oracle

WebCenter

10.0.2,10.3.0

-

-

-

-

-

Open Source

JRuby HTTP

-

-

-

Yes

-

Not by default

Spring

Spring MVC

-

-

-

Yes

-

Not by default

Java Frameworks Configuration

For the Java framework environments that require additional configuration, this section provides some information and links to topics that help you configure the environment.  Environments in the Java Frameworks Support table that require additional configuration, link to the configuration table below. 

Java FrameworkConfiguration Notes
Adobe BlazeDS 
Adobe ColdFusion

Configuration is required for transaction discovery

Apache Cassandra with Thrift framework

No additional configuration is required.

Apache Struts
Apache Tapestry
Wicket
Apple WebObjects

Business transaction naming can be configured via getter-chains, see

CometD

Open Source Enterprise Java Beans (EJB)

Open Source Hibernate JMS Listeners

No additional configuration is required. See also:

Open Source Java Server Faces (JSF)
Open Source Java Server Pages

Open Source Jersey

Open Source JRuby HTTP
Open Source WebSocket

Node property: websocket-entry-calls-enabled

Spring MVC

RPC/Web Services API/HTTP Client Support

These are the known Java framework environments in which the Java Agent has been used to instrument applications. Some require additional configuration. Click the link on the RPC, web services or API framework name in the following support matrix for information about additional configuration required or related configuration topics.

Vendor

RPC/Web Services API Framework

Version

SOA Protocol-
WebServices

Auto Naming

Correlation/Entry Points

Exit Points

Configurable BT Naming Properties

Detection

Apache

Apache CXF

2.1

JAX-WS

Yes

Yes

Yes

Yes

Yes

Apache

Apache HTTP Client

-

HTTPClient (now in Apache HTTP Components)

Yes

Yes (correlation only)

Yes

-

Yes

Apache

Apache Thrift

-

-

Yes

Yes

Yes

Yes

Yes

IBM

WebSphere

6.x

JAX-RPC

-

-

-

-

-

IBM

WebSphere

7.x, 8.x

JAX-RPC

-

-

-

-

-

IBM

Websphere

7.x, 8.x

IIOP

-

-

-

-

-

Red Hat

JBoss A-MQ

4.x+

RMI

Yes

Yes

Yes

Yes

Yes

Open Source

java.net.Http

-

HTTP

Yes

-

Yes

Yes

Yes

Open SourceHTTPClient 0.3-3Oracle SOA (and potentially others that embed this library) -Correlation: Yes; Entry: NoYes-Yes

Oracle

GlassFish Metro

-

JAX-WS

-

-

-

-

-

Oracle

GlassFish Metro with Grails

-

JAX-WS

-

Yes

-

-

Not by Default

Oracle

Oracle Application Server

ORMI

-

no

-

-

-

-

Oracle

WebLogic

10.x

T3, IIOP

Yes

Correlation: Yes; Entry: No

Yes

-

Yes

Oracle

WebLogic

9.x, 10.x

JAX-RPC

-

-

-

-

-

Sun

Sun RMI

-

IIOP

-

Not by Default

-

-

-

Sun

Sun RMI

-

JRMP

-

By Default

Yes

host/port

Yes

-

Web Services

-

SOAP over HTTP

-

Yes

Yes

-

-

RPC/Web Services API Framework Configuration

For the RPC and web service API environment that require additional configuration, this section provides some information and links to topics that help you configure the environment.  Environments in the RPC/Web Services API Framework Support table that require additional configuration, link to the configuration table below. 

Supported Platform Matrix for the .NET Agent

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 2003 (32-bit and 64-bit)
  • Microsoft Windows Server 2008 (32-bit and 64-bit)
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2

Microsoft .NET Frameworks

  • Microsoft .NET Framework versions 2.0, 3.0, 3.5, 4.0, 4.5, 4.5.2

Runtime Environments

  • Microsoft IIS versions 6.0, 7.0, 7.5, 8.0, 8.5
  • Managed Windows Services
  • Managed Standalone Applications
  • Microsoft SharePoint 2010, 2013 as services running inside IIS

Microsoft Windows Azure

  • Windows Azure Cloud Services (Web Roles and Worker Roles)

Unsupported Frameworks

  • Microsoft .NET versions 1.0, 1.1
  • Unmanaged native code
  • Windows Azure Web Sites

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

.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 App Agent for .NET 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 Configure Error Detection.

Remote Service Detection

The .NET Agent automatically detects the following remote service types. The agent enables detection by default. You don't 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

.NET Remoting

Yes

No

Requires configuration. 
See Enable Correlation for .NET Remoting.

WCF

Yes

See Asynchronous Exit Points for .NET.

Yes

WCF Data Services

Yes

No

No

Web Services, inlcuding SOAP

Yes

See  Asynchronous Exit Points for .NET.

Yes

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 .NET.Yes
   RabbitMQSee  RabbitMQ Backends for .NET.NoYes

   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. for details.

 

Supported Windows Azure Remote Services

Type

Configuration
can be customized

Downstream
Correlation

Azure Blob

No

No

Azure Queue

No

No

Microsoft Service Bus

No

Yes

Data Storage Detection

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

Type

Configuration Can
Be Customized

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. for details.

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.

Supported Platform Matrix for the PHP Agent

PHP Versions

Supported PHP Versions

Comment

5.2

Does not detect mysqli backends instantiated with the new keyword. See note below.
PHP 5.2 is not supported on OSX.

5.3

 

5.4

 

5.5

 

5.6 

PHP 5.2 Note

The PHP Agent is incompatible with PHP 5.2 applications that use the new keyword to instantiate a mysqli backend.
For example, AppDynamics will not detect the mysqli backend created by a PHP 5.2 application that uses an expression like this:

// Does not get detected.
$db = new mysqli("localhost", "user", "password", "database");

The workaround is to change such expressions to use mysqli_connect():

$db = mysqli_connect("localhost", "user", "password", "database");

PHP ZTS Note

The PHP Agent is incompatible with the mode of PHP called Zend Thread Safety (ZTS).

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 non-ZTS mode.

PHP Web Servers

Supported Web Server

Version

Comment

Apache

2.2

in prefork mode using mod_php

Apache

2.4

in prefork mode using mod_php

Apache

2.2

in worker MPM mode using mod_fastcgi with php-fpm or mod_fcgid with php-cgi

Apache 2.4

2.4

in worker MPM mode using mod_fastcgi with php-fpm or mod_fcgid with php-cgi

Any Web Server compatible with php-fpm

 

 

Operating Systems

Supported Operating System

Version

Comment

RHEL/CentOS

5.8+

SELinux is disabled.

Ubuntu

10+

SELinux is disabled.

Debian

6

SELinux is disabled.

OSXMavericks 

Architecture

Supported Architecture

32-bit

64-bit

PHP Frameworks and Protocols

Framework/Protocol

Version

Entry Point Type

Drupal

7

Drupal

WordPress 

3.4+

Wordpress

Zend

1 & 2

PHP MVC

CodeIgniter 

2.x

PHP MVC

FuelPHP 

1.5x & 1.6x

PHP MVC

Magento 

1.5, 1.6 & 1.7

PHP MVC

Symfony  

1 & 2

PHP MVC

CakePHP  

2.x

PHP 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. You can modify the naming convention used for PHP Web Entry points. See Configure PHP Web Transaction Naming.

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.

Exit Points

Supported HTTP Exit Points

curl/curl-multi

drupal_http_request()

fopen(), file_get_contents()

Zend_HTTP_Client::request()

Supported Database Exit Points

MySQL old native driver

MySQLi Extension

OCI8

PDO

PostgreSQL accessed via PDO and pgsql extensions New in 4.1.5

Supported Cache Exit Points

Version

Memcache

 

Memcached

 

Predis

0.8.5

Predis is supported on PHP versions 5.3 and higher.

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)

 

Correlation with AppDynamics for Databases

AppDynamics for Databases version 2.7.4 or higher is required if you want to correlate AppDynamics for Databases with the PHP Agent.

Supported Platform Matrix for the Node.js Agent

Node.js Versions

Node.js Agent Version

Node Versions Supported by this Agent

4.1.0

0.8.0 – 0.8.28
0.10.0 – 0.10.39
0.12.0 – 0.12.4

4.1.1

All versions supported by 4.1.0, plus:
0.12.5 – 0.12.6

4.1.2 – 4.1.7All versions supported by 4.1.1, plus: 
0.12.7
4.1.8 – 4.1.9All versions supported by 4.1.7, plus: 
0.12.9
4.1.10

All versions supported by 4.1.9, plus: 
4.0.0
4.1.0 – 4.1.2
4.2.0 – 4.2.6
4.3.0 – 4.3.2
4.4.0 – 4.4.2
5.0.0
5.1.0 – 5.1.1
5.2.0
5.3.0
5.4.0 – 5.4.1
5.5.0
5.6.0
5.7.0 – 5.7.1
5.8.0
5.9.0 – 5.9.1
5.10.0

 

Operating Systems

Supported Operating System

Linux 32-bit

Linux 64-bit

Mac OSX v10.9.2

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

Supported Database Exit Points

MongoDB

MySQL

PGSQL

Riak

Riak backends are automatically detected, but they are displayed as HTTP backends in the flowmaps.

Cache Exit Points

Supported Cache Exit Points

Memcached

Redis

Supported Platform Matrix for the Python Agent

Python Versions

Supported Python Versions 
CPython 2.6 
CPython 2.7 

Operating Systems

Supported Operating System

Linux 64-bit

Linux 32-but
Mac

Python Frameworks and Protocols

Framework/ProtocolVersionEntry Point Type
WSGI1.0Python Web

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

The agent may be configured 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, and CherryPy 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
Bottle
CherryPy
Django
Flask
PasteDeploy New in 4.1.3
Pyramid
Zope 3

Transaction Naming

Framework/EnvironmentDefault Transaction Naming
WSGIfirst two segments of the URI

Database Exit Points

Supported Database Exit PointsVersion
MySQL-Python 
MySQL Connector/Python 
Psycopg 2 

HTTP Exit Points

Supported HTTP Exit Calls
httplib*
httplib2
requests
urllib
urllib2
urllib3

*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, etc. are detected and displayed as HTTP exit calls.

Cache Exit Points

Supported Cache Exit Points

Memcache

Redis-py

 

 

Supported Platform Matrix for the Web Server Agent

Web Servers

Supported Web Server Version
  • Apache HTTP Server 2.2.x (32-bit and 64-bit)
  • Apache HTTP Server 2.4.x (32-bit and 64-bit)

Operating Systems

Supported Operation System
  • Ubuntu 11+ (32-bit and 64-bit)
  • Cent OS 5+ (32-bit and 64-bit)
  • Red Hat 5+ (32-bit and 64-bit)

Automatically Discovered Business Transactions

The Web Server 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 Web Server 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_dav.c

mod_dav_fs.c

mod_dav_lock.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 Web Server Agent does not support:
  • automatic injection of the Javascript adrum header and footer to instrument web pages.
  • server side business transaction correlation with Mobile Real User Monitoring.

Supported Platform Matrix for the Standalone Machine Agent

The Standalone Machine Agent provides platform-level metrics. It has a default built-in plugin for hardware monitoring. See Install the Standalone Machine Agent.

JVM Requirements for the Standalone Machine Agent

The Standalone Machine Agent runs on a Java Virtual Machine. JVM 1.7 is required.

The Standalone Machine Agent should work with most, if not all the JVMs supported by the Java Agent; however, the Standalone Machine Agent is only extensively tested with and fully supported on Oracle JDK and OpenJDK.

Supported Platforms for Default Hardware Monitor Plugin

Operating System

Architecture

Versions

Linux

x86

2.2 and above

Linux

amd64

2.6 kernel

Linux

ppc

2.6 kernel

Linux

ppc64

2.6 kernel

Linux

ia64

2.6 kernel

Linux

s390

2.6 kernel

Linux

s390x

2.6 kernel

Solaris

Sparc-32

2.6, 7, 8, 9, 10

Solaris

Sparc-64

2.6, 7, 8, 9, 10

Solaris

x86

8, 9, 10

Solaris

x86_x64

8, 9, 10

AIX

ppc

4.3, 5.1, 5.2, 5.3, 6.1

AIX

ppc64

5.2,5.3,6.1

HP-UX

PA-RISC

11

HP-UX

ia64

11

FreeBSD

x86

4.x

FreeBSD

x86

5.x, 6.x

FreeBSD

x64

6.x

FreeBSD

x86, x64

7.x,8.x

OpenBSD

x86

4.x,5.x

NetBSD

x86

3.1

Mac OS X

x86

10.4, 10.5, 10.6

Mac OS X

x64

10.5, 10.6

Windows

x86

NT 4.0, 2000 Pro/Server, 2003 Server, XP, Vista, 2008 Server, 7

Windows

x64

2003 Server, Vista, 2008 Server, 7

The following Linux distributions have been certified:

Distribution

Versions

Red Hat

6.2, 7.3, 8.0, 9.0

RHEL

3, 4, 5, 6

CentOS

3, 4, 5

Fedora

2, 3, 4, 5, 6, 7, 8, 9, 10

SuSE

10, 11

Ubuntu

6.06, 8.04, 8.10, 9.04

Debian

2.6, 3.0, 3.1, 3.2, 4.0, 5.0

VMware ESX

2.x, 3.0

XenServer

3.1, 3.2, 4.0, 4.1, 5.0

Slackware

10, 11

Mandrake

10

Scientific Linux

5

Gentoo

(info) Note: If you are using a 64-bit Operating System, use only a 64-bit Java Runtime Environment (JRE). For more details see Supported Platform Matrix for Default Hardware Monitoring Plugin.

Supported Platform Matrix for Browser Real User Monitoring

Browser Compatibility

  • IE6/7/8/9/10/11/Edge
  • Chrome, including Mobile
  • Firefox, including Mobile 
  • Safari, including Mobile
  • Opera

(info) Browsers are rapidly evolving, and not all versions have been specifically tested with Browser RUM. You can see which browser versions are likely to support the Resource Timing API functionality here.

Browser RUM Compatibility in Java Environments

Listed below are the injection types with their supported frameworks/technologies:

  • Automatic Injection: JavaServer Pages (JSP) compiled using the Jasper compiler. Jasper is the default JSP compiler in Tomcat, Glassfish, and JBoss.
  • Assisted Injection: All Servlet frameworks.
  • Manual Injection: All technologies that generate HTML pages.

See Set Up Your Application for Browser RUM for details.

Browser RUM Compatibility in .NET Environments

AppDynamics certifies Browser RUM instrumentation for the following .NET frameworks.

Web Application/ AJAX Frameworks

Versions

Additional Supported Script Injection Methods

ASP.NET Web Forms (.aspx)

3, 4

Automatic, Assisted Injection-Using Attribute Injection

ASP.NET MVC Web Forms (.aspx)

3, 4, 5

Automatic, Assisted Injection-Using Attribute Injection

ASP.NET MVC Razor

3, 4, 5

Assisted Injection-Using Attribute Injection

Microsoft SharePoint

2007, 2010

Automatic

 

(info) AppDynamics does not support Browser RUM instrumentation of legacy ASP (.asp) pages.

Supported Runtime Environments for .NET Browser RUM

  • Microsoft IIS versions 6.0, 7.0, 7.5, 8.0, 8.5

Supported Platform Matrix for Mobile RUM

Operating Systems

Supported Operating System

Version

iOS

5.1.1+

Android

2.3.3+

iDevice Architecture

Apple 32-bit ARM

Apple 64-bit A7

iOS Environments

Supported Framework

Version

XCode

5+

Apple WatchKit Extension Environments

Supported Architectures
watchOS 1 architectures in both watchOS 1 and 2 environments

 

Android Environments

Supported Framework

Version

Ant

 

Gradle

1.8, 1.10, 1.12, 2.1

Maven

3.1.1+

 

Supported HTTP Libraries

PlatformLibrary
iOSNSURLConnection, NSURLSession
AndroidHttpURLConnection, HttpsURLConnection, HttpClient
BothOther HTTP libraries can be added by using the agent SDK. See Use the APIs of the iOS SDK to Customize Your Instrumentation and Use the APIs of the Android SDK to Customize Your Instrumentation for more information.

Supported Compute Clouds for Automating Workflow

In order to create workflows that allow the automatic creation and deletion of cloud-based instances in response to load, the AppDynamics controller must have access to a cloud-provider-specific cloud connector extension. The AppDynamics Community provides many of these cloud connector extensions. You can download supported cloud connector extensions from the AppDynamics Exchange.

 

 

  • No labels