IBM Cloud App Management V2019.4.0 is generally available on December 13, 2019. Here are the new features and enhancements of the release:

IBM® Cloud App Management

Transaction Tracking
Enabled Transaction Tracking to provide an ability to troubleshoot an issue by looking at a specific request flow through the system and quickly identifying the bottleneck which caused the bad experience for that client. The transaction tracking feature enables topology views and instance level transaction monitoring. By distributed tracking infrastructure, transaction tracking can detect bottleneck issues including latency problems and errors, and filter or sort traces based on application. Transaction tracking can also filter views based on length of trace, timestamp, interactions, errors and transaction comparisons. For more information, see Transaction tracking.

Entitled Registry Installation
Entitled registry is an efficient installation experience using industry best docker-based processes for image management and optimization. Entitled software, IBM Cloud App Management in this case is stored in an IBM Cloud Container Registry cp.icr.io domain. To access the IBM Cloud App Management installation image in this domain, you must create an image pull secret with an entitlement key for your cluster and add this image pull secret to the Kubernetes service account of each namespace where you want to deploy the IBM Cloud App Management entitled software. After this setup, you can select the Cloud App Management Helm chart from the IBM-entitled-charts in the catalog where it can be quickly installed.
For more information about IBM Cloud App Management with IBM Cloud Pak for Multicloud Management online installations using Entitled registry, see Online installation of IBM Cloud App Management with IBM Cloud Pak for Multicloud Management topics.

Incident resolution
Navigation enhancements were added to facilitate incident resolution: While investigating an incident, you can select the Event resource page from the Events tab to see a timeline of metrics in context of when the problem surfaced. As well, transaction traces reflect the API that drove the incident.

OpenShift monitoring

You can monitor OpenShift route traffic performance and router performance by deploying the Unified Agent plug-in for OpenShift. The plug-in monitors each route response time, volume and error, and also integrates with Kubernetes data collector to enable exploring the associated services and application data. For more information, see Configuring OpenShift monitoring in Unified Agent.

Adding HTTP server support for digital experience monitoring (DEM)
Besides Liberty applications, you can now enable DEM on HTTP server by installing the DEM plug-in for HTTP Server. The DEM plug-in for HTTP Server passively collects data on how actual users are interacting with and experiencing your application. This is achieved through instrumenting the application or injecting code on the page to collect metrics. With DEM and Transaction Tracking and Deep Dive, the DEM plug-in for HTTP Server can monitor web application performance from the browser to the line of code. For more information, see Deploying digital experience monitoring(DEM).

New agents and data collectors

  • Citrix VDI agent
    The Monitoring Agent for Citrix Virtual Desktop Infrastructure monitors the following functions: Citrix XenDesktop component, Event log and alerts, and Citrix XenDesktop services. Additionally, you can view the Load Index Summary metrics performance data for Citrix XenApp and XenDesktop. You can diagnose problematic login times by viewing the performance data for the login steps. For more information, see Configuring Citrix Virtual Desktop Infrastructure monitoring.
  • Go data collector
    The Go data collector can provide you with visibility and control of your Go applications, and help you ensure optimal performance and efficient use of resources. You can reduce and prevent application crashes and slowdowns around the clock, as the data collector assists you in detecting, diagnosing and isolating performance issues. For more information, see Configuring Go application monitoring.
  • HMC agent
    The Monitoring Agent for HMC provides you with the capability to monitor the Hardware Management Console (HMC). The HMC agent monitors the availability and health of HMC resources such as CPU, memory, storage, and network. It collects the following metrics: HMC, Managed Server(CEC), LPAR, VIOS, CPUPool, VSCSI, FibreChannel, and NPIV and sends these metrics to the Cloud App Management server. The supported HMC versions are V8.2 to V8.7, and V9.1. For information about configuring the agent after installation, see Installing and Configuring the HMC agent.
  • Microsoft Active Directory agent
    The Monitoring Agent for Microsoft Active Directory provides capabilities to monitor the Active Directory in your organization. You can use the agent to collect and analyze information that is specific to Active Directory. For information about configuring the agent after installation, see Configuring Microsoft Active Directory monitoring.
  • RabbitMQ agent
    TThe Monitoring Agent for RabbitMQ provides you with the capability to monitor the RabbitMQ cluster. You can collect and analyze information about the nodes, queues, and channels of the RabbitMQ cluster. For information about configuring the agent after installation, see Configuring RabbitMQ monitoring.
  • Sybase agent
    The Sybase agent offers a central point of management for distributed databases. It collects the required information for database and system administrators to examine the performance of the Sybase server system, detect problems early and prevent them. For information about configuring the agent after installation, see Configuring Sybase Server monitoring.
  • Ruby data collector
    The Ruby data collector can provide you with visibility and control of the Ruby application, and help you ensure optimal performance and efficient use of resources. For more information, see Configuring Ruby application monitoring.
  • WebLogic agent
    The Monitoring Agent for WebLogic provides you with a central point of monitoring for the health, availability, and performance of your WebLogic server environment. The agent displays a comprehensive set of metrics to help you make informed decisions about your WebLogic resources, including Java™ virtual machines (JVMs), Java messaging service (JMS), Java Database Connectivity (JDBC). For information about configuring the agent after installation, see Configuring WebLogic monitoring.

Agent and data collector enhancements


Db2® agent

  • Added support for Solaris x86-64.
  • Added support for RHEL 8 on x86-64 and Power Linux Little Endian (pLinux LE) (64 bit).


Hadoop agent

  • Added new widgets to monitor Job Details parameters: Failed Map and Reduce tasks, and Map Output Record spills.
  • Added legends for the charts having more than one metric.


Microsoft Exchange Server agent

  • Added support for Microsoft Exchange Server 2013, 2016 and 2019.
  • Added resource type Microsoft Exchange Server for Microsoft Exchange Server 2007 and 2010.
  • Added resource type Microsoft Exchange Server 2k13 for Microsoft Exchange Server 2013, 2016 and 2019.


Python data collector

Added the support of uWSGI and mod_wsgi/Apache httpd. For more information, see Configuring Python application monitoring.

SAP agent

A line chart is added on the UI depicting the count of errors that occur on the SAP system. Error counts shown in the line chart are:

  • Kernel Errors
  • Database Interface
  • ABAP Programming Errors
  • Installation Errors
  • Resource Shortage Errors


SAP HANA Database agent

A line chart is added on the UI depicting the count of errors that occur on the SAP HANA Database. Error counts shown in the line chart are:

  • Network error
  • CPU Errors
  • Storage Errors
  • Administrator / Configuration Errors
  • Memory errors

Join The Discussion

Your email address will not be published. Required fields are marked *