21.11

Here are the new, changed, and deprecated features in DX Application Performance Management (DX APM) 21.11.
apmsaas
2
Cloud Monitoring Enhancements
Here are the enhancements that are related to cloud monitoring in this release.
Google Cloud Monitoring
Google Cloud Platform Firewall Insights Monitoring
You can now monitor the health and performance of Firewall Insights, which provides information about firewall usage and firewall configuration issues. Firewall Insights Monitoring supports the correlation between Virtual Private Cloud (VPC) elements such as Project, Region, Zone, and Subnets. This correlation provides you with metrics that deliver a holistic monitoring experience. You can better understand and safely optimize your firewall configurations. You can also review reports about firewall usage and the impact of various firewall rules on your VPC network.
More information:
Google Cloud Platform Firewall Insights Monitoring
Amazon Web Services (AWS)
AWS Virtual Private Cloud Monitoring
Use AWS Virtual Private Cloud Monitoring to visualize your AWS Cloud Platform VPC and how your VPC components are connected. Examine the metrics to monitor your VPC health and performance. This extension helps you understand the context of applications that are connected to your VPC, providing you with application-to-infrastructure-to-network correlation. Monitor and analyze AWS Cloud Platform VPC key performance indicators. These indicators include data in from source, data out to destination, active connection count, and error port allocation.
More information:
AWS Virtual Private Cloud Service
AWS Transit Gateway Monitoring
AWS Transit Gateway is a service that allows you to connect your AWS Cloud Platform VPCs and their on-premises networks to one gateway. AWS Transit Gateway Monitoring provides you with data about your AWS Transit Gateway health and performance. This extension also correlates your AWS Transit Gateway with other VPC components. Transit Gateway Monitoring enables you to visualize and resolve problems with accurate metrics data on network activities and traffic sources. These metrics help you to optimize bandwidth allocations, ensure proper capacity planning, resolve issues, and monitor the bandwidth consumption.
More information:
AWS Transit Gateway Service
Amazon FSx Monitoring for Windows File Server
Amazon FSx allows you to start, run, and manage commercial and open-source file systems in the AWS cloud. Amazon FSx Monitoring for Windows File Server automatically discovers this service and periodically performs a synchronize operation. You can choose the matrices for DX APM to monitor using Basic and Advanced filtering. You can use Amazon FSx Monitoring for Windows File Server service-specific attributes such as ipAddressm type of ipAddress, VPC Id, and DNS hostname.
More information:
AWS FSx for Windows File Server Service
Java Agent
Monitor Java Agent Experience Frontends Performance
The Java Agent now tracks Experience frontends performance throughout transactions. This capability allows you to use Assisted Triage to determine the root cause of application performance issues. The Java Agent pinpoints performance bottlenecks by correlating software stack application anomalies to poor and unacceptable Experience performance.
More information:
Java Agent Experience Frontends
Kafka Monitoring Improved to Use SSL
The Kafka Monitoring Java Agent extension now allows you to monitor your Kafka using the Secure Socket Layer (SSL) security protocol.
More information:
Kafka Monitoring
Monitor Azure Java App Services
The Java Agent for Microsoft Azure App Services allows enterprises running Java applications in Microsoft Azure to identify and resolve performance issues. The Java Agent for Microsoft Azure App Services integrates performance metrics into DX APM for intelligent analytics, alerting, and visibility on a single dashboard. You can deploy this site extension when you deploy a Tomcat container in Azure. After you deploy the Java Agent for Microsoft Azure App Services, you can configure agent properties using the Azure site settings.
Infrastructure Agent
New DX APM-Mainframe Integration
You can now monitor the performance of your SYSVIEW mainframe environment using the new DX APM-Mainframe integration. This DX APM Infrastructure-Agent-based integration includes out-of-the box Grafana DX Dashboards, SYSVIEW and Cross-Enterprise APM (CE APM) metrics, and alerts for the SYSVIEW metrics.
More information:
DX APM - Mainframe Integration
New SystemEDGE Data Collectors
The new SystemEDGE Data Collector decouples SystemEDGE Core from Infrastructure Agent Host Monitoring. However, DX APM continues to support all of your legacy and custom SystemEDGE-based monitoring use cases after you upgrade to the APM SaaS 21.11 Infrastructure Agent. The SystemEDGE Data Collector allows you to continue using the SystemEDGE core libraries. In the future, the SystemEDGE libraries will be available only by using the Infrastructure Agent SystemEDGE Data Collectors. The SystemEDGE Data Collectors support SNMPv3, providing SNMPv enhanced authentication and privacy.
DX APM provides two SystemEDGE Data Collectors: the Standalone SystemEDGE Data Collector and the SystemEDGE Data Collector for Linux. The Standalone SystemEDGE Data Collector is supported for AIX, Linux, and Windows. The SystemEDGE Data Collector for Linux allows you to continue using Host Monitoring and employ the benefits of using a SystemEDGE Data Collector.
More information:
Standalone SystemEDGE Data Collector, SystemEDGE Data Collector for Linux
Run Multiple Infrastructure Agents on the Same Computer
You can now run multiple Infrastructure Agents on one computer to spread out the load to help you manage monitoring many bundles. You can configure the service name and ports when you install the Infrastructure Agent to eliminate conflicts from multiple installed agents on the same computer.
More information:
Download and Install the Infrastructure Agent on AIX, Linux, and Solaris.
Infrastructure Agent Load Balancing for Node.js Environments
You can now load balance multiple Infrastructure Agents to achieve high-availability in complex Node.js container and cloud environments. UMA provides HTTP communication between the Node.js Probe and the UMA HTTP Collector Agent. This functionality allows you to configure HTTP load balancing to manage your Infrastructure Agents. The Load Balancer provides automated traffic distribution from Node.js Agents to multiple HTTP Collector Agents. This distribution prevents overload on any particular Node.js Agent.
More information:
UMA for HTTP Collector
Log Monitoring Enhancements
Log Monitoring now reads newly generated log files after configuration without having to restart the managed application. You can configure log-file names using regular expressions (regex) for better name-matching. Log Monitoring can now dynamically read log files that are created daily or even more frequently. DX APM can now read errors from log files and create the associated Errors per Interval metric and Error Snapshots. Team Center displays error transaction traces when you select a Log Monitor agent vertex.
More information:
Log Monitoring
Infrastructure Agent Security Improvements
The Infrastructure Agent is now supported on the latest platforms and industry-standard security protocols. Here are some examples: End-to-end AES-256 encryption; SHA-256 hashing; SNMPv3, wherever applicable; upgraded to VS 2017; and all passwords that are stored in configuration files are encrypted wherever applicable.
More information:
Standalone SystemEDGE Data Collector, Host Monitoring on Linux
MongoDB Monitoring Now Supports SSL
MongoDB Monitoring is now enhanced to use SSL for more secure communications between the MongoDB client and the Infrastructure Agent.
More information:
Install and Configure MongoDB Monitoring.
.NET/.NET Core Agent
Improved Browser Agent Monitoring
Browser Agent monitoring for .NET applications now includes HTTP header-based response decoration by default. No more manual tracer configuration is required achieve Browser Agent transaction trace correlation and correlation from DX AXA sessions to DX APM.
More information:
DX APM Articles
: Configure the Browser Agent for .NET/.NET Core, Configure Browser Agent Automatic Snippet Injection for .NET/.NET Core, Configure Browser Agent Response Decoration for .NET/.NET Core /
CA Experience Collector articles
: Install the .NET Agent and Configure the Browser Agent, Configure the Browser Agent for .NET, Browser Agent Properties for .NET.
Universal Monitoring Agent (UMA)
UMA DX Dashboards
UMA now provides out-of the box Grafana DX Dashboards to present your Kubernetes environments performance data. These dashboards supplement the Team Center Infrastructure layer dashboards. The UMA dashboards support all container environments, including Kubernetes, OpenShift, and Docker (ECS).
More information:
Universal Monitoring Agent, Universal Monitoring Agent (UMA) Dashboards
UMA Kafka Cluster Performance Monitoring
You can now monitor your Kafka cluster performance using UMA. UMA automatically discovers your ZooKeeper pods and Kafka Broker pods using annotations and your Kafka Monitoring extension configurations. You can configure SSL for Kafka Brokers and JMX over SSL.
Kubernetes Monitoring Enhancements
UMA now provides deeper insights into Kubernetes Monitoring, which provides even more network performance and cluster performance data. You can now run Kubernetes Monitoring on the latest Kubernetes version. Kubernetes Monitoring now includes Persistent volumes support, providing the new
%CPU/Memory utilization
and
%Disk Utilization by Pods
metrics. Monitor Kubernetes StatefulSets using the new
%CPU/Memory
utilization and
%Disk Utilization by Pods
metrics. The new metrics also display on the UMA DX Dashboards.
UMA Multi-Tenancy Support
You can now deploy and use UMA in a multi-tenant environment.
More information:
Deploy UMA in a Multi-Tenant Environment.
Manage Universal Monitoring Agents using APM Command Center
You can now create and deploy UMA packages in APM Command Center.
More information:
Deploy UMA Packages Using APM Command Center
User Interface Improvements
View Universe Roles in Team Center
When you use SSO authentication, the roles that you can play can vary for every session depending on the external IdP that is granted and provided in the SAML response. In the 
Launchpad
>
Settings
>
Users
panel, you can see your specific Universe roles and your tenant roles (User, Power User, Tenant Admin).  You can now also see your current profile role at the screen top right of window.
More information:
  In the Configure Universes article, see the section about
