Here are the new, changed, and deprecated features in DX APM 21.6.
Cloud Monitoring Enhancements
Here are the enhancements that are related to cloud monitoring in this release.
Google Cloud Monitoring
GCP Cloud VPN Service
The GCP Cloud Virtual Private Network (VPN) service allows you to monitor the health and performance of Google Cloud Platform Cloud VPN. This capability helps you ensure that your cloud infrastructure is always available, and performant to meet your customer uptime SLAs.
The Google Virtual Private Network (VPN) establishes secure connections between your on-premises networks, remote offices, client devices, and the Google global network. This capability enables your organization to transition your VPN hosting to the cloud, thus improving access to your cloud-based resources.
More information:
Google VPN Service
Amazon Web Services (AWS)
AWS Database Migration Service (DMS)
Now monitor the health and performance of the AWS Database Migration service, which enables you to seamlessly migrate multiple components to your data in the AWS Cloud. These components include relational databases, data warehouses, NoSQL databases, and other types of data stores. You can use the AWS Database Migration Service to migrate your data between on-premises instances (through an AWS Cloud setup) or between combinations of cloud and on-premise setups. This service allows you to perform one-time migrations, and replicate ongoing changes to keep the sources and targets in sync.
More information:
AWS Database Migration Service
Java Agent
Improved Java Agent Property Logging
You can now examine Java Agent logs to determine the precise set of configuration properties in use and the source of the property values.
Java 13 and Java 14 Support
The Java Agent now supports Java versions 13 and 14.
JBoss EAP 7.3 Support
The Java Agent now supports JBoss EAP version 7.3.
Automatic Transaction Trace Filtering Default Change
Automatic Transaction Trace filtering no longer includes the fastestn and slowestn transactions in the default configuration. These settings can cause higher than normal resource overhead for certain applications. Here is the current property default in the
Configure Transaction Trace Filtering to enable filtering for the fastestn and slowestn transactions.
Infrastructure Agent
IBM DB2 Database Monitoring
You can now monitor the performance of your IBM DB2 database in your live environment. IBM DB2 database monitoring provides you with visibility into the database KPIs. This information enables you to isolate the problems from the application components and helps you quickly resolve issues in the live environment.
The IBM DB2 database monitoring extension is an enterprise-ready relational database management system. We designed this extension to deliver resiliency, performance, and cost-effectiveness for your transactional workloads.
More information:
IBM DB2 Database Monitoring
IBM DataPower Extension
The IBM DataPower extension is a single multi-channel gateway that is designed to provide security, control, and integration. We optimized this extension to access a full range of mobile, web, application programming interface (API), service-oriented architecture (SOA), B2B, and cloud workloads. The IBM DataPower extension allows you to monitor essential performance data about the DataPower gateway. You can proactively identify performance issues in the environment, and quickly correlate DataPower devices to backend applications.
More information:
IBM DataPower Extension
vRealize Operations Monitoring
You can monitor, troubleshoot, and manage the health and capacity of your virtual environment by applying policy-based automation. vRealize Operations Monitoring offers intelligent operations management with application-to-storage visibility across physical, virtual, and cloud infrastructures. This extension collects performance data from each object at every level of your virtual environment. The extension analyzes the data to provide real-time information about the performance issues.
More information:
vRealize Operations Extension
IBM Integration Bus (IIB) Monitoring Enhancements
You can now establish the IIB Monitoring connection using Local mode or Remote mode during the configuration. The Set Security Requirements to Monitor an MQ object have been optimized to provide more secure monitoring.
More information:
Install and Configure IIB Monitoring Extension, IIB Monitoring Metrics
RESTmon Observability Metrics
The Infrastructure Agent is now enhanced to support RESTmon observability metrics. You can use these metrics to self-monitor the performance of your cloud monitoring deployments. This support provides metrics about various platforms. We provide Amazon Web Services Endpoint-related metrics, Google Cloud Platform Monitoring-related metrics, Azure-related metrics, and so on.
More information:
RESTmon Observability Metrics
SiteMinder Monitoring Extension
DX Application Performance Management (APM) for CA Single Sign-On (CA SSO) is a special-purpose
package to monitor CA SiteMinder. The new
SiteMinder Monitoring extension includes this package. CA APM for CA SSO periodically collects CA SSO metrics and sends the metrics to the
Infrastructure Agent. The SiteMinder Monitoring extension includes multiple DX dashboards providing performance insights about proxy servers and web agents.
More information:
SiteMinder Monitoring Extension
Elastic Monitoring Extension
The Elastic Monitoring extension allows you to monitor the performance of the Elastic Search cluster, nodes, and indices to identify problems in your live environment. You can now filter metrics and perform group configurations using the Elastic Search Infrastructure Agent extension.
More information:
Elastic Monitoring Extension
Oracle Database Monitoring Support for Oracle 19C
The Oracle Database Monitoring Infrastructure Agent extension now supports Oracle database version19C. More information: Oracle Database Monitoring
.NET/.NET Core Agent
Smart Instrumentation Enhancements
.NET./.NET Core Smart instrumentation automatically discovers .NET/.NET Core frontends and backends. After discovery, the frontend and backend tracers added to a PBD file that the .NET Agent reloads. By default, the new tracers are disabled, however, you can configure the tracers. You can also start discovery sessions using a transaction trace session. .NET/.NET Core Smart Instrumentation also includes a configurable CPU trigger that starts a discovery session when the User CPU exceeds a threshold.
More information:
Configure .NET/.NET Core Smart Instrumentation.
.NET 5 Support
The .NET/.NET Core Agent now supports .NET version 5.
Universal Monitoring Agent (UMA)
Package and Download UMA Using APM Command Center
You can now create a UMA package with UMA-specific monitoring capabilities in the APM Command Center.
More information:
Deploy UMA Packages Using APM Command Center.
Pod Disk Usage Monitoring
You can now monitor the disk usage of pods that are configured with persistent volumes.
More information:
Pod Performance Data
UMA Automatic Agent-Naming in Container Environments
UMA can now determine an appropriate agent hostname for agents running in container environments. This capability includes automatic Java Agent naming in .NET/.NET Core; UMA AutoAttach in Kubernetes, ECS, OpenShift, and so on.
More information
: Install and Configure UMA for ECS, Install, and Configure UMA for Kubernetes.
UMA Multi-tenancy Support
You can now use UMA in a multi-tenant environment.
UMA AutoAttach Capability for Node.js Probe Agent
You can now monitor all your applications and infrastructure running in the Kubernetes environment with a single agent. The AutoAttach capability almost zero-touch or minimal touch configuration enables ease of onboarding and discovery. The AutoAttach capability offers you a one-stop solution for managing and monitoring out-of-the-box cloud-native applications on the hybrid cloud.
More information:
Node.js Agent AutoAttach
Known Issue
Under certain circumstances, the JVM might perform a core dump. This issue occurs when
is monitoring asynchronous applications.
As a workaround, take
of these actions:
  • Upgrade to the latest JVM patch.
    Upgrading typically solves this issue.
  • Create or update a package that contains the NoRedef bundle appropriate for your environment.
    The NoRedef bundle contains the
    file, which deactivates the class redefinition and retransformation to prevent possible performance issues.
    You can choose from these NoRedef bundles:
    • Java Agent NoRedef
    • JBoss NoRedef
    • Sockets NoRedef
    • Tomcat NoRedef
    • WebLogic NoRedef
    • WebSphere NoRedef