Skip to content
CA Application Performance Management - 10.5
Documentation powered by DocOps

Integrate CA App Synthetic Monitor In Your APM Deployment

Last update February 6, 2017

CA App Synthetic Monitor (ASM) provides end-to-end transaction response-time visibility into cloud, mobile, and web applications to provide up-to-the-minute insight into performance and availability. The ASM agent is an integration between ASM and APM. Each ASM agent acts as a standalone agent, converting ASM folder, monitor, and checkpoint data that a single ASM account generates into APM metrics. The ASM agent retrieves data from an ASM account at configurable intervals. The ASM agent connects to a standalone Enterprise Manager or Collector as an Introscope agent, and reports metrics every 7.5 seconds.

To integrate ASM, first download and install the agent, then validate the ASM agent connection.

API Credits

The ASM Agent makes API calls and therefore, consumes API credits in the ASM account. One ASM agent consumes approximately 3500 credits per day. Ensure that your ASM account has sufficient API credit for the number of agents and other API usage . For details of API credit usage, click the specific API call in the ASM API documentation.

Note: A basic ASM account provides 10,000 API credits per day. To increase API credits, go to the Subscriptions tab in your ASM account.

Download and Install the ASM Agent

In this task, you download and install the ASM agent, which is required to integrate ASM and APM.

Note: You can install the ASM agent on any computer on your network. Its function is to receive ASM data over the internet and forward the data to the Enterprise Manager, so it can be any computer, though you should choose a computer with server-level CPU/RAM.

To download and install the ASM agent:

  1. Download the ASM agent archive file. Save the file to your computer.
    Installers for Windows, Linux and Solaris are located on the CA APM software download website.
  2. Install the agent.
    1. Launch the ASM installer file.
    2. Accept license terms.
    3. Specify the <Agent_Home> directory.
    4. Specify the Enterprise Manager host and port the agent will connect to.
    5. In the ASM Account Settings screen, enter your ASM userid and API password.

The ASM agent installation is complete.

Validate the ASM Agent Connection

To validate that the ASM agent is correctly installed, you start the agent, and check for data using WebView or the Workstation. Validate the connection by verifying incoming data from ASM is current.

Note: To see ASM data in WebView or the Workstation, you must have set up folders and monitors in ASM.

Follow these steps:

  1. Navigate to the directory where the ASM agent was installed, and run one of these files to launch the agent.
    • On Windows, double-click APMCloudMonitor.bat.
    • On Linux or Solaris, run APMCloudMonitor.sh.
    The agent launches in a console window.
  2. Launch WebView or Workstation.
  3. Locate data from ASM.
    1. If an Investigator window is not open, select File > New Investigator.
    2. Browse to the Metric Browser tab.
    3. Expand the following nodes:
      SuperDomain | <Host_Name> | CAAppSyntheticMonitor | CAAppSyntheticMonitorAgent | CA App Synthetic Monitor
      <Host_Name> is commonly the computer where you installed the ASM agent, but what appears in the Metric Browser tree is the value of the property apmcm.agent.hostName in the CAAppSyntheticMonitor.properties file.
    4. Expand folders to see individual metrics and confirm that the metrics are current.

Troubleshooting

Symptom

WebView/Workstation do not allow the full display of ASM data.

Solution

If you failed to select "App Synthetic Monitor" as a monitoring option during the Enterprise Manager installation process, this problem can occur. Copy contents of the <EM_Home>\examples\CAAPMIntegrationForAppSyntheticMonitor\ directory to <EM_Home>\config\modules\ and <EM_Home>\ext\xmltv.
The management modules and other files necessary are then available to display ASM metric data.

Symptom

Monitors fail with errors such as Access denied: 530 (Login denied) or 401 (unauthorized).

Solution

Insufficient or missing security credentials commonly cause this problem. For basic monitors, you can add a username and password by editing the monitor.

  1. Click Show More options.
  2. Complete the exposed User Name and Password fields in the monitor properties.
    If this information is already filled out, ensure that the user and password are properly specified.
Was this helpful?

Please log in to post comments.

  1. Adrien Stozicky
    2018-01-08 07:08

    It would be perhaps a good idea to mention that you have to look for CA Application Performance Management Agent MULTI-PLATFORM>Release 10.0>APM Integration for APM Cloud Monitor r10.0 on the support.ca.com to find the files

    1. Maria Wasilewska
      2018-01-08 07:24

      Thanks for the  comment Adrien.

      I'll forward this to the appropriate tech writer for review.