AppDynamics helps to ensure that the software applications your business depends on always perform as you expect they should.
AppDynamics Pro 4.2 brings new features to enhance your experience and add clarity into the performance of the applications, servers, databases, and networks of your environment.
This release adds support for new languages, frameworks and components, while enhancing your experience to help you deal with the complexity of distributed, heterogeneous application environments. This release also includes several new products to help you monitor more and delve deeper.
This page describes selected highlights of this release. For more information about this release, see the Release Notes.
Watch the video:
Thread Contention Detection (Version 4.2.5)
The Controller now displays information about thread contention as it relates to business transactions or service endpoints, and it can help you discover the cause of the contested resources and help you resolve the issue.
In the Transaction Flow Map for a transaction snapshot, the Potential Issues panel displays potential Thread Contention issues:
Selecting the thread contention item and drilling down into the call graph displays additional detail about the Wait Time, Block Time, and affected node. It also specifies the time spent in each thread and the state of the thread.
You can view additional information in the Thread Contention details pane for each thread instance:
This pane displays the name of the method holding a lock on the blocking object, the name of the object that the blocked thread is waiting to access, the amount of time waiting to access the object, and the line number in the blocked method where the blocking object is being accessed.
Thread contention information is also available for service endpoints.
For more information, see Thread Contention.
AppDynamics presents the industry's first application-centric server monitoring. Server Monitoring uses the Standalone Machine Agent to provide extended operating system metrics and Service Availability Monitoring. Server Monitoring includes additional views in the Controller UI that enable you to quickly see underlying operating system and server issues impacting your application performance. This means you can rapidly troubleshoot underlying server and operating system performance problems that are impacting your applications.
Some of the most notable features of Server Monitoring include:
- Key performance metrics for all your servers on a single window.
- Key performance metrics for the selected server, including the top 10 consumers of CPU and memory.
- Performance metrics for disks, partitions, and volumes for the selected server.
- Network performance metrics for network interfaces on the selected server.
- Configurable set of performance metrics for processes.
Browser Synthetic Monitoring for SaaS
AppDynamics' End User Monitoring is enhanced with Browser Synthetic Monitoring for AppDynamics Pro SaaS implementations. Using Browser Synthetic Monitoring you can gain deeper diagnostic data by automating the testing of your Browser applications from different browsers in North and South America, Europe, Asia, and Oceania.
Synthetic Monitoring provides:
- Flexible job schedules and timing windows, where you can choose to perform your web tests at any time interval you require to maximize cost effectiveness.
- Cloud-based distributed agents whose capacity can be increased or decreased easily.
- Auto re-test on errors so you don't have to wait for the next regularly scheduled job to retest, reducing the number of unnecessary alerts.
- Dashboards showing metrics such as availability trends, average session duration, session duration distributions, and number of times the test was run.
- Scripting based on the Selenium scripting language.
- Snapshots of every synthetic transaction.
- Full waterfall detail on every page, exposing the details of every browser event.
Application Performance Monitoring for C/C++ Applications
The new AppDynamics Agent SDK for C/C++ enables instrumentation of your C and C++ applications. You can view application flow maps and key performance metrics for business transactions, backends and exit points using the AppDynamics agent.
Sessions for SaaS
Our End User Monitoring offerings on AppDynamics Pro SaaS implementations have been enhanced to provide you with session information to give deeper visibility into your browser and mobile users' journey through the application. For example, you can now see what pages or screens your browser and mobile users are visiting, and in what sequence. This allows you to more quickly troubleshoot when problems occur in the context of the user's behavior.
Features of new session-based monitoring include:
- Record every web and mobile session to see how many pages or screens your users go through as they interact with your web or mobile applications.
- Drill down into session details to see how long the session lasted, which pages the user interacted with during the session and the length of time the user viewed that page and how long the server took to process the user requests on each page.
- Drill down further to see the details of each page in a session and every mobile action in a session. For mobile, crash details per session are also available.
AppDynamics Query Language
AppDynamics Query Language (ADQL) is a SQL-like query language for searching through your data available in Application Analytics including transactions, logs, browser records, mobile snapshots and analytics custom events. ADQL auto-complete displays a list of event types, functions, and fields available to use in your searches based on the stage of your search.
MongoDB Database Support
Database Monitoring now offers support for the MongoDB database platform, allowing you to Monitor MongoDB databases with query details and cluster and node level metrics.
The 4.2 release of the Java and .NET agents provides out of the box detection for MongoDB backends. If a Database Monitoring Collector has already been created for a database with that same host name, port number, and database type, then that database is automatically mapped to the corresponding Database Monitoring Collector.