Discussion Feed

To make sure you complete all the tasks necessary for upgrading your Dynamic Language Agents after a release, we recommend following the instructions below.   NOTE : The information in this article is not release-specific. You can reference it for any release   Table of Contents Prepare to upgrade your EUM servers, agents and SDKs Planning your EUM Server, Agent, and SDK upgrades  Plan your on-premises EUM server upgrade Plan your EUM agents and SDK upgrades How to upgrade your EUM Server, Agent, and SDK How do I upgrade my on-premises EUM Server?   How do I upgrade EUM Agents and SDKs?  Additional Resources   Prepare to upgrade your EUM servers, agents and SDKs Review the Product Announcements and Alerts page  for details on any intermediate versions between the current version of your instance and the version you are targeting. Review the compatibility matrix in our Community and documentation for various components of the AppDynamics environment. Review our EUM component compatibility article for details specific to EUM. Review the Mobile Agent Version and Deployment Support Matrix to determine the minimum versions of the Controller and EUM Server required for supporting the latest features of the Mobile Agents. For platforms where the Controller, EUM Server, and Events Service are being upgraded at the same time: The Controller version should be <= the Events Service version and you should perform the upgrades in a specific order. See Upgrade Platform Components for details on the upgrade order and instructions on upgrading the Events Service, which should be upgraded before the EUM Server .   Planning your upgrades Considerations for upgrading an on-premises EUM Server and EUM Agent and SDK are different. See each below.   Plan your on-premises EUM Server upgrade The EUM Server version should be less than or equal to (<=) the Events Service version Ensure the key matches between the Events Service, EUM Server, and Controller: analytics.accountAccessKey == ad.accountmanager.key.eum ==appdynamics.es.eum.key For instructions on configuring EUM connection settings, see:  Connect to the Events Service See Upgrade the Production EUM Server for step-by-step instructions. In addition to upgrading your server, you will need to follow the instructions on migrating your EUM data. For the 4.5 production EUM Server, the EUM MySQL database has been moved from the Controller host machine to the EUM Server host machine.   After upgrading your EUM Server, you can upgrade your Controller following the steps outlined in Upgrade the Controller using the Enterprise Console .   Plan your EUM agent and SDK upgrades Before upgrading EUM Servers, Agents and SDKs, review the following: Product Announcements and Alerts page for details on any intermediate versions between the current version of your instance and the version you are targeting. Review the compatibility matrix in our Community and documentation for various components of the AppDynamics environment. Review our EUM component compatibility article for details specific to EUM. Review the Mobile Agent Version and Deployment Support Matrix to determine the minimum versions of the Controller and EUM Server required for supporting the latest features of the Mobile Agents.   For platforms where the Controller, EUM Server, and Events Service are being upgraded at the same time , the Controller version should be lesser than or equal to (<=) the Events Service version. You must perform the upgrades in a specific order. For example, be sure to upgrade the Events Service before the EUM Server.   See Upgrade Platform Components for details on the upgrade order.    How to upgrade your EUM Server, Agent, and SDK See below for the considerations for upgrading your on-premises EUM Server, EUM Agent and SDK.   How do I upgrade my on-premises EUM Server?  The EUM Server version should be less than or equal to (<=) the Events Service version Ensure the key matches between the Events Service, EUM Server, and Controller: analytics.accountAccessKey == ad.accountmanager.key.eum ==appdynamics.es.eum.key For instructions on configuring EUM connection settings, see: Connect to the Events Service See Upgrade the Production EUM Server for step-by-step instructions. In addition to upgrading your server, you will need to follow the instructions on migrating your EUM data. For the 4.5 production EUM Server, the EUM MySQL database has been moved from the Controller host machine to the EUM Server host machine.   After upgrading your EUM Server, you can upgrade your Controller following the steps outlined in Upgrade the Controller using the Enterprise Console .   How do I upgrade EUM Agents and SDKs? Upgrade the JavaScript Agent Note: If you are a 4.4 SaaS customer and have an EUM license, we recommend upgrading to the latest JavaScript Agent. See Upgrade the JavaScript Agent. Upgrade the Mobile Agents See Upgrade iOS SDK for step-by-step instructions on upgrading manually or using CocoaPods. See Upgrade the Android Mobile Agent for step-by-step instructions on upgrading the Android SDK in your app. See Upgrade the Xamarin Agent for step-by-step instructions on upgrading the Xamarin Agent package in your app. Upgrade the IoT SDKs See Upgrade the IoT C++ SDK for step-by-step instructions. See Upgrade the IoT Java SDK for step-by-step instructions.   Additional Resources Instructions for upgrading other AppDynamics components are available in our general Release Upgrade Checklist ... View more

