Skip to end of metadata
Go to start of metadata

This page lists the resolved issues for the agents, the Controller (on-premises or SaaS), and the on-premises platform in the 21.2 release. 

When artifacts are updated, they are listed with their new version numbers in the tables below. Version numbers are also shown in the AppDynamics Downloads Portal.

You can sort the table of resolved issues by key, version, and product, or use the search field to find resolved issues. The most recent releases appear at the top of the page.

Agent Resolved Issues

No results found.

KeyProductSummaryVersion
ANALYTICS-13226Java AgentEnabling recommended data collection intermittently affects Transaction Analytics reporting21.2.0
BRUM-6539JavaScript AgentReferenceError: hideCookieBanner is not defined when page is injected with adrum-latest.js21.2.0
BRUM-6552JavaScript AgentExtra value at the end of the app URL set by the ADRUM cookie21.2.0
BRUM-6553JavaScript AgentJavaScript statements inside setTimeout and setInterval runs in local scope when adrum is enabled21.2.0
CDM-7033iOS AgentiOS Agent disables SwiftUI previews21.2.0
CDM-7175Android AgentEvents are stored on EventBus even when agent is not initialized21.2.0
DBMON-7552Database AgentThe Database Agent sends the health rule data of a MongoDB replica node even after the node is stopped21.2.0
DBMON-7568Database AgentThe Database Agent log file includes the error, invalid USERENV parameter, for an Oracle collector21.2.0
DBMON-7739Database AgentThe custom metrics value drops to zero intermittently21.2.0
DBMON-7654Database AgentThe Oracle collector log displays an error when Sysmetrics query is used21.2.0
DBMON-7745Database AgentThe Explain another query: field under Execution Plan displays an error without any details for MariaDB21.2.0
JAVA-9093Java Agent

The User Experience value based on the set threshold limit is incorrect only for those records that do not have a matching transaction snapshot on the APM

21.2.0
JAVA-9037Java Agent

Upgrading the Java Agent to 20.11 displays an exception Error instantiating DispatcherServletInterceptor in the logs

21.2.0
PYTHON-498Python AgentJava proxy caches stale agent data21.2.0

Controller (SaaS/On-Premises) Resolved Issues

No results found.

KeyProductSummaryVersion
ALERT-7111Alert & RespondGarbled characters appear in email template instead of cyrillic string21.2.0
ALERT-7786Alert & Respond

Health rules not available in cache after Controller upgrade

21.2.0
AMCSEV-1260App Monitoring Cloud ServicesTiers Page does not show node details for the nodes after the 10th registered node21.2.0
ANALYTICS-12846Application AnalyticsAnalytics data table does not display the correct value for fields of the originating tier21.2.0
ANALYTICS-12938Application AnalyticsFunnel Dashboard link causes an Access to the specified resource has been forbidden error21.2.0
ANALYTICS-13089UI CloudIncorrect Browser Sessions/Mobile Sessions details in the Analytics Home page21.1.1
ANALYTICS-13090Application AnalyticsNode.js Agent does not receive the Analytics HTTP configuration21.2.0
ANALYTICS-13161Application AnalyticsAnalytics Home page displays inconsistent EUM charts21.2.0
ANALYTICS-13185Application AnalyticsRenamed fields/expressions are not reflected in the Analytics Pie Widget21.2.0
ANALYTICS-13205Application Analytics

From the Dashboard, double-clicking "business journey" transactions directs user to Overview page instead of Details dialog

21.2.0
ANALYTICS-13219Application Analytics

When changing the date format in My Preferences to "DD/MM/YY" and then opening a transaction snapshot in Analytics the error TRS has illegal timeRange is displayed

21.2.0
ANLYTCS_ES-3474Events Service

Some logically incorrect ADQL is validated

21.2.0
BRUM-6410Browser RUMReview of health rules violations from User Experience applications redirects to health rules for Application Performance21.2.0
DBMON-7131Database VisibilityAn Incorrect Database Agent version is displayed in the Database Agents setting after upgrading the agent and starting the new agent with the same name21.2.0
DBMON-7222Database Visibility

When configuring Monitoring Operating System for an AWS RDS collector, the required region is not displayed in the list.

Now, the required regions are included and some unnecessary regions are removed from the list.

21.2.0
DBMON-7302Database VisibilityDisk Usage within the database Queries displays an incorrect error message for the PostgreSQL database21.2.0
DBMON-7308Database VisibilityThe Live view session list displays all the active sessions when the View filter is set to All Sessions, but active sessions are not displayed when the filter is set to All Active21.2.0
DBMON-7354Database VisibilityThe Invalid DB error is displayed when saving an action suppression on one of the nodes of the database cluster21.2.0
DBMON-7373Database VisibilityA blank window is displayed when you click Drill Down for a database on the Transactions snapshot21.2.0
DBMON-7517Database VisibilityInconsistent Custom Metric permissions21.2.0
DBMON-7535Database VisibilityThe Exclude Schemas option gets checked after upgrading from old Controller to new Controller21.2.0
DBMON-7549Database VisibilityDuplicate IO Metric entries are displayed for Microsoft SQL Server on the Health Rule configuration page21.2.0
DBMON-7604Database VisibilityCustom Metric not displayed in Custom Metrics tab even though data is displayed in Metric Browser21.2.0
DIAGPLAT-1080APMSearching for snapshots yields inaccurate results for Standard Time Range from Transaction Snapshot21.2.0

SVCMON-1303

APMNPE in BtServiceImpl#registerDeleteMdsBtEntityTransactionListener does not allow purge of applications and Business Transactions21.2.0
USERIMPACT-714Experience Journey MapBad Link when clicking View All Applications in Experience Journey Map21.2.0

On-Premises Platform Resolved Issues

No results found.

KeyProductSummaryVersion
ECONSOLE-6395Enterprise ConsoleThe Controller monitoring setting in the AppServer configuration is fixed21.2.0

Known Issues

There are no known issues in the 21.2 release as of yet.



  • No labels