CA APM Release Notes

This release notes article explains the key features and details for CA APM 9.7.
apmdevops97
This release notes article explains the key features and details for CA APM 9.7.
2
2
CA APM Service Pack 9.7.1
This section of the Release Notes provides an overview of the new and enhanced features of Service Pack 9.7.1.
EPAgent HTTP RESTful Interface
EPAgent HTTP RESTful interface provides a REST-compliant interface that allows metrics to be submitted in batches over a more efficient RESTful PUT operation. You can configure the interface to submit metrics gathered from your application or environment. The HTTP RESTful Interface can operate with your existing EPAgent metric gathering solutions, including stateful and stateless plugins, network socket listener, and the HTTP method using GET with query parameters.
For more information, refer to the Configure the EPAgent RESTful Interface section of the EP Agent.
CA APM Command Center
CA APM Command Center provides an overview of Introscope Java agents in your environment. The application  web user interface enables you to see the list of Java agents installed in the environment, download agent log files, obtain diagnostic information about Java agents, and change the log level of agents. The Command Center is installed separately from CA APM. 
Fixed Issues
The APM Service Pack 9.7.1 fixes the issues noted in the  section.
CA APM Release 9.7.0
This section of the Release Notes provides an overview of the new and enhanced features of 9.7. 
For information about the enhancements that were made to the CA Cross-Enterprise Application Performance Management, see the
Release Notes
for that product.
Documentation Wiki
The new documentation wiki is a 
collaborative
 content delivery system that presents CA APM product documentation online. The wiki provides CA APM documentation for 9.6 and 9.7. Benefits of the wiki include easy direct involvement with and feedback from our customers, frequent documentation updates and fixes, and useful new product documentation between product releases.
CA APM bookshelves on CA Support Online continue to host previous release documentation.
Getting Started Roadmap
The new Getting Started Roadmap helps the CA APM Administrator install, configure, and administer CA APM.
Troubleshooting Guide
The new Troubleshooting Guide helps you to solve problems that you might experience with CA APM. Troubleshooting information for various CA APM components is easily accessible by navigating a central wiki location or by using keyword searches.
Smart Instrumentation
Deep transaction trace visibility has been renamed as smart instrumentation. Deep transaction trace components have been renamed as deep visibility components. Smart instrumentation has been expanded to include automatic transaction tracing.
Automatic Transaction Tracing
Introscope automatically collects a transaction trace when application errors occur or when a component response time was exceeded. The automatic transaction traces include deep visibility components and component details about the trigger mechanism and instrumentation level. 
Deep Component Visibility for Stalls
When a stall occurs, deep visibility components display in the Live Error and Historical Event viewers.
Smart Instrumentation Level Change Now Hot
Smart instrumentation provides three levels to determine the amount of managed application code that the agent instruments to discover deep-visibility components. You configure the instrumentation level using the introscope.agent.deep.instrumentation.level property in the agent profile. You can change the level without restarting the managed application.
Agent Ability to Collect Deep Visibility Components Now Enabled by Default 
The introscope.agent.deep.trace.enabled property enables and disables the agent ability to collect deep visibility components and send the data to the Enterprise Manager. This property is now set to true (enabled) by default.
WebView Charts and Dashboards
In this release, WebView now includes the following enhancements to charts and dashboards.
For more information about these features, see Work with Data Viewers.
Filter Agents with the Console Lens
The Console Lens lets you display dashboards using a specific set of agents. The list of agents is retrieved in the same manner that the Workstation uses.
Add Shapes and Connectors to a Dashboard
To help explain and illuminate your data, you can add the following shapes, lines, and connectors to a WebView dashboard. For example, you can draw connectors between objects to create a simple flow chart.
  • Line
  • Straight connector
  • Elbow connector
  • Polygon
  • Scribble (freehand drawing tool)
Show Min/Max Display in a Line Chart
In WebView, you can show minimum and maximum data point values in a time series graph chart for standard metrics, such as Average Response Time. When this charting option is enabled, you can:
  • Identify outliers in the metric spikes that indicate faulty data or errors.
  • Share the Min/Max URL with individuals or customers through email or instant messaging.
Export Data from a Chart to CSV
You can export a snapshot of current data in a line graph to a comma-separated values CSV file. With this export capability, you can:
  • Analyze data in an interactive spreadsheet program
  • Share the data with individuals and customers
WebView SMTP Mail Action Notifications
The following WebView SMTP Mail Action notification enhancements are included in this release:
  • Customizable email notification message
  • Common email notification template
  • SMTP mail server connection security