Release Upgrade Checklist for Database Agents   NOTE : The information in this article is not release-specific. You can reference it for any release   To make sure you complete all the tasks necessary for upgrading Database Agents after a release, we recommend following the upgrade checklist instructions below.    Table of Contents Prepare to upgrade your Database Agents Plan your Database Agent upgrade Next Steps Troubleshooting Additional Resources   Prepare to upgrade your Database Agents Review the Product Announcements and Alerts page for details on any intermediate versions between the current version of your instance and the version you are targeting. Review either of the following to confirm the compatibility of the various components of the AppDynamics environment: Knowledge Base article: How do I get started with upgrading my AppDynamics components for any release? , especially the component compatibility matrix Technical documentation: Agent and Controller Compatibility   Plan your Database Agent upgrade Review the Agent/Controller compatibility matrix for compatibility mappings between agents and Controller versions. Supported Controller versions v.4.3 v4.4 v4.5 v20.3 - future releases DB Agent versions 4.1 - 4.3 (1) 4.1 - 4.4 (1) 4.1 - 4.5 (1) 4.1 - 20.x (1) (2)                (1) Controller version supports through the most recent release of the Database Agent                   (2) DB Agent is only compatible up to its corresponding Controller version      Before upgrading, we recommend completing two backups: Backup your previous installation of the Controller. Backup the <db_agent_home> directory so you can revert to the previous installation if required. To maintain the same configuration information, you will also need the <db_agent_home>\conf\controller-info.xml file. If you are upgrading both the Controller and agents, upgrade the Controller before upgrading the agents. See Upgrade the Database Agent for important upgrade notes and step-by-step instructions.    Next Steps For each database, you will need to configure the Database Collectors according to the database in your environment.  See Add Database Collectors in the documentation.   Troubleshooting If your database isn’t reporting, check Database Visibility System Requirements in the documentation If you are having problems with your Collector, see Add Database Collectors .  If your agents don’t seem to be reporting, see the Troubleshooting Collector Problems section under Add Database Collectors .   Additional Resources Instructions for upgrading other AppDynamics components are available in our general How do I get started with upgrading AppDynamics components for any release? ... View more

Release Upgrade Checklist for Machine Agents   Note: The information in this article is   not   release-specific. You can reference it for any release.   To make sure you complete all the tasks necessary for upgrading Machine Agents after a release, we recommend following the upgrade checklist instructions below.   Table of Contents Prepare to upgrade your Machine Agents Plan your Machine Agent upgrade Troubleshooting Additional Resources   Prepare to upgrade your Machine Agents Review the  Product Announcements and Alerts page  for details on any  intermediate versions between the current version of your instance and the version you are targeting. Review either of the following to confirm the compatibility of the various components of the AppDynamics environment: Knowledge Base article: How do I get started with upgrading my AppDynamics components for any release?, especially the component compatibility matrix Technical Documentation: Agent and Controller Compatibility   Plan your Machine Agent upgrade   Review the Machine Agent and Controller version compatibility information below: Supported Controller Versions v4.3 v4.4 - 4.4.3 v4.5+ v20.3 - future release Machine Agent Versions 4.x - 4.3 4.4.1 - 20.x (1) 4.5 - 20.x (1) 4.4 - 20.x (1)(2) (1)   Controller version supports through the most recent released Agent version (2)  Controller does not support Agent version 4.1 Review the list of Machine Agent supported environments and versions to ensure compatibility between your Machine Agents and JDK. For example, 4.0.x is the latest version that can run on JDK 1.5 and higher and any version from 4.1.x and higher needs JDK 1.7 or higher . See Upgrading the Machine Agent for step-by-step instructions. Note: It’s a good practice to back up the <machine_agent_home> directory to a <machine_agent_home_BACKUP>  in case you need to revert to the previous installation.   Troubleshooting In the event of a failure, uninstall the new version and reinstall the previous version of the Machine Agent.   Additional Resources Instructions for upgrading other AppDynamics components are available in our general How do I get started with upgrading AppDynamics components for any release? ... View more

