What Is Monitoring?
Monitoring is the ability to capture resource metrics about target servers and network devices involved in CloudTest-generated tests. Monitoring provides information about how servers and other network devices (load balancers, routers, etc.) are handling the load being generated against the web application. Real-time monitored metrics are included in the CloudTest dashboards to help identify possible bottlenecks in the web application being tested. Monitored information is available at several different levels including system resources (i.e. CPU, network, disk, and memory utilization), processes (i.e. apache thread counts), and server specific information (i.e. application server JVM information, database commits/rollbacks, etc.).
CloudTest's monitoring feature may be implemented in one of two ways:
- Agent-less approach: The agent-less approach makes use of open network protocols such as SSH (secure shell), SNMP, and RMI, to connect to any remote server t hat you wish to monitor. Any CloudTest with access to the destination machine can capture resource information. This is the preferred method for capturing information on servers inside the same LAN as it does not require an installed application and has a minimal impact on performance.
- Agent-based approach: The agent-based approach is primarily for target servers that are behind the firewall, and does not require direct access from the CloudTest to the target server. Instead, the CloudTest Conductor, installed on the target server, creates an outbound HTTP(S) connection to CloudTest and provides the resource information. This approach is also required when interfacing with Windows performance counters.
- External Data Sources: You can also use external data sources such as New Relic, Dynatrace, AppDynamics, and CA Wily Interscope.