CA APM Sizing and Performance

Recommendations for hardware sizing and configuration.
This guide contains recommendations for hardware sizing and configuration. Requirements vary dependent on the size of the environment being monitored, the level of monitoring (number of metrics collected) and the number of extensions and integrations included in the monitoring solution. The example recommendations for various typical installations provide figures for the minimum hardware outlay which ensures consistent good operation.
The sizing requirements for components in production environments, handling large numbers of metrics, can be multiple times greater than testing and development installations.
Follow these steps:
  1. Determine your sizing needs from reviewing the sizing and performance guidelines and using the APM Sizing Utility.
  2. Review and finalize the sizing details.
  3. Planning: Create a network diagram and list of application information. Create a logical diagram of your network, applications, and CA APM components. This diagram helps you to prepare for your deployment.
  4. Set up and configure hardware and virtual machines. Assign IP addresses, host names, and so on.
  5. Assign and train a CA APM administrator.
Docker Containers
APM is certified to run in Docker containers. You can use a combination of components installed normally and in Docker containers. Use one docker container for each component. You can have more than one container on one host. If you use Docker containers, you might need to increase some of the sizing requirements to deal with the overhead of the containers. For more information, see Docker Requirements.
Component Version Compatibility
These rules govern version compatibility among CA Introscope components.
  1. Enterprise Manager
    • The Enterprise Manager and the Workstation must be the same version. The Command-line Workstation must also be the same version as the Enterprise Manager.
      When you upgrade an Enterprise Manager, you install a new Workstation of the same version. This rule includes upgrades to service pack or patch releases.
    • All Enterprise Managers in a cluster must be the same version. This rule includes the MOM, all Collector Enterprise Managers, and the WebView Server.
  2. Enterprise Team Center
    The Enterprise Team Center server and providers must use this version of Enterprise Manager. Upgrade any earlier versions of Enterprise Manager to deploy an ETC monitored environment.
  3. Cross-Cluster Data Viewer
    The Cross-cluster Data Viewer must be the same version as the Collectors and clusters it connects to.
  4. Agents
    • Agents, AutoProbe or ProbeBuilder, and the Platform Monitor must all be the same version. If you upgrade agents, you also upgrade AutoProbe or ProbeBuilder, and Platform Monitors.
    • Agents can be either the same version as, or an earlier version than, the Enterprise Manager.
For complete component compatibility requirements, see Support and Compatibility.