Release Upgrade Checklist for Java Agents   To make sure you complete all the tasks necessary for upgrading Java Agents after a release, we recommend following the upgrade checklist instructions below.    NOTE : The information in this article is not release-specific. You can reference it for any release   Table of Contents Prepare to upgrade your Java Agent  Plan your Java Agent upgrade  Shut down the JVM when uninstalling a Java Agent  Additional resources    Prepare to upgrade your Java Agent Review the Product Announcements and Alerts page for details on any intermediate versions between the current version of your instance and the version you are targeting. Review either of the following to confirm the compatibility of the various components of the AppDynamics environment: Knowledge Base article: How do I get started with upgrading my AppDynamics components for any release? , especially the component compatibility matrix Technical documentation: Agent and Controller Compatibility   Plan your Java Agent upgrade To ensure a successful correlation, upgrade agents on downstream tiers first, and then on upstream tiers. If you’re upgrading multiple agents in your monitored environment, upgrade the agents for the tiers on which business transactions are originated last. Starting in release 4.5, Java Agents are automatically backward-compatible with any 4.4.1+ Controller, so you can upgrade your agent while retaining your 4.4.1+ Controller. Note : If your Controller is older than 4.4.1, you must upgrade your Controller before upgrading your Java Agent. Supported Controller Versions v4.3 v4.4 v4.5 v20.3 - future releases Java 4.x - 4.3 4.4.1 - 20.x (1) 4.5 - 20.x (1) 4.4 - 20.x (1)(2) (1) Controller version supports through the most recent released Agent version (2) Controller version does not support Agent version 4.1   Review How does EUM component compatibility work? for compatibility mappings between agents and Controller versions See Upgrade the Java Agent for step-by-step instructions. See Install the AppDynamics Site Extension for Java for instructions for both minor and major releases.   Shut down the JVM when uninstalling Java Agents When uninstalling, it’s important to shut down the JVM that the Java Agent runs on, or the Java Agent will reappear in the UI. See Uninstall the Java Agent for the correct procedure.    Additional Resources Instructions for upgrading other AppDynamics components are available in our general release upgrade checklist,  How do I get started with upgrading AppDynamics components for any release? ... View more

A complete checklist for upgrading platform components   NOTE: The information in this article is not release-specific. You can reference it for any release. To make sure you complete all the tasks necessary for upgrading platform components after a release, we recommend following the upgrade checklist instructions below.    Table of Contents Prepare to upgrade your platform components Plan your platform component upgrade  Step 1: Upgrade the Enterprise Console Step 2: Upgrade the Events Service Single-node install or manual upgrade? Step 3: Upgrade the EUM Server Step 4: Back up the Controller Step 5: Upgrade the Controller with the Enterprise Console Troubleshooting Additional Resources   Prepare to upgrade your platform components Review the Product Announcements and Alerts page for details on any intermediate versions between the current version of your instance and the version you are targeting. Review either of the following to confirm the compatibility of the various components of the AppDynamics environment: Knowledge Base article: How do I get started with upgrading my AppDynamics components for any release? , especially the component compatibility matrix Technical documentation: Agent and Controller Compatibility   Plan your platform component  upgrade Before upgrading to a newer version of the platform, complete the tasks outlined in the Update Product Components documentation . To ensure all data is transferred properly, perform your upgrades in the specific recommended order for the components you’re using:   Step 1. Upgrade the Enterprise Console Review the Upgrade the Enterprise Console documentation first.   To determine the requirements, review the Controller system requirements and increase your hardware resources if necessary.   Step 2. Upgrade the Events Service Do I need a single node install or a manual upgrade? The Enterprise Console supports the installation of the Events Service on a Windows environment for a single node install . If you have several remote nodes, you will need to do a manual upgrade of the Events Service cluster and set the keys manually. For instructions on connecting to the Events Service, see the End-User Monitoring Connection Settings documentation .   Note: Even though th e Enterprise Console will set and sync the keys between the Controller and Events Service, we still recommend confirming that the keys were synced correctly: appdynamics.on.premise.event.service.key == ad.accountmanager.key.controller Note: If you're upgrading the Events Service using the Enterprise Console, you don't need to stop the Events Service.   Complete the Events Service upgrade Follow the Upgrade the Events Service documentation to complete the Events Service upgrade.   Step 3. Upgrade the EUM Server See Upgrade the EUM Server for instructions on upgrading an EUM Server.   Step 4. Back up the Controller Complete a full backup of the Controller. Reference Back up the Existing Controller for instructions.   Step 5. Upgrade the Controller with the Enterprise Console Final Upgrade Considerations Before completing the upgrade process, review the following and implement as appropriate:   Upgrading an HA Pair If you are upgrading an HA pair, we recommend upgrading via CLI using the Phased Upgrade Method (new in v4.5.6) . This allows you to retain the HA roles of the Controllers so that the primary and secondary roles do not switch after upgrade and you can check the status of your primary Controller before upgrading the secondary.    If you encounter any issues during or post-upgrade, you can roll back by promoting and failing over to the preserved, secondary Controller.    It is also possible to use GUI or the old CLI method to upgrade your HA pair, but we recommend the Phased Upgrade Method.   Upgrading from a small to an extra-large deployment You can directly upgrade from small/demo deployments to large/extra large deployments. See the Tuning for Large Profile Controller documentation for instructions on preparing a large deployment.   Be sure to check the Controller’s database.log Check the Controller&rs database.log for any errors during this process. You can find the log at <controller_home>/db/logs/database.log> . There should not be any InnoDB: Error lines in the log from the last startup. If any errors are found, contact AppDynamics Support before attempting the upgrade. Upgrading the Controller with a corrupt database may put the Controller in a bad state with a high recovery time.   Upgrade the Controller with the Enterprise Console Once you’ve completed preceding steps and considerations, refer to the Upgrade the Controller using the Enterprise Console  documentation to perform and complete the upgrade.   Troubleshooting In the event of a failure, follow the troubleshooting steps in the  Troubleshoot the Upgrade documentation.   In the event of a failure when upgrading a platform component, please contact AppDynamics Support .   Additional Resources How do I get started with upgrading AppDynamics components for any release? ... View more