Configure Universes Security
.
New Team Center Icon to Access Javascript Calculator Management Page
As a Tenant Administrator, you can now click a new icon to access the
JavaScript Calculator Management
screen You can set the JavaScript view security in that screen.
More information:
Supported Roles and Privileges.
Agent Download Dialog Supports Multiple-Level Properties
The Agent Download Dialog now allows you to set properties that use multiple level configurations. For example, the log monitor configuration uses a variable number of matchitems, pathPatterns, and matchpatterns. Using this new functionality, you can add subproperties under subproperties when making configurations in the Agent Download Dialog.
Other Features
MongoDB and Redis Database Visibility for Python Agent Application Monitoring
The DX APM Python Agent now provides enhanced backend database visibility for your Python applications. You can now monitor your MongoDB and Redis databases to help you detect downstream components, enriching the topology along with service analytics and root cause analytics. Team Center displays performance metrics for backend calls, and correlated transaction traces.
More information:
MongoDB Support, Redis Support
DX APM Jenkins Plugin Enhancement
You now have the flexibility to configure the DX APM Jenkins Plugin in either primary or secondary mode depending on your Jenkins setup.
More information:
Configure the DX APM Jenkins Plugin.
Newly Supported Platforms and Capabilities
APM for SiteMinder (CA APM for CA SSO) Support for AIX 7
You can now monitor the performance of APM SSO running on AIX 7. Now curl is bundled with the APM for SSO Web Agent for AIX, which also has AIX 7 64-bit support.
More information:
In the APM For SiteMinder 13.3.0 article, see the
Installation and Configuration on Web Agent (AIX)
section.
Infrastructure Agent Platform/Environment Support and Certification
The Infrastructure Agent is now supported on more of the latest platforms and industry-standard security protocols. All Infrastructure Agent functionalities are certified to work on these platforms and in these environments: Windows 10, Windows 2019, Windows CORE 2019, RHEL 8.x, CentOS 8.x, SLES 15.x, OpenSuse 15, and Ubuntu 20.04. Infrastructure Agent SystemEDGE is supported on RHEL 8.x and Windows 2019 server. Infrastructure Agent Host Monitoring is supported for Windows 2019.
More information:
Host Monitoring on Windows, Supportability Matrix for Infrastructure Agent, Host Monitoring Troubleshooting
CA APM 10.7 EPAgent Supported on DX APM SaaS
DX APM allows you to continue using your CA APM 10.7x EPAgent Perl scripts in DX APM SaaS. You do so by migrating your CA APM 10.7 EPAgent to DX APM SaaS.
More information:
In the Cloud Proxy article, see the section
Migrate Individual Agents to DX APM using Cloud Proxy
.
Known Issues
Defect DE521796
- Duplicate Business Transactions Vertices on Map
Symptom:
I downloaded the DX APM 21.11 Tomcat Java Agent with the DX APM 21.11 Browser Agent extension. I navigated around DX APM and looked at the map in Team Center. For a few vertices, the business transaction vertex from the Browser Agent and the business transactions from the Java Agent are associated with the frontend vertex. This issue occurs only with DX APM 21.11 agents.
Solution:
Ensure that all three of these properties are set to
false
:
  • introscope.agent.first.frontend.biz.enabled
    When there are no externally defined business transactions, this property enables the Java Agent to create a default business transaction. The Java Agent identifies the first monitored frontend.
    • Values:
      true, false
    • Default:
      true
    • Example:
      introscope.agent.first.frontend.biz.enabled=true
    • Note:
      No monitored application restart is required.
  • introscope.agent.crossprocess.biz.enabled
    This property enables the Java Agent to forward business transactions across processes to downstream agents. This property allows DX APM to create cross-process business-transaction metrics for the downstream agents.
    • Values:
      true, false
    • Default:
      true
    • Example:
      introscope.agent.crossprocess.biz.enabled=true
    • Note:
      No monitored application restart is required.
  • introscope.agent.backend.biz.enabled
    This property enables the Java Agent to collect business-transaction metrics for backend components.
    • Values:
      true, false
    • Default:
      true
    • Example:
      introscope.agent.backend.biz.enabled=true
    • Note:
      No monitored application restart is required.