Both WebView and Workstation enable you to create or edit the SMTP Mail Action settings from the Management tab. However, only WebView enables you to use the enhancements in this release.
To configure SMTP mail actions, go to Configure Alerts, Metrics, and More and view the scenario: How to Create and Edit Actions for Danger and Caution Alerts.
Customizable Email Notification Message
From the Management tab, SMTP Mail Action configuration page, the WebView administrator can now perform these tasks:
  • Customize both the subject and body of the SMTP Mail Action notification message.
  • Add multiple email addresses in the To: field of the notification message. Use a semi-colon to separate email addresses.
  • Specify dynamic alert parameters in the body of the message, such as the alert name ${
    ALERT_NAME
    } and links to metrics. This capability provides more context about the triggered alert, which helps the triager understand the urgency of a problem, so they can perform the appropriate action.
  • Configure notifications to send emails in HTML or plain text format.
  • For the HTML notification, limited HTML markup is supported within the body of the template. The body can include links to control the layout and the supporting documentation.
    Not all email clients support HTML.
  • To help with routing email through rules, you can use the following email headers:
    • X-CA-Alert -- The name of the alert.
    • X-CA-Source -- The host name / IP address of the Enterprise Manager (or MOM) that sent the alert.
    • X-CA-Application -- The application name.
    Any rule-based routing must support UTF-8 for non-ASCII characters.
  • When you click the Test Now button to test the notification, the new custom message now replaces the simple message from the previous release. The notification uses a simulated alert to populate the property values. Metrics that are displayed provide links, but the links do not show an actual metric. The ${
    ALERT_NAME
    } parameter returns to the alert action instead. Only a simple alert is simulated.
To create and edit actions from the Management tab, WebView users must have read and write permissions to the domain (or SuperDomain).
Common Email Notification Template
The WebView administrator can define a common template in HTML (default.html) or plain text (default.txt) format for all email notifications. The common template is located in the <
EM_Home>
/config/notify directory and it supports the following alert types: Simple Alerts, Summary Alerts, and Triage Map Alerts.
In the template, the (${
email_body
}) tag indicates where the body definition is defined within the email message. When the notification is sent to recipients, the body definition is replaced with the new content.
Considerations:
  • The common template also supplies the default value for all Workstation client notifications, and for all SMTP actions from the previous release.
  • Certain alert parameters, for example, ${
    ALERT_NAME
    } and ${
    PROBLEM_LIST
    }, let you add hypertext links to contextual data within WebView. For plain text emails, the properties (${
    URL_Alert_Info
    } and ${
    URL_Detail_List
    }) supply these same links.
    This action requires you to configure the introscope.webview.default.url property value on the Enterprise Manager (or MOM) to locate WebView.
  • The Powered By tag has been added to all SMTP notifications by default. You can remove this tag as follows:
    • Modify the template file (default.html and default.txt) in the following <
      install_home
      >/config/notify directory.
    • Open the template file for editing and remove this property:
      ${ca_email_footer}
  • In the common template, you can add a corporate privacy disclaimer at the bottom of all notifications.
  • For the HTML formatted emails, you can perform minor restyling of the email using CSS styles. This action requires advanced knowledge of CSS styles.
    Not all email clients fully support CSS styles.
WebView Default URL for SMTP Email Notifications
For the SMTP email notification configuration, you can configure the introscope.webview.default.url property that defines the default URL for embedded hyperlinks to alerts and metrics in WebView.
To configure the introscope.webview.default.url property on the Enterprise Manager (or MOM) to locate WebView, see the WebView IntroscopeEnterpriseManager.properties.
SMTP Mail Server Connection Security
In this release, the mail server connection security has been enhanced as follows:
  • The SMTP Mail Action notification can now be sent to recipients using either TLS or SSL connections. By default, SMTP connections are not encrypted and typically use port 25 on the SMTP server. SSL and TLS both add a level of encryption of the data sent to the server. SSL requires a dedicated connection port (typically port 465) for its communication. TLS can start a connection unencrypted, then switch to an encrypted communication before transmitting data. In addition, TLS can reuse the single port 25 for both secure/non-secure communication.
  • To allow switching ports, the SMTP server port can be set to a value other than port 25.
  • For the JVM trust store, when applying certificates, review the vendor-specific mail server processes and Java standard practices.
Exchange does not support implicit SSL for the SMTP protocol; therefore, only TLS is supported on Exchange.
Impacts to SMTP Mail Notifications
The impacts to email notifications (SMTP Mail Action) from the 9.x to 9.7 release are as follows:
  • Enhancements to notifications in 9.7 are only supported on the WebView client and they are designed to function without end-user changes after an upgrade.
  • Any previously created SMTP Mail Actions now use the customizable default templates available in 9.7. The 9.x releases used a simple, non-customizable message.
  • In 9.7, you can create and edit email notifications through the Workstation. However, the email subject/body of the message, port, or connection type (SSL or TLS) settings are not configurable in the Workstation. They are only configurable in WebView.
  • Although the notifications continue to work without changes after an upgrade, the introscope.webview.default.url property value in the Introscope.EnterpriseManager.properties file must be configured. This property defines the default URL for embedded hyperlinks that link to alerts and metrics in WebView.
  • If you have rules-based handling of email notifications, update these rules to accept the changes to both the subject and body of the email message.
