CA APM monitor
This section explains how to use the CA Application Performance Management (APM) monitor. The CA APM monitor is a Web application monitor that lets you detect and diagnose performance problems in your complex or enterprise environments.
To use this monitor, you need to specify a cloud server that offers the monitoring service.
For the supported server versions, see the Integration with non-Micro Focus products section of the System Requirements.
This integration allows you to display up to 100 (approximately) CA APM measurements during runtime.
If you are using a cloud-based CA APM solution with a corporate proxy on your network, you need to set up a web proxy to collect data from it. To do so, on the Performance Center server, open the PCWEB\MEApplication.exe.config file in a text editor, and add the following under the configuration section of the file:
<system.net> <defaultProxy enabled="true">
<proxy proxyaddress="http://<PROXY_ADDRESS>:<PORT>" bypassonlocal="True" />
Set up the CA APM monitor
From the Performance Center navigation toolbar, click and select Monitors (under Assets).
In the test resource tree, select an existing monitor profile, or click New Monitor Profile and create a new monitor profile.
In the Monitor Profile page, click Add Monitor and select CA APM.
In the CA APM page, enter the server details:
Click Get Counters to display a list of available metrics and counters per metric from the selected CA APM application, and select the relevant measurements that you want to monitor.
You can get all types of metrics including application, user experience, database, and server metrics.
For detailed information on the performance measurements that CA APM can monitor, refer to the CA APM documentation.
Notes and limitations
The following are notes and limitations when using the CA APM monitor:
|REST API support||
CA APM does not support REST API calls for versions earlier than 10.7.
|Delay displaying data||
The default sampling rate for a cloud-based CA APM solution is every 15 seconds. This means that data is slightly delayed in arriving relative to other monitors which provide a much more granular data sampling. While this might not affect the data flow during the run, it will affect the time it takes to fetch data from CA APM when configuring the monitor profile.