Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

How does EUM component compatibility work?

Table of Contents

How EUM Compatibility Works

Version Compatibility

Compatibility Example

 

How EUM Compatibility Works

This article breaks down version compatibility for the different EUM components: JavaScript Agents, Mobile Agents (iOS, Android, Xamarin, Cordova), the EUM Server, and the Events Service.

 

You may need to upgrade one component in order to get a bug fix, but want to know how the upgrade will impact your entire environment and reporting before doing so.

 

The various AppDynamics components talk to each other by exposing APIs and have a client/service relationship. For example, JavaScript Agents send browser metric data to the EUM Server using a collector API. In this case, the JavaScript Agent becomes the client for the EUM Server. If you upgrade the JavaScript Agent, you need to make sure that the EUM Server version is compatible in order to understand the call.

 

AppDynamics ensures that the components are backward compatible with their clients, but if the client (e.g., JavaScript Agent) is upgraded to a higher version, there could be compatibility issues. The client might be talking to the Server in a language that the Server might not understand. In this example, you would need to upgrade the EUM Server to a version equal to or higher than the JavaScript Agent.

 

Version Compatibility

Review the compatibility matrix below for various components of the AppDynamics environment.

 

Apache Web Server Agent version <= Controller version
Application Agent version(Java, .Net, Node.js Agent etc) <= Analytics Agent version

For Controller versions lower than 4.4.1Application (language) Agent version (Java, .Net, Node.js Agent, etc.) <= Controller version

*For Controller versions 4.4.1 or higherApplication (language) Agent version (Java, .Net, Node.js Agent, etc.) unrestricted

Analytics Agent version <= Controller version
Analytics Agent version <= Events Service version 
Controller version <= EUM Server version
Controller version <= Events Service version 
DB Agent version <= Controller version
EUM version <= Events Service version
JavaScript Agent version <= EUM Server version
Mobile Agent version: To determine the minimum versions of the Controller and EUM Serverrequired for supporting the latest features of the Mobile Agents, see the Mobile Agent Version and Deployment Support Matrix

Machine Agent v4.5.2+ is compatible with Controller v4.4.0+
Machine Agent v4.5.0 - 4.5.1 is compatible with Controller v4.5.0 - 4.5.x
Machine Agent v4.4.0 - 4.4.3 is compatible with Controller v4.4.0 - 4.4.3
Machine Agent v4.3.x, 4.4.x, and 4.5.x is compatible with Controller v4.5.x

 

*Backward compatibility is supported on the following agents starting in Release 4.5:

  • Java
  • .NET
  • Node.js
  • PHP
  • Python
  • Go SDK
  • C/C++

 

Compatibility Example

If you are upgrading your iOS Agent to the latest version, check that you are using at least the recommended minimum Controller and EUM Server versions so all features for that agent version will function correctly and there will be no unexpected side effects.

 

If you update your Controller and EUM Server, you should plan to upgrade the Events Service to ensure that the Events Service version is higher than or equal to the EUM Server and Controller version.

 

Although we encourage you to keep your environment components in compatible versions as stated above, in some cases, the components can still be compatible if they vary within just the patch version.

 

The process for the other Mobile Agents should be similar, but please refer to the Mobile Agent Version and Deployment Support Matrix for version specifications.

 

Last Updated: 3/15/19

Version history
Revision #:
20 of 20
Last update:
‎03-15-2019 11:45 AM
Updated by:
 
Labels (1)


Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.
Comments
I have had conflicting responses from AppD support concerning the compatibility of the standalone machine agent (a.k.a. Server Agent) with the controller. I am simply attempting to determine if a 4.4.1 SaaS controller will truly support a 4.4.3 standalone machine agent? From looking at the above, it appears that it would, but due to some issues we have run into AppD engineering had confirmed that "all newer version agents EXCEPT the machine agent can be supported by the 4.4.3 controller. We are again experiencing some issues and AppD support is now again stating that the 4.4.1 controller has no issues with a 4.4.3 machine agent. So, which way is it...... Any other experience or thoughts on this? Thanks much.

@Joe.Shaughnessy I apologize for the confusion. Here is a breakdown of compatability between the Machine Agent and the Controller:

 

Machine Agent v4.5.2 or newer is compatible with Controller v4.4.0 or newer
Machine Agent v4.5.0 - 4.5.1 is compatible with Controller v4.5.0 - 4.5.x
Machine Agent v4.4.0 - 4.4.3 is compatible with Controller v4.4.0 - 4.4.3
Machine Agent v4.3.x, 4.4.x, and 4.5.x is compatible with Controller v4.5.x

 

To answer your specific question, a v4.4.3 Machine Agent  would work with a v4.4.1  Controller. Please let us know if you have any further questions about this. 

 

We'll update the article to make this information clearer.