This topic covers release information for the AppDynamics App iQ Platform versions 4.5.x. In addition to the enhancements and resolved issues described here, the latest 4.5.x release includes enhancements and resolved issues included in certain limited-availability releases, as well as security fixes.
The first generally available 4.5.x release is 4.5.nnn, which incorporates fixes to pre-release issues in 4.5.nnn and 4.5.nnn.
The release notes are inclusive. All updates since 4.5.nnn are noted in the 4.5.x Release Notes. The Product Announcements and Alerts page lists versions, along with release dates, across product versions.
This documentation reflects AppDynamics Application Intelligence Platform version 4.5.x. Changes between minor versions are noted in the release notes and indicated in-place in the documentation where applicable.
AppDynamics App iQ Platform Notes
The following updates apply to the common components of the AppDynamics App iQ Platform, including changes to the cross-product elements of the Controller UI.
|Table of Content Zone|
- You can submit a request via a customer service ticket to purge your Controller, EUM, or Analytics account. The AppDynamics team can also perform piecemeal search and delete requests using internal REST APIs.
- Audit logging coverage has been made more comprehensive. It now includes the following:
- Failed logins
- Changes to configuration settings
- Personally Identifiable Information deletion
- Application deletion
- Audit log, report, and API details have been enhanced to include more information on what was updated.
- There is a UI for reporting of MDS audit logs.
Data Collection Dashboard
You can view the current state of all configuration parameters that may affect your security and privacy from a single dashboard view. These settings include retention settings, custom data collectors, IP-address retention in EUM, etc. See Data Collection Dashboard for more information.
This customizable statement is present in all areas of the AppDynamics UI where data collection can be configured.
- Authentication and authorization security enhancements have been made to the AppDynamics App iQ Platform in the form of scalable, securable, and admin configurable support:
- You can create and use API Clients to provide secure access to the Controller through REST API calls. These calls now use OAuth token-based authentication over basic authentication. See API Clients for more information.
- The SAML authentication can handle encrypted SAML responses from identity providers. You can enable SAML Encryption on Authentication Provider of Administration on your Controller.
- When creating usernames in SAML in Azure environments, the UserName attribute is used if it is passed along. The NameID attribute is not handled if it is passed back in Azure. If you relied on the legacy behavior of concatenating the first name and surname, then you can work around this enhancement by changing your Azure provider to return the concatenated names in the UserName attribute.
|Application names under Roles are not in alphabetical order|
|PLATUI-313||Application search under Roles is case sensitive|
|PLATUI-346||Application search under Roles displays blank screen after scrolling|
|PLATUI-736||Unable to save the custom role when the dashboard search box is selected|
|REPORTS-105||Dashboard Health List names in Hebrew are not displayed on Reports on Linux Controllers|
Reports are not generated properly – includes empty iframe
- For JMX functionality to work, set a Currently monitored statistic set to an option other than None in IBM WebSphere.
Application Performance Management Notes
|Table of Content Zone|
C/C++ Agent Enhancements
Go Agent Enhancements
.NET Agent Enhancements
.NET Core for Linux SDK
- .NET for Pivotal Cloud Foundry (PCF)
|DOTNET-2443||Automatic node naming is not working in Service Fabric cluster for .NET Core.|
|DOTNET-1351||Machine snapshots do not show CPU percentage and process when ProcessNameFormat is set to 2.|
|DOTNET-1319||Agent is not able to identify the ADO.NET exit for the System.Data.Common.DbDataAdapter class methods.|
Node.js Agent Enhancements
Java Agent Enhancements
- Added a node property jmx-query-timeout-limit to override ignoring JMX rules/attributes.
- The Java Agent supports transaction detection, naming, and data collector instrumentation for the IBM BPM product.
- The Java Agent supports for Correlation for Kafka.
- The Java Agent adds support for Eclipse Vert.x version 3.5.
- The Java Agent handles the Exit Point Identification of the Distributed Command Bus for Axon 3.x.
- The Java Agent now reports Business Transaction and Backend timings reflecting the black-box http response times for supported asynchronous entries and exits.
|JAVA-1368||BCI Exclude not properly excluding Lambda classes|
|JAVA-2123||RabbitMQ Message Properties get changed when correlation is enabled|
|JAVA-3080||Error in getting field marshaller for classes extending org.springframework.ws.client.core.WebServiceTemplate|
|JAVA-3086||Error creating custom JMX rules which are inside a composite data structure(array)|
|JAVA-3088||Agent holds error references when not connected to Controller|
|JAVA-3161||StackOverflowError in CallGraphBuilder.fixChildrenWaitBlockTime(CallElement e)|
|JAVA-3190||NPE thrown when trying to get Destination type (JMS) and disabling interceptor|
|JAVA-3214||AppAgent 4.4.x version does not start with JDK 1.9 as JRE runtime version|
|JAVA-3485||WebSpherePMI Domain MBeans are not supporting instance identifier customization|
|JAVA-3598||NPE Error with VERTX API version 3.3.0 and java agent 4.4.1|
|JAVA-3809||Correlation not working for ning http client|
|JAVA-3819||Memory leak by adding EUM http header in NettyHttpResponse|
|JAVA-3846||[PWC POV] MuleV38HTTPServerEntryInterceptor / MuleESB - EUM Correlation not working in 4.4.x agent|
- If you enable Kafka consumer entry points for the Java Agent, the flow map shows the data flow in reverse from the node to the Kafka cluster.
- Business transaction retention settings are not affected by the business.transaction.retention.period value in the Admin Console.
- For JMX functionality to work, set a Currently monitored statistic set to an option other than None in IBM WebSphere.
Database Visibility Notes
|Table of Content Zone|
End-User Monitoring Updates
|Table of Content Zone|
The new Code Issues Dashboard enables you to get trend and detailed information about caught non-fatal exceptions and instances of applications not responding (ANRs). The Android/iOS SDKs enable you to set the severity of caught non-fatal exceptions, so that you can filter code issues by severity in Code Issues Analyze.
The IoT REST API enables you to correlate business transactions between IoT applications and business apps. See Correlate Business Transactions for IoT Monitoring for more information.
|BRUM-3734||The Controller is not receiving metrics because of a time skew between the Controller and the EUM Service.|
|BRUM-3615||Child Ajax events are not reported because of missing parent page events.|
|BRUM-3571||When an EUM app's new metric limits are reached, no new metrics are created, and data for existing metrics are not recorded.|
|MRUM-3379||For some iOS ANRs, the wrong thread is marked as not responding.|
Browser Synthetic Monitoring
|SYNTH-3373||The start time is incorrect for synthetic sessions where the HAR doesn't have a base page.|
|SYNTH-2287||Some internal errors are being reported as timeouts.|
|EUMUI-1703||Mobile sessions are not loading for some users.|
|EUMUI-1574||Regular expressions the include ampersands aren't working.|
|EUMUI-1033||The map locations of US cities are incorrect when filtering by 'United States'.|
|EUMUI-616||When a user has been explicitly granted delete permission, deleting a job shows an error box, although the deletion works.|
|EUMUI-608||The screenshot timestamp for synthetic sessions should not be an available field.|
Infrastructure Visibility Notes
|Table of Content Zone|
Important Note about Changes in Dynamic Monitoring from Previous Releases
Starting in release 4.5, the default Dynamic Monitoring Mode (DMM) for all Standalone Machine Agents is KPI (collect Key Performance Indicator metrics only). This is true for the following metrics:
This change can affect any user-defined features created in previous releases that rely on Diagnostic or Advanced Diagnostic metrics. Examples include Health Rules, Dashboards, and scripts with metric API calls. AppDynamics strongly recommends that you disable these user-defined features or edit them to use KPI metrics instead. For more information about Dynamic Monitoring Mode, see:
Standalone Machine Agent Enhancements
- The Standalone Machine Agent is now supported on Windows Server 2016.
Server Visibility Enhancements
- This release supports monitoring of applications deployed in OpenShift v3.
- Dynamic Monitoring Mode enhancements:
- Dynamic Monitoring Mode (DMM) is now supported for all Docker Visibility metrics. See Dynamic Monitoring Mode and Docker Visibility.
TBD – Move this page over to the Cloud Space when 4.5 goes GA
- The Controller now has three different DMM defaults for all agents reporting to that Controller. Each setting applies to a different set of metrics.
- The default for all three settings is KPI, the lowest setting: collect Key Performance Indicator metrics only.
- AppDynamics recommends that you leave these global settings at their defaults and increase the DMM on individual servers or containers on an "as-needed" basis:
- When you need to troubleshoot a specific server or container, increase the DMM on that object only.
- When you finish troubleshooting that object, set the DMM on that object back to KPI.
- This workflow is described in detail in TBD. Link to page in Cloud Space when 4.5 goes GA
- When a container monitored by a Java App Agent shuts down and restarts, any overridden DMM specified for the shut-down container is lost. The DMM for the restarted container automatically resets to the global default specified by
- Docker Visibility enhancements:
- The Container Details window includes a new Network tab. This tab is available only if the Dynamic Monitoring Mode for the container is Diagnostic or Advanced Diagnostic. This tab shows:
- Network KB – Total traffic (KB)
- Network Rate – Rate of traffic (KB/s)
- Network Errors
- Packet Drops – Rate of incoming/outgoing packets dropped by the network. A high rate of packet drops might indicate congestion or other network issues.
- Errors – Rate of incoming/outgoing packets with errors.
- The following new metrics are available in the Metric Browser:
CPU %Busy Scaled – If the -cpus=<value> option is set in the container, this metric measures the scaled value of the CPUs property. If this value is not set, this metric measures the scaled value of the Logical CPUs property.
You must enable CPU Scaling on the Controller to collect this metric. See Docker Container Metrics.
- Network metrics
- Incoming KB
- Outgoing KB
- Incoming KB/sec
- Outgoing KB/sec
- Incoming packets
- Outgoing packets
- Incoming packets dropped
- Outgoing packets dropped
- Disks – these metrics might not be available on all platforms:
- Average IO Utilization (%)
- Queue size
Network Visibility Enhancements
- Transaction Snapshots now support network analysis and troubleshooting workflows.
In the Snapshot Overview, you can right-click on a flow and choose View Network Metrics. The resulting dashboard shows the Performance Impacting Events (top-left chart) for that flow and possible correlating factors for these events. See KPI Metrics in Right-Click Dashboards.
- The Network Dashboard can now show Cross Application Flows.
- This release includes a new default Health Rule for troubleshooting Network Agents:
Network-Host: Packet drops too high
This rule triggers an alert when packets get dropped between a Network Agent and the host interface. A high rate of packet drops on the host can result in inaccurate metrics.
- TBD The Connection Explorer, Mapping Wizard, and Connections tab (in network link popups) display the Fully-Qualified Domain Names for remote services and Load Balancers by default. This makes it easier to identify the external services used by your monitored applications.
- Usability enhancements:
- Right-click dashboard charts now support both linear and logarithmic scales. Click in the top-right of each chart to change the scale to best highlight metric spikes and variations.
- The Transaction Snapshot window makes it easier to analyze multiple network links used by the same application flow. Open a snapshot; right-click on a multi-link flow; choose View Network Metrics; the resulting dashboard includes a menu (top left) for switching between link views.
- You can open the Unmapped Connection Wizard directly from a Tier Dashboard if that tier has any unmapped connections.
Controller UI stops working intermittently due to threadpool saturation
Machine Agent cannot collect OS info on Red Hat Extended Linux 7.4
Service Availability Event should display events related to that service only
Node Dashboard > Server tab should show the same information as Server Dashboard
Enabling sim.machines.reuse.enabled sometimes results in thread pool saturation and prevents Standalone Machine Agent from communicating with Controller
Server page shows data for 13 hours, not selected time range of 1 day (observed on SaaS Controller)
In some cases, Machine Agent stops collecting process metrics even after machine/global max thresholds are increased
Machine agent is not reporting processes, network and volumes when running in Container
Disk usage percentage on Linux needs to reflect "df -P -m" command
Machine Agent not reporting metrics on docker when process command contains space
Hierarchy name check is case-sensitive, which prevents Standalone Machine Agent registration
Number of CPUs reported by Standalone Machine Agent is sometimes in accurate on Windows
Cannot update RPM Standalone Machine Agent due to packaging error
License > Account Usage does not show Service Availability license usage
Standalone Machine Agent Known Issues
- Reset Machine Agent action on the AppDynamics Agents window is not available for 4.4 and higher Machine Agents.
- (Windows only) The JavaHardwareMonitor extension and the ServerMonitoring extension (introduced in 4.2) assign network names differently. If you have any health rules based on JavaHardwareMonitor names, and you want to use these rules with the ServerMonitoring extension, you will need to update the names that these rules are based on.
Server Visibility Known Issues
- If a metric name contains colons or pipe characters (
|), the Metric Browser interprets the name as hierarchically separated. These characters could appear in a process name, a disk or partition name, a mount point, or a network interface name. METADATA-1373
- If the machine that a Machine Agent is monitoring goes to sleep, monitored processes might be duplicated on the Controller. Because the process has a new start time, the Controller interprets it a new process. When the configured process count is reached, the Controller marks the duplicated processes as terminated and purges them.
- (Windows only) You must have .NET Compatibilty Mode enabled for Server Visibility to work correctly on a server with a .NET APM agent installed.
- Server Visibility does not support the following on Solaris:
- Solaris zones
- Unicode characters
- The following Health Rule is disabled by default in this release:
Disk Usage is too high on at least one partition.
This wildcard health rule can result in high resource consumption and health rule evaluation times on the Controller. If this rule is critical for your environment, the recommended practice is to create your own custom Health Rules and apply specific rules for specific volumes on specific servers. For more information, see the following Support Advisory: https://community.appdynamics.com/t5/FEZ-Knowledge-Base/Server-Visibility-Support-Advisory/ta-p/22408
Docker Visibility Known Issues
- The Standalone Machine Agent running inside the container sometimes reports a few extra volumes for the host machine. This can result in a higher total volume for the aggregate volume metrics.
- There might be gaps in the container network I/O metrics. This happens because the Docker API resets the accumulated network I/O metric data for every 4.2 GB of data sent or received. When the data is reset, the Standalone Machine Agent calculates negative I/O values and does not report a data point for that time window.
- If the agent started monitoring the current container after the beginning of the selected time range in the Controller, the Controller might show metric data prior to the container start time. This metric data will include metrics from a previously monitored container. This behavior occurs when the Controller flag "sim.machines.reuse.enabled" is enabled.
- If the agent started monitoring the current container before the beginning of the selected time range in the Controller, the data is correct for the current container.
- If a container stops running while it is being monitored, the Tiers & Nodes Dashboard > Server tab will show data for the stopped container rather than for the underlying server.
- In some cases, container monitoring is suspended when some containers that are currently being monitored are stopped. This issue has been observed on Docker API version 1.24. The suggested workarounds, in this case, are to
- Restart the Standalone Machine Agent (Docker Visibility will start monitoring the containers), or
- Upgrade to Docker CC/EE v17.03 or Docker Engine v1.13.
- cgroup data collection is not supported in Kubernetes deployments. If the Standalone Machine Agent is monitoring containers deployed as Kubernetes pods, do not enable the cgroup Enabled setting.
- The Container Details > Network tab does not display IP or MAC addresses for monitored containers.
Network Visibility Known Issues
- In the Application Flow Map, you can click on a flow and view a Network tab in the flow popup. The Network KPIs shown (Latency, PIE, Errors) are based only on the exit traffic from the initiating service on that flow. To view Network KPIs for all monitored traffic to and from that service, go to the Network Dashboard and open the popup for a network link.
- In some cases, the KPIs for a tier or link might be different in the Network tab vs. the Network Flow Map. The popup window shows the latest data; the Flow Map updates data every two minutes. Any discrepancy between KPI values is due to this difference in reporting times.
- If you open the Network Flow Map for an individual node, the KPI metrics for node-to-load-balancer and node-to-tcp-endpoint links show network KPIs for all nodes in the parent tier (instead of KPIs for the individual node only). To view KPIs for the individual node, open the link popup and look at the Connection KPIs.
AppDynamics Business iQ Notes
|Table of Content Zone|
Enhancements and Updates
- User experience of running ADQL queries has been improved:
- ADQL UI now has the Save button. Use the button to save new searches. (ANALYTICS-648)
- The following fields are added to the ADQL UI for
mobile_snapshots: Platform,Request Content Length,Response Content Length, Country, Region, Background. (ANALYTICS-4708)
- The Analytics Search page shows advanced statistics, such as standard deviation, median, minimum, and maximum, for numeric fields. Click the field to view associated statistics. (ANALYTICS-691)
- The following clauses are added to ADQL: HAVING and SINCE ..UNTIL. (ANALYTICS-3263)
- The analytics functions, such as avg, max, and min, now support the datetime format. (ANALYTICS-1200)
- Business iQ now supports exporting data to a file in CSV format for external use. Use the Search page to do so. (ANALYTICS-3397)
- Type conversion for MIDC and HTTP Data Collectors are supported in Transaction Analytics. The MIDC and HTTP Data Collectors allow you to convert transaction analytics data into suitable data types. The supported data types are String, Boolean, and Number. (ANALYTICS-3285)
- ADQL now supports the TotalResults() function. It returns the total count of events. TotalResults() does not accept a field. (ANALYTICS-3446)
- The IS NOT NULL operator is now supported in Basic mode (Drag and Drop Search), including Funnel filters. The operator returns all the events with values either true or false. (ANALYTICS-2870)
- The numeric widget now has a comparison indicator. Use the Compare to and Trailing By options in the Widget Properties to indicate an offset. The Compare to option by default is set to None. Select Prev.period from the Compare to drop-down and specify the relative time in minutes, hours, or days using the Trailing By option. The current aggregate value is compared against the period you specify and the difference is displayed on the widget. (ANALYTICS-3388)
- All the widgets now support user input for percentile aggregations. The supported values are integers between 1 and 99 inclusive. In Basic mode, drag a numeric field to the canvas, and use the drop-down next to the field name to specify a value for percentile aggregation. (ANALYTICS-1237)
- The logarithmic scale is now supported in Analytics widgets for the Time Series charts. Use the Logarithmic Y Axis checkbox in the Widget Properties to apply the logarithmic scale to a selected field. (ANALYTICS-695)
- Ability to hide legends is now supported in widgets. In the Widget Properties, select None from the Legend drop-down to hide legends. (ANALYTICS-4875)
- Analytics Widget Properties now have an option to make the widget's background transparent. (ANALYTICS-3364)
- Agent ID and Client GUID are exposed in the Data tab and can be used to build custom widgets. (ANALYTICS-4119)
- Close Widget Builder option is provided to support canceling widget editing. With this option, unwanted changes to a widget can be dropped while editing, and revert to the previous version by closing the widget. (ANALYTICS-3311)
- The extra whitespace on the histogram has been removed. The histogram now looks condensed on the dashboard. (ANALYTICS-3896)
- The metrics created using the Numeric widget now displays the exact value returned by the search. In Widget Properties, select Exact from the Format drop-down to view the exact number. Other options available are Automatic, Thousands(k), and Millions(m). The default is Millions(m). (ANALYTICS-7044)
- Business Journeys authoring has been enhanced with the following features: (ANALYTICS-3099)
- Business Outcomes has been renamed as Business Journeys. (ANALYTICS-4068)
- A Search button has been added to the Business Journey page. Analytics Search button provides one-click access to the underlying events. Selecting an enabled Business Journey and clicking Analytics Search takes you directly to the Searches page in Basic mode. Analytics Search button is unavailable for definitions in Draft and Valid Draft states. (ANALYTICS-3928)
- Float type is supported for filtering Business Journey events. (ANALYTICS-6983)
- Custom event types are supported. (ANALYTICS-4456)
- Custom event data can be used to create Business Journeys. (ANALYTICS-3904)
- All the fields that are part of filters and optional filters are automatically collected. (ANALYTICS-349)
- When defining Business Journeys, you can now delete the same field from one milestone and add it to a different milestone in the same Save action. (ANALYTICS-3149)
- At the Business Journey level, a field named completed has been added to track the status of the workflow using the boolean values. True represents a completed Business Journey, whereas False indicates that the journey is in progress or is incomplete. Use the Search widget or an ADQL query for the desired Business Journey with the query string completed to view the status of the associated events. (ANALYTICS-2866)
As you create milestones, a flow map detailing the business workflow is now displayed in the Business Journey page. Additionally, selecting a Business Journey opens it in a new window with the flow map enabled. This behavior is controlled by the analytics.business.outcomes.flowmap.enabled property in the Controller Settings. (ANALYTICS-3727)
- Enabling and disabling Business metrics are supported. Use the Enable and Disable button on the toolbar to do so. (ANALYTICS-1219)
- Double-clicking a Business metric opens it in the Metric Browser. (ANALYTICS-3268)
- Business Metrics list is now searchable. (ANALYTICS-3267)
- Event Type column is added to the Metrics page. (ANALYTICS-4712)
- Metric on ratios is supported. (ANALYTICS-736)
Experience Level Management (XLM)
- Visibility into XLM data is improved in the following ways:
- You can now create XLM dashboards and reports in the time zone of your choice.
- You can now export reports. The exported report is in CSV format, and contains however many reporting periods you choose.
- You can now specify files to exclude from ingestion, by defining a glob pattern of file paths to blacklist.
- This is especially useful when:
- You define a glob pattern to include all the files that you want to ingest
- You define an additional glob pattern to exclude (blacklist) files that satisfy the first glob pattern, but that you do not want to ingest
Upgrading the Analytics Agent
Field Names for Data Collectors
Enabling Transaction Analytics
|ANALYTICS-4608||Analytics Agent stops ingesting logs when log file rolls over|
|Users assigned Analytics Administrator permissions through a Group cannot see searches saved by other users|
|ANALYTICS-7554||Duration settings for XLM synthetic sessions are in seconds, but should be in milliseconds|
AppDynamics On-Premises Platform Notes
The following notes describe updates to the AppDynamics on-premises platform, including the Controller, Events Service, and EUM Server components.
|Table of Content Zone|
There is support for major-version upgrades for the Enterprise Console application. You can select which version you would like to upgrade to.
The Enterprise Console installer now uses version 6 of i4j. This resolves issues with warnings seen when installing on console mode.
The JRE of the Controller and Events Service has been upgraded to version 8u162.
You can now upload your license using the Enterprise Console UI.
When adding the Enterprise Console host machine, you should stop using the alias, 'platformadmin', and instead start using the following:
- On the CLI, you should use 'localhost', the loopback address '127.0.0.1', or the machine's actual hostname.
- From the UI, you should use the Add Enterprise Console Host button, which will automatically populate the text field with the hostname of the Enterprise Console machine.
- You can edit credentials from Custom Installation.
- You can download logs for a failed job from the Enterprise Console Jobs page.
- You can manage your Controller SSL certificate on the Enterprise Console UI under Configurations.
The Enterprise Console CLI commands now consistently use hyphens (-) instead of underscores (_).
The Enterprise Console supports up to 20 platforms at a time by default. You can configure this setting in the PlatformAdminApplication.yml file.
|ECONSOLE-1529||Windows Controller installation fails when special characters are used in controller admin password|
|ECONSOLE-1923||Enterprise Console UI does not show where to upgrade an existing Controller|
|ECONSOLE-1924||Enterprise Console upgrade procedure shows Install instead of Upgrade at the bottom|
|ECONSOLE-1951||Service name is not displayed in the error message when the Windows service registration fails|
|ECONSOLE-1978||Enterprise Console startup script should unset CDPATH|
|ECONSOLE-1992||Enterprise Console does not back up configuration files when any configuration is updated|
|ECONSOLE-2068||Internal app agent does not report to internal monitoring Controller automatically after Controller installation on Windows|
|ECONSOLE-2087||Enterprise Console should check available disk space before taking controller backup|
|ECONSOLE-2563||Verify SSH connection fails due to incorrect SSH setup|
|ECONSOLE-2608||Upgrading MySQL task does not update the database version correctly if the job fails halfway|
|ECONSOLE-2656||Enterprise Console fails on SuSE|
Enable edit of platform path within Enterprise Console UI
|ECONSOLE-2712||orcha-modules.log contains no dates|
|ECONSOLE-2796||Misleading Enterprise Console error message in platform-admin-server.log - attempted to reach unknown host|
|ECONSOLE-2806||db/lib backup does not cope well with Linux symbolic links|
|ECONSOLE-2851||Add current Linux effective user name to rsync/ssh UI error messages|
|ECONSOLE-2936||Intermittent HA primary Glassfish availability leads to two active controllers running|
|ECONSOLE-2938||Glassfish server.log file size reduced by 60%|
|ECONSOLE-3220||Secondary MySQL does not start due to space ID collisions|
|ECONSOLE-3238||Failover Job does not trigger|
Controller stop operation fails when service is in STOP_PENDING
|METADATA-1843||User login exception when using old password format|
|METADATA-2198||Description of audit.log.file.size property in admin.jsp does not mention units|
|METADATA-3606||Controller startup failure due to login audit failure in 4.4.1|
|METADATA-4242||Upgrade fails if dropping mds database fails in execute setup.xml ant tasks|
Deprecation and End of Life (EOL) Notices