Defect DE521742
- Anomalies Not Converted to Problems
Symptom:
I wanted to monitor applications using  DX APM 21.11 agents without the Browser Agent being enabled. I noticed that anomalies are not getting converted to problems, even when my Frontend nodes have active alerts. Active alerts have a Danger or Caution state. New business transaction vertices were created by the DX APM 21.11 agent. These vertices report BlamePoint metrics. The BlamePoint metrics display under the new business transaction vertex, which is matching metrics that the agent generates for the frontend.
I noticed that anomalies were converted into problems only when the new business transaction vertices had active alerts. I see metrics under the Frontend node, however, there are missing business transaction metrics for the new business transactions. The missing metrics are all non-BlamePoint metrics. Also, default frontend alerts are not present under the new business transaction vertex. This issue occurs only with DX APM 21.11 agents.
Solution:
Create the frontend alerts by changing the metric grouping for default alerts. Include a new Business Segment node metrics regex, or create custom alerts on the business transaction BlamePoint metrics. The agent reports these metrics under the agent node
Business Segment
node. We have no workaround for creating custom alerts that are generated under the frontend node non-BlamePoint metrics.
Defect DE521611
- Alert Definition Link Error When Alert Name Contains Plus Sign
Symptom:
I created an alert and the name contains the plus sign (
+)
. The name was similar to this name:
cpu+Processor1
. I opened the
Settings
>
Alerts
>
Edit Alerts
page to test the alert. I opened DX Operational Intelligence and navigated to the
All alarms
page to test the alert definition. I selected my
cpu+Processor1
alert. In the
Overview
section under
Custom Attributes
, I clicked the
APM Alert Definition > Alert Definition
link. However, the
Alert
page would not open. And in DX APM, on the
Edit Alerts
page, this error message displayed:
Error fetching alert
. The same problem occurs when a management module name contains the plus sign.
Solution:
Do not include the plus sign in DX APM alerts and management modules.
Defect DE521571
- Exception when Downloading Bundle from APM Command Center to Running Agent
Symptom:
 When I was trying to download an APM Command Center bundle to my running Java Agent, the agent threw exceptions similar to this message:
Could not copy file from https://<
gateway name
>:443/apm/appmap/acc/apm/acc/downloadpackage/70368744219120?format=zip&bundles=70368744216967&task=70368744219123&packageDownloadSecurityToken=<security token> to C:\
<download location>
\package.tmp. Error details javax.net.ssl.SSLHandshakeException: Received fatal alert: unrecognized_name
Note: This issue only occurs with certain JDK versions, for example, Java 1.8u25.
Solution:
We have no workaround for this issue.
Defect DE521544
- Add Experience Card Attributes Drop-down Does Not Display
Symptom:
I logged into my tenant and navigated to DX APM. I configured my Tomcat Java Agent, then exercised my application to generate some transactions. In
Experience View
, I selected
Add new "+"
. In the
Add Experience Card
page in the
select a
universe
dropdown list, I chose
Your applications
. In the
use entire universe or apply a filter
bullet, I chose
Select agent from Application layer
. Under
Group by section
, when I selected the
Attribute
dropdown list, the list was empty. The list does not display any layer attributes. This issue occurs only with DX APM 21.11 agents.
Solution:
Select the
Include Experience node
check-box in the
Add Experience Card
page. You can see the
Attributes
dropdown list, but only for the
Application
layer, not other layers.
Defect DE520944
- APM Command Center Incorrectly Displays Error Message After Package Configuration Changes
Symptom:
I used the Agent Download Dialog to download an Infrastructure Agent. I navigated to APM Command Center to configure the Infrastructure Agent and chose
packages
>
Configuration
. I edited my package and configured a mix of cold and hot properties. Some properties require a managed application restart and some did not. When I clicked
Switch,
this message displayed:
Agent is not using the latest package version. The latest package version must be applied manually.
When I applied the new package version to the agent, this error message displayed for all the cold and hot Infrastructure Agent configuration changes:
The latest version of package "Infrastructure Agent-apmia-20211117" can only be applied manually. The agent that uses this package will not be displayed. APM Command Center does not support applying newer infrastructure agent package version through user interface.
However, the package still displays in the versions list, and I was able to apply the new package to my running agent.
Solution:
You can ignore these messages. All package-related functionality works properly. Package lists display the correct versions, and there are no issues when applying new packages to running agents.
Defect DE520499
- Transaction Trace Set Data Error Message in Browser Console and Notifications
Symptom:
I logged into my tenant and navigated to DX APM. I connected my Tomcat Java Agent, and exercised my Java application to generate some transaction traces. In
Metric
view, I selected an agent name and clicked on the
Traces
tab. I changed the time from
Live
to various historical times, for example, 24 or 6 hours while keeping the
Traces
tab open. After few minutes, this exception appeared in my browser console and browser notifications:
Error retrieving transaction trace set data. Status Code: undefined Type: undefined Reason: undefined
This message that is also displayed in my browser footer and debugger console in
Map
view when I selected a vertex.
Solution:
We have no workaround for this issue.
Defect DE519466
- Python Agent MongoDB Average Response Time Metric Zero Value is Incorrect
Symptom:
When the Python Agent is monitoring MongoDB read operations, the
Average Response Time (ms)
metric value is zero when the value should be greater than zero.
Solution:
We have no workaround for this issue.
Defect DE496868
- Upgrade - ADD Saved configurations: Package is not available post upgrade
Symptom:
I logged in to DX APM and navigated to the Agent Download Dialog in Team Center. Previously I had created and saved packages with property configurations. I clicked on
Settings
,
Agent
,
Download Agent
. When I then clicked on
Saved Package Configurations
, only the existing packages for the Infrastructure Agent were available. The saved packages for all my other agents displayed this error message:
Package is not available
. Agent examples are Tomcat on Windows and Linux Agents and Java Agents. The
Actions
column for these agents displayed no icons. Therefore, I could not edit or download these non-Infrastructure Agent packages.
Solution:
We have no workaround for this issue.