20.11

apmsaas
Here are the new, changed, and deprecated features in
DX APM
20.11.
2
Java Monitoring Enhancements
The Java Agent includes these changes:
Spring Cloud Gateway Monitoring
Spring Cloud Gateway Extension is an API Gateway that provides a simple, yet effective way to route the APIs.
More information:
Spring Cloud Gateway Extension.
WebSphere Portal Extension
The WebSphere Portal extension helps you to build and manage web portals. You can use this extension to create a portal, which is a collection of portlets. Each portlet is assigned a designated space in the portal. You can create the portlets by fetching data from various sources, and display data about the portlets in
Metrics View
.
More information:
WebSphere Portal Extension.
MySQL Version 8.x Support
The SQL Agent for Java now monitors the performance of database backend calls for MySQL version 8.x.
PostgreSQL EDB version 4.2
The SQL Agent for Java now monitors the performance of database backend calls for PostgreSQL EDB version 4.2.
Improved Java Agent for WebSphere Application Server Monitoring
You can now use the Agent.jar file as the JAR file for WebSphere Application Server (WAS) for versions 8 and higher. You no longer must configure the
AgentNoRedefNoRetrans.jar
file.
More information
: WebSphere Application Server.
More Java Agent Security
You can now use the
agentManager.tls.validateHostname
property to increase
DX APM
security by preventing potential trusted man-in-the-middle attacks.
More information
: Java Agent Properties.
Java Agent Transaction Tracing Enhancements
You can now use these two properties to collect and decorate Java Agent priority automatic transaction traces. Priority automatic traces are transaction traces that enable other essential capabilities, such as topology-discovery.
  • introscope.agent.deep.automatic.trace.priority.clamp
    This property clamps the number of priority automatic transaction traces that the agent collects per 1-minute interval.
  • introscope.agent.deep.automatic.trace.detailed.reason
    This property allows automatic transaction traces to be decorated with the detailed reason that the agent was triggered to collect the trace. Otherwise, the traces are decorated with a summary reason.
More information
: Java Agent Properties.
.NET Agent Monitoring Enhancements
The .NET Agent includes these changes:
.NET/.NET Core Smart Instrumentation
.NET/.NET Core Smart Instrumentation detects and instruments.NET/.NET Core frontends without any required configuration. .NET/.NET Core Smart instrumentation is enabled by default, and activated when you start a transaction trace. You can configure properties to control the logging of specific thread stacks and the location of generated .pbd files. Upon detecting a new frontend, the .NET.NET Core Agent adds more configuration to the
detected-frontends.pbd
.
More information:
Configure .NET/.NET Core Smart Instrumentation.
Enhanced .NET/.NET Core CPU Performance Root Cause Analysis
The .NET.NET Core Agent reports two new metrics that provide more CPU performance information about .NET methods. These metrics can help you determine whether a performance bottleneck is due to method code execution or the I/O time.
  • Average User CPU Time (ms)
  • Average System CPU Time (ms)
Async Fragment Metrics and Async Fragment Transaction Traces for ASP.NET and ASP.NET Core
The .NET/.NET Core Agent now monitors asynchronous requests in ASP.NET and ASP.NET Core applications. The Metrics Browser displays the associated frontend metrics under the
Fragments
and
Called Fragments
nodes. The agent also collects Fragment transaction traces.
More Information:
.NET/.NET Core Asynchronous Fragments.
Automatic Attribute Decoration for .NET/.NET Core
Automatic Attribute Decoration is included in the NET/.NET Core Agent to enable you to add custom attributes from your agent environment to your Team Center vertices. With Automatic Attribute Decoration, you can automatically control and populate all attributes to the vertices that the agent manages in your environment. The map displays the vertices, allowing you to identify the communication channel between multiple vertices in your environment. Added attributes allow you to more easily identify and isolate a problematic vertex, facilitating faster problem mitigation and issue resolution.
More information:
Automatic Attribute Decoration (.NET/.NET Core Agent).
Cloud Monitoring Enhancements
Cloud Monitoring includes these changes:
Google Cloud Monitoring
Cloud Bigtable Monitoring
Google Cloud Bigtable helps you store large amounts of single-keyed data with low latency. Cloud Bigtable Monitoring includes a static node that is named
multi-region
of type
GCP Region
. This static node allows you to connect the GCP Bigtable instances to the applicable regions.
More information:
Google Cloud Bigtable.
Google Memorystore for Memcached Monitoring
GCP Memorystore for Memcached is a highly scalable, fully managed Memcached service for the Google Cloud. You can monitor GCP Memorystore for Memcached using status metrics, attributes, and cloud metrics. For this agent, you can monitor the metric group at the node level.
More information
: Google Cloud Memorystore for Memcached.
Amazon Web Services
AWS SageMaker Monitoring
The AWS SageMaker allows you to train, build, and host a model at an available endpoint. You can monitor the performance of SageMaker using the AWS monitoring extension.
More information:
AWS SageMaker.
AWS Athena Monitoring
The Amazon Athena Service is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. You can monitor metrics from Cloud Watch and Service API. You can also monitor the derived metrics. AWS Athena Monitoring supports Workgroup, which helps to separate users, teams, applications, or workloads.
More information:
AWS Athena Service.
AWS Step Functions Monitoring
AWS Step Functions is a serverless orchestration service. This service allows you to combine AWS Lambda functions and other AWS services to build business-critical applications through a visual workflow. Enable this service to view your Step Functions metrics.
More information:
AWS Step Functions.
AWS Services Tag-based Discovery Support
The tag-based filtration helps you to monitor instances with only specific tags for the following AWS monitoring services:
  • AWS EC2 Monitoring Service
  • AWS Classic Load Balancer (CLB) Service
  • AWS Network Load Balancer (NLB) Service
  • AWS Application Load Balancer (ALB) Service
  • AWS S3 Service
  • AWS EBS Monitoring Service
  • AWS Redshift Service
