Supported Platform Matrix for the AppDynamics Controller

Controller Operating System Requirements

The Controller is supported on the following Operating Systems:

Supported Web Browsers for the Controller UI

The AppDynamics UI works best with the latest version of any modern browser along with the latest version of Flash. 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 use an external directory server to authenticate and authorize user access to the Controller UI. The Controller works with 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+

See Administer the Controller.

Supported Platform Matrix for the App Agent for .NET

Supported Runtime Environments

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

OS Versions

Microsoft .NET Frameworks

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

Runtime Environments

Microsoft Windows Azure

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

Unsupported Frameworks

Automatically Discovered Business Transactions

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

◊ New in 3.8.4, 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 App Agent for .NET

• Log4Net
• NLog
• System Trace
• Windows Event Log

If you are using a different logger, see Custom Logger Definitions.

Remote Service Detection

The App Agent for .NET automatically detects the following remote service types. The agent enables detection by default. You don't need to perform extra configuration.

† The agent discovers asynchronous transactions for the Microsoft .NET 4.5 framework. See Monitor Async Transactions for .NET for details.

Supported Windows Azure Remote Services

Data Storage Detection

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

Supported ADO.NET Clients

We 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.

Supported Platform Matrix for the App Agent for PHP

PHP Versions

PHP 5.2 Note

The app agent for PHP 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 app agent for PHP 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.

If you have a legacy infrastructure which requires ZTS or an app library that needs it, such as pthreads, contact AppDynamics Support.

PHP Web Servers

Operating Systems

Architecture

PHP Frameworks and Protocols

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 PHP Web Transaction Naming.

Transaction Naming

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

HTTP Exit Points

Database Exit Points

Cache Exit Points

Predis is supported on PHP versions 5.3 and higher.

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

Web Service Exit Points

Message Queue Exit Points

RabbitMQ support requires the amqp extension.

See also Monitor RabbitMQ Backends for PHP.

Opcode Cache Compatibility

Correlation with AppDynamics for Databases

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

Supported Platform Matrix for the Standalone Machine Agent

The 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 Machine Agent runs on a Java Virtual Machine.  JVMs versions 1.5 and higher are supported for most installations.

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

Supported Platforms for Default Hardware Monitor Plugin

The following Linux distributions have been certified:

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 Web EUM

End User Monitoring Browser Compatibility

The following Web browsers are certified for the JavaScript agent for Web EUM.

Web End User Monitoring (EUM) Compatibility in Java Environments

Manual injection for the JavaScript agent is available for all Java web application environments.

In addition, the following frameworks are certified for the following Web EUM instrumentation strategies.

• All these frameworks support manual injection of the JavaScript agent for Web EUM. 
• Additional supported script injection strategies are listed in the Script Injection column. See Set Up Your Application for Web EUM for details.

End User Monitoring (Web EUM) Compatibility in .NET Environments

AppDynamics certifies Web EUM instrumentation for the following .NET frameworks.

• All listed frameworks support manual injection of the JavaScript agent for Web EUM.
• Additional supported script injection strategies are listed in the Script Injection column. See Set Up Your Application for Web EUM for details.

AppDynamics does not support Web EUM instrumentation of legacy ASP (.asp) pages.

Supported Runtime Environments for .NET Web EUM

• Microsoft IIS versions 6.0, 7.0, 7.5, 8.0

Supported Platform Matrix for Mobile APM

Operating Systems

iDevice Architecture

iOS Environments

Android Environments

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.