Table of Contents Feature Enhancements Heads Up - What Else You Should Know BETA Programs Resolved Issues Get Started Ask a Question   In March, we released key enhancements and resolved issues, as well as recent Agent updates (if the Agent is not v4.5.8 it is noted below). Please check our Agent and Controller Compatibility documentation to see which Agents are backwards compatible.    What are the highlights I should know about? These release highlights will guide you through the newest features and capabilities. Notice in the grid below each feature enhancement identifies the most interested or impacted users.   Product Enhancement User and Performance Analyst Admin and Implementer Developer Platform Cognition Engine Powers Anomaly Detection and Automated Root Cause Analysis ✓ ✓ ✓ Database Monitoring Oracle Real Application Cluster (RAC) Auto-Discovery Enhancements ✓ ✓ ✓ Custom JDBC Connection Properties ✓ ✓ ✓ End User Monitoring Mobile Sessions API and UI Enhancements ✓   ✓ IoT Geo Widget Builder ✓   ✓ User Event Information for the Fetch API   ✓ ✓ Application Performance Monitoring PHP v7.3 Support ✓ ✓ ✓ Additional Java Framework Support ✓ ✓ ✓ .NET Class/Method Transaction Detection for .NET Agent for Linux ✓ ✓   ASP.NET Transaction Naming Configuration for .NET Agent for Linux ✓ ✓   Analytics Encrypt Sensitive Text in the Analytics Agent   ✓   Partnerships Multi-Buildpack Support for Pivotal Cloud Foundry   ✓ ✓ Extensions AppDynamics Extension for Linux Monitoring Upgrades ✓       Cognition Engine Powers Anomaly Detection and Automated Root Cause Analysis Anomaly Detection and Automated Root Cause Analysis are AI-powered features designed to reduce Mean Time To Resolution for application performance problems. Anomaly Detection automatically tells you if every Business Transaction in your application is performing normally. Automated Root Cause Analysis helps you quickly determine the root cause of problems revealed by Anomaly Detection. Read the full documentation for details. Available to SaaS customers only.   Oracle Real Application Cluster (RAC) Auto-Discovery Enhancements The Database Agent now supports additional ways of auto-discovering connectivity details for the member nodes of an RAC cluster, making it easier to deploy in the enterprise. Read the documentation for details.   Custom JDBC Connection Properties You can now add and edit custom JDBC connection properties on a per collector basis for relational databases. This allows AppDynamics Database Visibility to support custom configurations more easily (e.g., for authentication, networking, security and others). Read the documentation for details.   Mobile Sessions API and UI Enhancements Gain additional insight into your users' actions using the new SessionFrames API, supported in v50.1 of the iOS Agent. This enables you to use business-specific context to break down user workflows. We are working to expand this API to other Mobile Agents soon. The Mobile Sessions UI has also been simplified to make it easier to digest information. Read the documentation for details.   IOT Geo Widget Builder Visualize and measure the geo-based performance of your business' connected devices by building custom Geo widgets with the IoT Widget Builder. By presenting this data in a widget format, you’ll be able to isolate performance issues to a region and resolve them faster. Read the documentation for details.   User Event Information for the Fetch API Gain an added layer of visibility into your browser application performance with the userEventInfo object for Ajax calls made through the Fetch API. Read the documentation for details.   PHP v7.3 Support PHP Agent v4.5.8 adds support for the latest PHP version 7.3. This release brings PHP customers a set of minor language updates and a performance uplift measured at nearly 10% compared to PHP 7.2. With v4.5.8 of the AppDynamics PHP agent, you can take full advantage of these benefits without losing critical visibility into your PHP applications.   Additional Java Framework Support Java Agent v4.5.8 adds support for IBM BPM v8.6, enabling you to continue tracking the technical and business performance of your BPM processes as you upgrade to the latest version of IBM BPM. We’ve also added native support for auto-instrumenting applications built using the new WebFlux and WebClient components of version 5 of the Spring Framework, providing end-to-end visibility for the most modern generation of Spring-based web applications. The Java Agent now also provides out-of-the-box support for HTTP Business Transaction flows through Oracle OSB, extending AppDynamics’ end-to-end transaction visibility through this commonly deployed ESB. Read the documentation for details.   NET Class/Method Transaction Detection for .NET Agent for Linux .NET Agent for Linux v4.5.9 enables you to define .NET Class/Method (POCO) transaction detection in order to monitor .NET applications that perform repeatable task executions. This enables to collect performance telemetry from the .NET Core applications running background tasks. For example, you can collect the number of executions, response time and error rates for the code triggered by timers, events or messages. Read the full documentation for details.   ASP.NET Transaction Naming Configuration for .NET Agent for Linux With .NET Agent v4.5.9, you can also fine tune which ASP.NET transactions to exclude from monitoring or define your custom rules by splitting, grouping or excluding requests based on URL parameters or payload. This configuration is optional, but in certain situations will improve telemetry to better represent the health of individual transactions and match those to business requirements. Read the full documentation for details.   Encrypt Sensitive Text in the Analytics Agent Organizations with advanced security policies now have the ability to encrypt sensitive text, including credentials, with Analytics Agent v4.5.7. This allows for multi-layered security for passwords stored in the different properties. Read the documentation for details.   Multi-Buildpack Support for Pivotal Cloud Foundry Starting with v4.6.x of AppDynamics Application Performance Monitoring for PCF, the AppDynamics extension buildpack (appbuildpack) offers multi-buildpack support for .NET Core on Linux, .NET Core and .NET Framework on Windows (.NET HWC), Python, and Golang applications. This allows for a single unified workflow for instrumenting your applications regardless of your language or framework and helps you release new AppDynamics features faster. Read the full documentation for details.   AppDynamics Extension for Linux Monitoring Upgrades We've upgraded the extension to a new version of the Extension Commons Library and added a feature for filtering metrics. Read the extensions documentation for details on downloading the latest version of the extension.   Heads Up - What Else You Should Know Below are additional updates that you should be aware of regarding Controller compatibility and profile: In order to customize Business Transaction detection, customers using .NET Agent for Linux v4.5.9 will need to upgrade their Controllers to v4.5.2+. The agent will continue to work with Controllers v4.4.1+, but the customizable detection capabilities require v4.5.2+.  See Agent and Controller Compatibility You can deploy a medium-profile Controller v4.5.8 on AWS with an Aurora database. Aurora provides a highly reliable, high-performance, low-cost deployment option. See Controller System Requirements   See What’s Coming! Join a BETA today We’re currently running BETA programs and we’re looking for new participants: >>[Update] Network Visibility for Java Applications on Windows and AWS Lambda Monitoring (Serverless Computing) are no longer running beta programs.   Resolved Issues This month, we addressed multiple product issues in order to create an improved customer experience. A complete list of resolved issues is available in the full Release Notes. Below is a list of key issues that were resolved:   Languages Error during agent startup from Log4j2 conflict (JAVA-4908) Vulnerability reported in request library used by Node.js agent 4.5.10 (DLNATIVE-2325)   End User Monitoring Correct BT Correlation for Fetch API calls by changing the ADRUM headers from "isAjax: true" to "isAjax:true" (BRUM-4924) Excluding a page type from "Pages and AJAX Requests" excludes all other page types with the same page name (BRUM-4634) Synthetic Agent manipulates the DOM in a way that breaks websites (SYNTH-4126) Slow download of EUM metrics are causing EUM metrics to be dropped (EUMIOT‑1336)   App iQ Platform and On-Premises Platform NPE when loading ADD by bogus Id (METADATA-5774)   Get Started Download Essential Components (Agents, Enterprise Console, Controller (on-prem), Events Service, EUM Components) Download Additional Components (SDKs, Plugins, etc.) AppDynamics Upgrade Checklist For Any Release Product Announcements, Alerts, and Hot Fixes Extensions   Can’t find what you are looking for? Need more assistance? Ask a question in the Latest Release forum. ... View more