Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

On this page:

Your Rating:
Results:
1 Star2 Star3 Star4 Star5 Star
5 rates
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. 

Enhancements

Audit Logging

  • Audit log, report, and API details have been enhanced.
  • Audit logging coverage has been made more comprehensive.
  • 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.

Modal Interstitial Page

  • You can provide a customizable privacy statement to your users who are configuring parts of the AppDynamics products that they have regulatory, legal, and customer-defined policies that must be followed regarding data collection. This feature is present in all places of the AppDynamics App IQ Platform UI where data collection can be configured.

Custom Dashboard

Universal Agent 

User Management

  • Authentication and authorization security enhancements have been made to the AppDynamics App iQ Platform in the form of scalable, securable, and admin configurable support:
    • 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 workaround this enhancement by changing your Azure provider to return the concatenated names in the UserName attribute.

License Management

Resolved Issues

 

KeySummary
  
  

Known Issues

 Universal Agent

  • To use the Universal Agent to deploy the Analytics Agent on Linux, you must use machine-agent mode. Standalone mode is not supported for this use case.

  • Using the auto-Java feature for deployment of the Java Agent with the Universal Agent is not supported on Windows 2008 SP2 32-bit and 64-bit.
  • To install the .NET Agent with the Universal Agent use a local repository for the .NET Agent distribution file. Downloading the .NET Agent from the Controller is not supported.

IBM WebSphere

  • For JMX functionality to work, set a Currently monitored statistic set to an option other than None in IBM WebSphere.

Application Performance Management Notes

 

Enhancements

Controller Enhancements

  • You can now drill down into federation applications. This allows you to display incoming calls from the upstream federated application.

C/C++ Agent Enhancements

Go Agent Enhancements

  •  

Java Agent Enhancements

  • The Java Agent adds support for Eclipse Vert.x version 3.5.

.NET Agent Enhancements

  •  

Node.js Agent Enhancements

Upgrade Notes

  •  

Resolved Issues

KeySummary
  
  

Known Issues

  • 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.
  • Inactive nodes do not get marked as historical despite appdynamics.jvm.shutdown.mark.node.as.historical being set to true.
  • Business transaction retention settings are not affected by the business.transaction.retention.period value in the Admin Console. (APMPLAT-6307)

Database Visibility Notes

 

Enhancements

Resolved Issues

 

KeySummary
  


End-User Monitoring Updates

 

Enhancements

Browser RUM

  • Browser Analyze enables you to viewtheend user response time as an aggregate of time in different components, such as the frontend, backend, network, CDN,andthird party content. Understanding how much time is beingspentin the different components enables you to pinpoint issues more quickly and also suggests the party responsible for an issue. For example, if you see that too much time is being spent on the backend, you can contact your backend engineers to find and correct the issue.

Mobile RUM 

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

  • Mobile RUM now provides monitoring support for Cordova-based applications and for WebViews running in native iOS and Android applications. For iOS and Android native applications, the iOS and Android Agents inject the JavaScript Agent into Android WebViews and iOS UIWebViews to enable monitor and collect metrics from the the WebViews. For Cordova-based applications, you install the AppDynamics Cordova plugin.

Browser Synthetic Monitoring

  • The Synthetic Jobs page shows historical data and trends for the availability and status of synthetic jobs.

IoT Monitoring

The IoT REST API enables you to correlate IoT applications with TBD (business apps?). See Instrument Applications with the IoT REST APIs and Correlate Business Transactions for IoT Monitoring for more information. (TBD: the former is for how to send the headers, and the latter page shows how to configure the Controller to correlate BTs.)

Resolved Issues

Browser RUM 

ComponentSummary
  

Mobile RUM

ComponentSummary
  

Browser Synthetic Monitoring

ComponentSummary
  
  

EUM UI

ComponentSummary
  
  

Infrastructure Visibility Notes

Server Visibility

Enhancements

  • This release supports monitoring of applications deployed in OpenShift v3.

Resolved Issues

 

Key
Summary
  

 

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.    
  • The Network Dashboard displays the FQDNs for remote services and Load Balancers by default. This makes it easier to identify the external services used by your monitored applications.
  • The Network Dashboard uses a new visual convention to represent TCP Endpoints.

    TCP Endpoint in 4.4
    TCP Endpoint in 4.5

Resolved Issues

Key
Summary
  

Standalone Machine Agent

Enhancements

  • The Standalone Machine Agent can now collect metrics for remote volumes.

 

Resolved Issues

 

Key
Summary
  

 

Known Issues

Server Visibility Known Issues

  • If a metric name contains colons or pipe characters (: or |), 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.
  • A machine agent enabled for the 4.1 Server Monitoring Beta will not work with a 4.4 Controller. To continue using Server Visibility (previously Server Monitoring), upgrade both the machine agent and the Controller.
  • 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.

 

Standalone Machine Agent Known Issues

  • Reset Machine Agent action on the AppDynamics Agents window is not available for 4.4 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.

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. 

 

Application Analytics Notes

Enhancements and Updates

Log Analytics

 

Funnel Widgets

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)

Business Journeys

 

Experience Level Management

 

Upgrade Notes

Upgrading the Analytics Agent

 

Field Names for Data Collectors

 

Enabling Transaction Analytics


Related Background

 

Resolved Issues

 

KeySummary
  
  

Known Issues


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. 

Enhancements

Enterprise Console

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

Controller

EUM Server

Events Service

Upgrade Notes

Resolved Issues

 

KeySummary
  
  

Known Issues

Deprecation and End of Life (EOL) Notices

  • The AppDynamics Java Agent will no longer support monitoring Java applications running in the Java Development Kit 5. See Desupport Notice: Java Development Kit 5.
  • Mobile RUM: Dynamic Info Points are no longer available for Android apps.

  • End-User Monitoring: The option View Dark Mode has been removed from the Geo Dashboard.

  • Server Visibility (formerly Server Monitoring): The "Disk Usage is too high on at least one partition" health rule is now disabled. See Support Advisory: "Disk Usage is Too High" Health Rule is Disabled in Release 4.3 and Higher.
  • The Controller UI is no longer supported on IE 9. IE users are advised to use IE 10+ versions when using the Controller UI.
  • The Controller Package Installer is no longer supported. The Enterprise Console application supports most of your platform deployment needs, including installing a Controller and Events Service.

 

  • No labels