Changes to the email subject and body of the message are as follows:
Email Subject:
  • In the previous release, the title was fixed and looked like:
    Subject: Introscope Alert Message
  • In this release, the title looks similar to:
    Subject: CA APM Alert from SERVER3: Backend Average Response Times in Caution state
Email Body:
  • In the previous release, the body of the message looked like:
    7/30/14 1:39:00 PM PDT Introscope Enterprise Manager (testdriver02:10.130.84.244) reported:
  • In this release, the same email body using the default template (shown in plain text) starts with this text:
    Alert Name: Backend Average Response Times Time Triggered: 7/30/14 1:49:45 PM PDT Alert Status: Caution Problem Details: SuperDomain/TestDomain2|localhost|WurlitzerDomain|WurlitzerAgent_4|Backends|OracleDatabase_13:Average Response Time (ms) = 439 SuperDomain|localhost|WurlitzerDomain|WurlitzerAgent_9|Backends|OracleDatabase_12:Average Response Time (ms) = 314 SuperDomain/TestDomain1|localhost|WurlitzerDomain|WurlitzerAgent_3|Backends|OracleDatabase_13:Average Response Time (ms) = 204
PHP  Monitoring
CA APM now supports PHP monitoring that provides continuous visibility and management into your PHP applications by allowing you to verify how your application performs, how fast it responds and analyze and pinpoint application issues.  By implementing the APM PHP Agent, you can collect and analyze detailed performance information about transactions in your PHP applications and the system environment where you run the PHP applications. 
The PHP Agent features:
  • Automatic Frontend Detection and Monitoring
  • Deep Transaction Trace Visibility
  • Custom Instrumentation of the FrontendMarker, BlamePointTracer and BackendMarker
End-User Endpoints Monitoring
CA APM End-User Endpoints Monitoring lets you use a common business transaction definition to monitor the performance of an end-user business transaction in context from the backend application perspective. For example, this monitoring can track a native mobile application call as the application infrastructure handles the request to the mainframe or database.
End-user endpoints monitoring depends on a compatible end-user monitoring component. The compatible component externally provides CA APM business transaction context and metadata for each request to an application that CA APM monitors. Monitoring this data helps you to isolate backend application performance problems that may affect your end users.
One of the solutions that can leverage this functionality is CA Mobile App Analytics (CA MAA). CA MAA, in the CA Mobile DevOps (CA MDO) solution suite, provides the request information to CA APM when enabled. CA MAA provides facilities to instrument native mobile apps on handheld computing devices for operating systems such as Android and iOS. The business transaction context moves from CA MAA to CA APM to show the end-user experience based on the originating device platform in APM WebView.
High-performance Transaction Impact Monitor (TIM)
The high-performance Transaction Impact Monitor (TIM) handles high-load environments. The TIM provides parallel functionality in a software-only TIM release. You can scale beyond the 16-CPU core limits to handle as much traffic as the network card and CPUs can handle. If you need increased performance, use a server with more CPUs.
Enhanced RTTM by User Group
Real-time transaction metrics (RTTM) provide real-time information about the end-user experience before that experience degrades to the point that an incident is created. Using CA CEM, you can now organize the RTTM metrics by user group. This functionality lets you capture more effective and meaningful business metrics.
You use the CA CEM administrator options to enable and configure RTTM parameters and to alias one or more CEM user groups to more readable names. CA CEM provides these configurations to the Transaction Impact Monitor (TIM). Based on the business transaction definitions and RTTM configuration settings, the TIM optionally records data about recent transactions. This data appears as metrics in WebView, so you can monitor business transactions for performance issues in real time.
After you enable RTTM data and options, the TIM collects the following data for each observed instance of a business transaction definition:
  • The business transaction definition ID (always sent).
  • The user group.
WebView support the following features:
  • A separate CEM Applications node instead of a single TESS Agent node for all applications.
  • Under each business transaction, if reporting by user group is enabled, metrics are sorted by user groups and their rules for the alias defined in the CA CEM Administrator UI.
Real-time transaction metrics are also referred to as business transaction statistics or btstats.
APM Database Upgrade on PostgreSQL – Pre-9.6 to 9.7
If you are upgrading an APM database on PostgreSQL before version 9.6, some additional upgrade steps are required in this release.
For more information about the upgrade steps, see the scenario How to upgrade the APM database on PostgreSQL--pre-9.6 to 9.7.
CA APM integration with CA LISA renamed as CA APM Integration with CA Application Test
CA LISA was separated into three rebranded products. The CA LISA product that integrates with CA APM is named CA Application Test.
The CA APM Integration with CA Application Test product installer, file names, and user interface still refer to CA LISA. CA will rebrand these components in an upcoming release.
Cross-Enterprise APM
For information about the enhancements for CA Cross-Enterprise Application Performance Management, see Cross Enterprise APM Release Notes.
CA APM Products and Resources
For more an information about CA APM products and resources, visit Integrating and APM Solutions.
Note:
If you downloaded CA APM after December 2015, Application Behavior Analytics (ABA) is not available. Team Center provides improved information about application behavior.