November 26, 2019 - What's New!
Infrastructure Agent Metrics for RedHat
You can now view RedHat server metrics about CPU, disks, file system, memory, network, processors, paging, SWAP, system performance, and more.
Spring Boot Reactive Monitoring
This new Java agent extension monitors Spring Boot Reactive applications. The extension specifically instruments Netty asynchronous HTTP servers, Netty asynchronous HTTP clients, and Springboot Reactor Core frameworks to provide cross-thread correlation and asynchronous component tracking. For more information, see Spring Boot Reactive Application Monitoring.
Oracle RAC Monitoring
The Oracle RAC extension enables you to monitor the performance and availability of your Oracle Real Application Clusters (Oracle RAC) environment. You can use the Oracle RAC extension to locate if any service in a cluster database has availability problems. Oracle RAC extension provides real-time visibility into critical database resources such as deadlocks, full table scans, redo log files, rollback segments and more.
You can configure the Oracle RAC extension to collect the performance metrics of Oracle RAC to help you monitor your Oracle RAC environment. You can see immediate time to value in the pre-configured dashboards and performance-triggered alerts that pro-actively notify you of potential SLA violations, before end users are affected. For more information, see Oracle RAC Monitoring.
Oracle EBS Monitoring
The Oracle E-Business Suite (EBS) extension enables you to monitor the performance and availability of the following components of Oracle EBS: Concurrent Managers, Concurrent Programs, and Conflict Resolution Manager. You can use the Oracle EBS extension to review the concurrent jobs, concurrent managers at both the cluster level and the individual node level. For more information, see Oracle EBS Monitoring.
You can use IBM Integration Bus Monitoring (IIB) Monitoring to monitor the health and availability of IIB-connected applications and the corresponding message flows. As a prerequisite, IBM MQ must running so that the IIB Monitoring extension can connect with IBM MQ and collect the IIB statistics metrics. For more information, see IIB Monitoring.
The Java Agent now supports OkHttp monitoring. OkHttp represents an efficient HTTP client that supports the HTTP/2 protocol. This protocol effectively loads data and saves bandwidth. For more information, see OkHttp Extension.
Host Monitoring Metrics
In addition to the existing Host Monitoring metrics that
DX APMsupports, the Host Monitoring metrics for Solaris and RedHat are newly added. For more information, see Host Monitoring.
NGINX Monitoring Support
The NGINX Monitoring agent extension enables you to monitor the following versions of NGINX Server: NGINX-Plus Version and NGINX Community Version. You can use the extension to monitor the NGINX Infrastructure monitoring. For more information, see NGINX Monitoring.
NET Agent Dynamic Instrumentation Loading
The .NET agent now can dynamically load instrumentation without requiring application restarts. Here are some examples:
- You can instrument a specific method that does not already match an existing probe definition. Specifically, you can instrument asynchronous MVC methods without requiring a restart.
- DX APMcan reevaluate methods and modify instrumentation when you take these actions:
- Place a new .pbd file into thehotdeployfolder
- Change or remove an existing .pbd file.
AWS and Azure Services
- The new extension of Amazon Web Services (AWS) supports the following new service types: compute, storage, messaging, database, analytics, mobile services. For more information, see Amazon Web Services Monitoring.
- The new extension of Azure Services support the following new service types: compute, storage, and analytics. For more information, see Azure Monitoring.
Infrastructure Agent Known Issue
Defect DE437143 - No Host Monitor Metrics
DX APM10.7 Service Pack 1 (SP1-3), DX APM SaaS, 11.1.3, Kubernetes and Host Monitor
No metrics display under the
SystemEdgenode in the
Metric View. This issue happens under these conditions:
- The Host Monitor is re-installed using the Universal Monitoring Agent
- The CA SystemEdge process is not killed even when Kubernetes destroys the corresponding pod.
Follow these steps:
- Log on to theSystemEdgenode where no Host Monitor metrics are present.
- Use this command to kill the SystemEDGE process if it is running:ps -ef | grep "SystemEDGE" |grep -v grep
- Redeploy the Universal Monitoring Agent.