User manual VMWARE APPSPEED SERVER 1.5

[. . . ] VMware vCenter AppSpeed User's Guide AppSpeed Server 1. 5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www. vmware. com/support/pubs. EN-000388-02 VMware vCenter AppSpeed User's Guide You can find the most up-to-date technical documentation on the VMware Web site at: http://www. vmware. com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware. com Copyright © 2010 VMware, Inc. VMware products are covered by one or more patents listed at http://www. vmware. com/go/patents. [. . . ] Prerequisites To view unmapped traffic on HTTP sites that incorporate SSL protection, you must first configure the SSL keys for each endpoint where AppSpeed detects SSL traffic. View the status information for the unmapped traffic. n n n n n Server: Name of the server. Latency: Average and standard deviation (STDEV) latency rates for the server or transaction. Hits: Total number of hits in the specified time frame for the server or transaction, and rate of hits per second. Throughput: Total throughput in the specified time frame for the server or transaction, and the average throughput. Errors: Average rate of errors, as a percentage, for the server or transaction. n n VMware, Inc. 23 VMware vCenter AppSpeed User's Guide 24 VMware, Inc. AppSpeed Topology Overview 3 The topology tables show the relationships between the services and servers detected on the network, and the dependencies between applications. This chapter includes the following topics: n n n "Analyze an Object, " on page 25 "Scalability Considerations for AppSpeed Monitoring, " on page 25 "Editing AppSpeed Topology, " on page 26 Analyze an Object You can select an object in the AppSpeed topology and view its details on the Analysis page. Procedure u Select the object in the topology table and click Analyze. The Analysis page for the selected service or server appears. Scalability Considerations for AppSpeed Monitoring AppSpeed is a real-time service performance tool that collects, analyzes, and stores substantial volumes of data per second. Various parameters affect AppSpeed performance. n n n n n The number of probes deployed The number of monitored services The number of monitored servers The number of transactions The volume of monitored network traffic The main factors affecting scalability in AppSpeed are the number of overall monitored objects and the number of transactions that are being monitored. AppSpeed reduces the number of transactions for each service as more services are mapped. This number can be reduced to as few as 50 transactions for each service. AppSpeed stops detecting new servers after the number of monitored servers exceeds 500, or the number of IP addresses and ports in the monitored network exceeds 3000. It also stops mapping new services if the number of monitored services exceeds 100. VMware, Inc. 25 VMware vCenter AppSpeed User's Guide Editing AppSpeed Topology AppSpeed maps servers and services topology from the network traffic monitored on the deployed hosts. You might want to change the topology, for example, to merge two separately mapped services or to view a single mapped service as two separate services, depending on the servers on which it runs. If you split, merge, or remap a service, the historical monitoring and configuration data of the servers or service roots, such as thresholds, is reset. You might also want to remove objects because they are obsolete or less relevant. Split a Service A service can be split so that it can be monitored as two separate services. For example, in a server-based scenario you might want to split the monitoring process of a service that is running on a staging server and on a production server, so that they are monitored as two separate services. A service is split according to either the server on which it is running, or on its service roots. A service root is a transaction, usually a database or a domain, in the service that all subordinate transactions have in common. For example, in a service root-based scenario, you might want to monitor two databases that were originally mapped under a single service, as two separate services. 5 6 In the confirmation dialog box, select the servers or service roots to split from the service. Type a name for the new service and click Split. Merge Services You can merge two or more services so that you can monitor them as a single service. [. . . ] To specify a date and time, rather than a preset time period, select Manual. 4 (Optional) To view the events for a specific service, select the check box of the service in the table and click View Details. a b In the view selection bar, click Events to see additional information for the service event you selected. (Optional) To display or hide transaction-specific events, select or deselect the Show Transactions check box. View Event Details You can view the details of a single event, including the key performance indicators of the object for which the event was generated. [. . . ]