Various Cloud Proxy Migration Issues

Products

• CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

I Have the following scenario:

On-Prem APM 10.8 environment: 20 agents, 3 collectors, 1 MOM

I want to migrate some agents from APM 10.8 on-prem to APM DX SaaS.

Questions:

• What is the best procedure to achieve this ? I understand I have to install a cloud proxy and use the loadbalancing.xml file to redirect traffic from MOM to cloud proxy server.
•  What are the network requirements for cloud proxy server?
• What is the procedure to install cloud proxy application on a new Windows Server?

Cause

 

Resolution

Table of Contents

• 1. Migrate Agents 
  • 1.1 References
  • 1.2 Using a Load Balancer
  • 1.3 Network Requirements for Cloud Proxy
  • 1.4 Optimize Cloud Proxy Network Performance
  • 1.5  Procedure to install the Cloud Proxy application on a new Windows Server
  • 1.6  Cloud Proxy High Availability

1. Migrate Agents 

1.1 References

Please see

• Migrate Agents Using Cloud Proxy
• Migrating Next Generation APM

1.2 Using a Load Balancer

What is the best procedure to achieve this ? I understand I have to install a cloud proxy and use the loadbalancing.xml file to redirect traffic from MOM to cloud proxy server.

Loadbalancer is needed for APM 10.7 and lower agents (which are no longer supported). Otherwise
Execute this procedure if you want to migrate agents that are running on APM 10.7 and lower versions. For DX APM 11 and later versions, the cluster automatically performs load-balancing.

You will be using a 2x.x Agent (Latest is 24.2) So no loadbalancing.xml is needed

1.3 Network Requirements for Cloud Proxy

- network requirements for cloud proxy server
The above link talks about the general requirements.

The only explicit network requirement is
the ports used . 
apm.server.port
Default: 5001
apm.server.httpPort
Default: 8081
apm.server.securePort
Default: 5443
apm.server.secureHttpPort
Default: 8444

1.4 Optimize Cloud Proxy Network Performance

Please see
Optimize CP Network Performance

Optimize Network and CPU Performance
Use the apm.server.compressionLevel in the application.yml file to configure the compression level for WebSocket communication between Cloud Proxy and Gateway. You can set any value from 0 to 9. It balances the amount of data and CPU usage. For example,
apm.server.compressionLevel: 1
The following are the applicable values:
6: Default value
1: To achieve the constant network speed for Cloud Proxy, but this may slightly increase the network traffic.
9: Use for best compression
0: No compression. It is recommended not to use this value as it increases the amount of data, and CPU improvement is minimal.
Restart the CloudProxy after each configuration change.
Distinguish Cloud Proxies

 

1.5  Procedure to install the Cloud Proxy application on a new Windows Server

See Configure CP for Windows

 

1.6  Cloud Proxy High Availability

HA with Cloud Proxy

Cloud Proxy is a standalone service running in a customer host OS environment. OS service manager or a third-party application is required to ensure instance availability. Cloud Proxy provides a liveness probe through HTTP and HTTPs endpoints under /supportability/health. A load balancer can be put in front of DX APM Cloud Proxies to achieve high availability. The load balancer ensures that agent reconnects are routed to an available instance. The load balancer also balances the number of connections between the instances.