On this page:
Welcome to version 4.3 of the AppDynamics App iQ Platform!
This release adds support for new languages, frameworks, and components, while expanding administrative capabilities for agents and licenses to help you deal with the complexity of today's distributed, heterogeneous application environments.
This page describes selected highlights of this release. For more information about this release, see the Release Notes.
The App iQ Controller uses licensing to determine the features that are available in an App iQ deployment and the scale of the deployment. The new License Management module gives you great visibility into your license consumption model, allows you to easily manage entitlements from your license pools, and manage and distribute your access keys usage so you can scale out your different applications.
License Management Scope configuration allows you to assign licenses to specific applications and machines. Using scopes to configure licenses allows you to easily express and scale the configuration modules as required.
License Management provides:
- Granular control with precise rules and access keys that restrict which hosts and apps consume licenses
- Great visibility with detailed current and historical usage reporting across business units and services
On the Add/Edit Rule dialogs, you can create/edit rules to specify license allocation according to selected agents, applications, and machines/servers, following a mix and match model. For example, a rule can be applied to a selected application running on specific machines.
The following illustrates the flexibility of license assignments under the license scope configuration model.
Using the "Include Applications/Machine matching the following criteria" option, you can easily make your selections by matching multiple machines using the match criteria. This is so much more efficient than scrolling through thousands of applications and machines to make your selections manually. You can also add to the rule any uninstrumented applications in the Application Scope and unmonitored machines in the Machine Scope, so that when you install the agents to instrument these unmonitored applications and servers, they will be allowed to use the licenses defined in this rule.
We can interactively monitor the licenses by clicking the name of a rule. App iQ displays usage over time statistics that are updated at specified time intervals, usually every two minutes or so.
On the Peak Usage tab, you can view license usage data for all your licenses over specified time ranges, including Application Performance Monitoring (APM) Agent, User Experience, Analytics, Database, and Server Visibility licenses.
Increased Platform Support
.NET Agent Supports Azure Websites
In addition to the already supported Azure Cloud Services: Web Roles and Worker Roles, the .NET Agent now supports Azure App Services (formerly Azure Websites). You can use Microsoft VisualStudio to add the .NET Agent directly to projects you plan to deploy to Windows Azure Cloud and App Services.
PHP Agent Supports PHP 7 Applications
The PHP Agent now supports PHP versions 7.0 and 7.1.
Server Visibility Supports Solaris
Server Visibility now supports Solaris servers and now includes additional windows in the Controller UI that enable you to quickly see underlying infrastructure issues impacting performance of applications running on Solaris servers.
New Go Agent Supports Google's Go Language
Applications that have been created with Google Go can now be monitored by App iQ by instrumenting them with the new Go Agent SDK for Application Performance Monitoring.
The Go Agent uncovers Go processes, allowing App iQ to:
- Trace transactions through Go tiers
- Surface Go runtime errors
- Report backend calls made by Go services
Scoped Business Transaction Detection Configuration
The scope configuration model is an alternative to the hierarchical inheritance model that App iQ applies to license allocation, transaction detection and analytics agent logs. The following diagram shows the hierarchical configuration model and the Scope Configuration Model for business transaction detection.
Using scopes to configure transaction discovery allows you to easily express and scale the configuration modules as required.
Transaction Detection Scope Configuration allows you choose which tiers of an application to include in a group, and then detect and track specific transactions for that group according to your specified transaction detection rules.
The following diagram shows the Scope Configuration Model for business transaction detection.
App iQ provides interactive tools to help you find business transaction entry points for Java and .Net apps. When you initiate a business transaction discovery session, using Live Preview, the Java and .Net agents stream live data to the Controller UI so you can identify the classes and methods of entry points to use in Transaction Detection Rules and monitor the business transactions that are important to your bottom line. Live Preview allows you to drill down to see all the inbound payload data. From the list of entry points you can choose which entry points to instrument.
Within the context of the Transaction Discovery Session, you can:
- Edit transaction detection rules and preview business transactions (Java Agent only)
- Identify entry points from un-instrumented code
Browse Classes/Methods to identify entry points
Business Transaction Automatic Cleanup
Automatic business transaction cleanup prevents less active transactions from cluttering your business transaction list. You specify the activity threshold for stale business transactions as a number of calls within a time period. Business transactions that fall below the activity threshold are flagged as stale and deleted.
Centralized Log Management for Log Analytics
Centralized Log Management provides a Controller-based UI for configuration and field extraction, replacing job files used in previous versions. Source rules of the Centralized Log Management provide the same capabilities that job files provided in previous releases and new features such as:
- Expanded field management capabilities, including masking or removing sensitive data
- Ability to override time zones in log data
- Automatic field extraction using sample files
Agent Scopes for Log Analytics enables you to create a group of Log Analytics Agents and assign a set of source rules for capturing log data to the group. The source rules define the fields collected for Analytics from your log files. Using scopes to configure analytics logs allows you to easily express and scale the configuration modules as required.
Log Analytics Agent Scopes allow you to create a group of Analytics Agents, and apply to that group a set of rules to convert the log source files captured by the agent to more meaningful information.
As you can see in the following diagram, using scope configuration to control which logs are collected by which agents is really very flexible.
End User Monitoring Sessions for On-Premises Installations
AppDynamics introduced End User Monitoring (EUM) Sessions for SaaS installations in App iQ version 4.2. App iQ version 4.3 supports EUM Sessions for on-premises (on-prem) installations as well. Our End User Monitoring offerings for both SaaS and on-prem provide you with session information to give you deeper visibility into your browser and mobile users' journey through your 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:
- Recording 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
- Drilling 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
- Drilling down further to see the details of each page in a session and every action in a session. For mobile sessions captured by the iOS or Android agents, crash details per session are also available.
Transaction Analytics Getting Started Wizard
In this release we have a wizard to make it easy for you get started using Transaction Analytics on your App iQ SaaS implementation. The wizard helps you check prerequisites, install the Standalone Machine Agent if necessary, and update the Machine Agent configuration to enable Transaction Analytics.
At the heart of the AppDynamics App iQ Platform is the Controller which communicates with agents you install and use to instrument your applications so the App iQ Controller can automatically detect application activity. Historically, deploying agents was accomplished in a very manual way. Prior to App iQ version 4.3, agents were deployed and managed manually via configuration files located on the disks of target machines or perhaps using build automation to install them on the box and then you needed to continue to update and maintain them over time. This presented a problem during large scale upgrades and reconfiguration of 100s of thousands of agents. AppDynamics recognized the need for a centralized way to manage agent configuration, as well as upgrades of batches of agents.
In App iQ 4.3, we introduce the Universal Agent which allows you to easily deploy agents on machines with very little configuration and overhead and more easily manage runtime agents deployments and updates. You can install a single agent, the AppDynamics Universal Agent that performs the installation, removal, upgrades, downgrades, configuration, and lifecycle. The best news is, that the Universal Agent does this in a single command via RESTful APIs, so users rarely have to touch the box again after installing the Universal Agent; all the management can be handled via APIs and batch actions. So, if you have 2,000 agents, all lifecycle management, upgrades, and configuration can be automated and performed in batch.
The Universal Agent enables you to manage the AppDynamics Standalone Machine and Java APM runtime agents from a single configuration file on the Controller.
A single Universal Agent manages the runtime agents for the machine it is installed on and can download and install runtime agents from the Controller runtime agent source repository, that is a local runtime agent repository on the same machine where each Universal Agent is installed or that is located on a shared file system, so that more than one Universal Agent can access it at a time. The Universal Agent uses rulebooks to add or remove agent instances on the machine by automatically checking the rulebook at regular intervals and applying changes when they are detected.