Infrastructure Monitoring Enhancements
The Infrastructure Agent includes these changes:
Cassandra Monitoring
Cassandra Monitoring is an Infrastructure Agent extension that gathers and displays the Apache Cassandra database cluster metrics.
More information:
Cassandra Monitoring Extension.
Vault Monitoring
Vault Monitoring is an Infrastructure Agent extension that allows you to monitor the Vault server performance of different libraries and subsystems. This extension collects various metrics including runtime, core, audit, storage backend, request handling, and secret engine.
More information:
Vault Monitoring Extension.
Support for IBM Integration Bus (IIB) ten Trace Extension
The IIB 10 extension helps you monitor IBM Integration Bus message flows performance, generating transaction traces and metrics. You can use cppprobe and userexits, which are provided by IIB, to interact with message flows without modifying the existing application.
More information:
IBM Integration Bus (IIB) 10 Trace Extension.
Improved Cloud Foundry Monitoring
The Cloud Foundry Monitoring Infrastructure Agent extension reports new metrics so you can better manage your Pivotal Cloud Foundry Platform performance. For example, Cloud Foundry Monitoring now provides Auctioneer and BBS LockHeld metrics, User Account and Authentication (UAA) metrics, and more.
More information
: Cloud Foundry Monitoring Metrics.
Enhanced Host Monitoring for Windows
The Host Monitoring for Windows Infrastructure Agent extension now includes all the performance and health metrics from SysEdge.
More information
: Windows Metrics
Automatic Attribute Decoration for Infrastructure Agent
Automatic Attribute Decoration is an Infrastructure Agent extension that enables you to add custom attributes from your agent environment to your Team Center vertices. With Automatic Attribute Decoration, you can automatically control and populate all attributes to the vertices that the agent manages in your environment. The map displays the vertices, allowing you to identify the communication channel between multiple vertices in your environment. Added attributes allow you to more easily identify and isolate a problematic vertex, facilitating faster problem mitigation and issue resolution.
More information
: Automatic Attribute Decoration (Infrastructure Agent).
Support for Windows Authentication for IIS Web Server Monitoring
You can now configure IIB Web Server Monitor using Windows authentication.
More information:
Configure Web Server Monitor Using Windows Authentication.
Configure Secure Access for F5 LTM Monitoring
The F5 LTM Monitoring Infrastructure Agent extension includes the new
introscope.agent.f5.tokenAuth
property to execute token-based authentication.
More information
: Configure F5 LTM Monitoring.
NonRoot User Infrastructure Agent Access
Nonroot users can now install, start, and stop the
Infrastructure Agent. Some Infrastructure Agent commands have changed. This table lists the former and updated commands:
Former Command
Updated Command
force_start
console_start
force_stop
console_stop This command is also added for the UNIX-based Infrastructure Agent.
apmia-ca-installer.sh / apmia-ca-installer.bat
APMIACtrl.sh / APMIACtrl.bat
UMA Features
This section lists the new and enhanced Universal Monitoring Agent features.
UMA for Python Probe Extension
The Universal Monitoring Agent for Kubernetes now automatically discovers and instruments your Python applications without requiring any manual changes to the application image.
More information:
Universal Monitoring Agent for Python Extension.
UMA for NGINX Probe Extension
The Universal Monitoring Agent for Kubernetes now automatically discovers and instruments your NGNIX applications without requiring any manual changes to the application image.
More information:
Universal Monitoring Agent for NGINX Extension.
Zipkin Support
DX APM
now collects span data about applications that are traced by Zipkin, a distributed tracing system. Zipkin Support reports and displays application performance metrics, errors, and transaction traces. Zipkin Support is an Infrastructure Agent extension that provides data about HTTP frontends, HTTP backends, and database backends.
More information
: Zipkin Support.
Node.js Agent Features
This section lists the new and enhanced Node.js Agent features.
Monitor Nodejs Runtime Performance in Containerized Deployments
You can now install Node.js as a standalone agent without Python.
More information:
Install the Node.js Agent.
MS SQL Support for Node.js Agent
The Node.js Agent now supports calls from Microsoft SQL Server versions 2016 and 2017 database.
More information
: Supportability Matrix for the Node.js Agent.
PHP Agent Features
DX APM
now supports PHP version 7.4.
More information
: Supportability Matrix for the PHP Agent.
UI Features
This section lists the new and enhanced UI features.
Enhancements to Universes Creation and On Boarding
In the new
Universes
view, administrators can grant different rights to users and user groups. The rights include accessing the universe and filtering the metric sources. Filtering can be based on domains (access to agents) with attributes and regular expressions, map components, and management modules.
Also, the behavior of universes has changed, affecting the metric sources filtering. Due to the change, you must reconfigure the universe metric sources to have correct agent filtering apply to the Metric Browser. For example, say that your environment has ten active agents. Before the 20.11 universes enhancements, you had four agents listed in Universe X and displaying in Metric Browser. After the 20.11 universe changes, Universe X contains ten agents that all display in Metric Browser. You must explicitly update the universe metric sources to again have four agents that are listed in Universe X and displaying in the Metric Browser.
More information:
Configure Universes.
Disconnected Agents
You can now access data from disconnected agents.
More information
: Monitor Agent Metric Values with Metric View.
Sorting Attributes in Perspective Window
You can now drag and drop attributes in the
Perspective
window to sort or rearrange the attributes in the hierarchy. The attribute order defines the order in which the filters are applied, and therefore the vertices grouping.
More information
: Organize Components Using Perspectives.
Status Colors for Agents
Disconnected agents now display in gray.
More information
: Monitor Agent Metric Values with Metric View.
Other Features
Export Metrics in Metric View
You can now export the metrics in
Metric View
to, for example, combine different data types and create charts in Excel.
More information
: Monitor Agent Metric Values with Metric View.
Known Issues
This section lists the known issues for the current release.
Symptom
: I log into a tenant with SAML-enabled tenancy from Chrome. When I log out, I get logged back in.
Solution:
This issue is due to keeping the same tenancy. This behavior is typical for applications that are SSO-enabled, as is DX SaaS. Examples of other applications include MS Office 365, Box, SharePoint, and Google. The solution is to clear the cache when logging out for tenancy.
Defect DE481045 - Cannot Log Out of DX SaaS SAML Tenant
Symptom
: I log into a tenant with SAML-enabled tenancy from Chrome. When I log out, I get logged back in.
Solution:
This issue is due to keeping the same tenancy. This behavior is typical for applications that are SSO-enabled, as is DX SaaS. Examples of other applications include MS Office 365, Box, SharePoint, and Google. The solution is to clear the cache when logging out for tenancy.
Here are workarounds:
Start a new session without logging out.
  • Open an incognito browser window and start a new session.
  • Open a different browser, such as FireFox, and start a new session.
Log out and log back in to start a new session.
  • Log out, and then click
    Sign in with another Tenant
    within a few seconds.
  • Manually log out of a tenant by deleting the
    CA_CLOUD_Management
    cookie. Then log in to another tenant.
  • Close the browser and wait until the session times out. Then log in to another tenant.
Defect DE481045 - Difficulty Switching Between Multiple DX SaaS SAML Tenants
Symptom
: I can access multiple SAML tenants, however, I cannot easily switch between the tenants.
Solution:
Your apparent switching problem is the side effect of a DX SaaS logging-out issue. DX SaaS cannot log out of multiple tenants being accessed using the same browser. This issue only occurs when using SAML.
Use the same workarounds as for the previous issue.
Defect
DE486199
- Incorrect Behavior When Creating a Universe or Saving the Map Filter as a Universe
Symptoms
:
  • When I create a new universe, these unwanted behaviors occur on the
    Create Universe
    page:
    • Sometimes the field names and descriptions automatically populate with data from an existing universe. When I click
      Save
      , the page is saved with default options (see below).
    • The
      Management Modules
      radio button default of
      All Items
      changes to
      Selected Items
      when I fill in the
      Name*
      and
      Description
      fields. When I click
      Save
      , the page is saved with default options (see below).
  • When I save the map filter as a universe, these unwanted behaviors occur:
    • The
      Management Module Filter
      radio button is positioned next to
      Selected items
      instead of
      All items
      . When I click
      Save
      , the page is saved with default options (see below).
    • When I save the map filter as a universe, the
      include experience node
      setting is not applied to the newly created universe.
Here are the default options for saving a new universe:
  • When the universe is created by clicking the
    New Universe
    button, the
    All items
    option is selected in each tab.
  • When the universe is created by clicking the
    Save as Universe
    from the
    Map
    page, a filter is populated in the
    Map
    Components
    tab.  Other tabs have the
    All items
    option selected.
Solution:
These issues do not have a workaround.