EA3347 - Analyzing Application Performance Using AppSpeed

EA3347 Analyzing Application Performance using vCenter AppSpeed
Hemant Gaidhani, Senior Technical Marketing

Manager, VMware, Inc.
Disclaimer
This session may contain product features that are currently under development. This session/overview of the new technology represents no commitment from VMware to deliver these features in any generally available product. Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. Technical feasibility and market demand will affect final delivery. Pricing and packaging for any new technologies or features discussed or presented have not been determined.
These features are representative of feature areas under development. Feature commitments are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. Technical feasibility and market demand will affect final delivery.
Copyright 2009 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents.
Overview
Understanding performance troubleshooting and monitoring Traditional performance monitoring AppSpeed approach AppSpeed deployment considerations Performance analysis methodology
Managing Performance with Service Levels
Requirements Vendors Guarantees System Managers
Service Level Agreements Business Users
Measurements Policies & Controls Application System Real User Experiences
Feedback Driven Resource Control Loop

Sometimes human feedback, sometimes automated Throughput Response Time Wait-analysis
Application
Performance Metrics
Limits Proportions Rates #instances Bandwidth Priority
Resource Controls CPU, Memory Disk, Network
Goals And Policies
Priority Deadline Velocity Throughput
Measurements
Business Units Prescribe Operational Criteria
Performance is described in business or end-user terms Examples include:
Response time Transaction Throughput
Traditional Performance Management

Service levels are sometimes measured by user application Measure of performance is done by proxy of resource utilization E.g. CPU is at 60% utilization, so my system must be performing well
Shortcomings of Resource Utilization Methods

Have to guess about the impact of a resource on response-times Problems may occur anywhere in the stack (e.g. storage)
Layers of a Typical End-to-end Stack
Goal: 0.50s Actual: 1.50s
Load Bal.
Web
App
SQL
Does this CPU peak cause this response time issue?
Users measure response-times Administrators measure utilization
How can we create a bridge?
Distributed Applications Pose Additional Challenge

A A
Transaction A
0.04
0.05
A A
2.10s
0.05
A
1.02
A
1.87s
0.03
0.04
Web Svr VM
Tier 1
App Svr VM
Tier 2
DB VM
Tier 3
The key is to connect the sub-transactions into a stacked graph:

Web Svr VM
Transaction A
0.12s
1.11s
2.10s
App Svr VM DB VM DB VM
0.87s
The AppSpeed Approach

Start with user experience
What matters is not whether CPU is at 100%, but what performance users are actually Seeing
First investigate application level details

Which Tier is the culprit
Which VM is the culprit (is there one?) Which Transaction(s) is the culprit?
Then look further

Is it a resources issue? Is it related to the application itself?
VMware vCenter AppSpeed Architecture

VMware vCenter Server
vSphere Client or VI Client
AppSpeed Plug-in
AppSpeed AppSpeed Server Probe
AppSpeed Probe
VMware ESX/ESXi Host
VMware ESX/ESXi Host
vCenter AppSpeed - Architecture

Probe Probe
connects to vSwitches & monitors traffic connects to vSwitches & monitors traffic
UI integrated into vSphere Client
AppSpeed Server
Analysis performed by central server (virtual appliance)
vCenter Server
vCenter AppSpeed - Architecture

An AppSpeed Probe is a VM that is installed on a host to collect the information that AppSpeed requires. The AppSpeed Server processes data from probes and produces topology information, performance metrics
The Server configures the Probe, and the Probe sends it samples and aggregations of the data it processes.
Configuration
Server
VC Probe
Probe
Probe
Host 1
Host 2
Host 3
Sampled traffic and aggregated statistics
How Does it Work?

Amount of user traffic Deep inspection of real user traffic Network latency vs server latency
+
Identify and monitor applications and transactions
Response times & errors

Transaction SLAs
+
Correlate transactions across tiers
Application topology map

Source of latency
13
Context | (Virtual) Hardware Layer

Virtual Machines can run multiple Endpoints. An Endpoint is an instance of a network service, which runs on a specific IP and port (or port range). Endpoints serve application data.
Apache on 195.14.144.5:80
SugarCR M HTTP
Apache on 195.14.144.20:80 MySQL 5.1 on 195.14.144.20:33 06
SugarCR M MySQL DB
Host 1
Endpoints are sometimes called Servers
Context | Application Layer

Servers consist of multiple Applications, which can use different communication protocols.
SugarCRM HTTP
Outlook Web Access
MAPI Mailbox Server
SugarCRM MySQL DB
POP3 Service
Active Directory
SugarCRM (a web-based Customer Relationship Management system)
Exchange
Context | Application Layer

Applications consist of Transactions, which are defined based on the specific protocol. For example, HTTP Transactions are web pages, while DB transactions are queries.
SELECT * FROM contacts SELECT
SugarCRM HTTP
Contacts
Edit View
SugarCRM MySQL DB
contacts
SELECT name FROM contacts WHERE
INSERT sugardb Users SELECT
INSERT INTO contacts
Create
Accounts Delete
SELECT id FROM users WHERE name=
Context and Terms

End Point
protocol served by specific server (e.g. 10.0.0.30:80 serves http)
Transaction - a single application function

HTTP web pages, URL with or without parameters that are translated to a function of the application SQL - group of queries that shares the same logical structure (tables, columns, condition etc)
Hits
number of request + reply per transaction
Application
a collection of transactions per tier that represent a basic unit
Dependencies
Application Dependencies
Automatically maps dependencies between applications If a transaction from App A requires the execution of one or more transactions of App B then the system will mark App B as a dependency of App A
Transaction Dependencies
If processing of a transaction from A requires the execution of a transaction B then the system will mark transaction B as a dependency of transaction A
e.g. For example, does the FE transaction cause a DB query?
Application Server
Database Server
Analysis Scenarios I see a slowdown, so

Has the Load increased?
Is the app slow because the load increased?
Is the DB slow because the load increased? Is there another application that uses the DB?
How deep does the slowness go?

Is it only the app tier that is slow or also the DB?
Which VMs are slow?

Is the slowness seen on all VMs? On a specific VM only?
Which Transactions are slow?

Is there a specific transaction which is slow?
Providing Answers
All those questions (and more) are answered by AppSpeed
Performance monitoring of all VMs Performance monitoring of all Transactions
Plus Usage and Availability monitoring
Each question helps narrowing the problem

Where can the blame lie Where *doesnt* the blame lie
Either identify the cause or direct into what resources to look into
Analysis Methodology
1. Deploy AppSpeed
2. Verify AppSpeed is monitoring application traffic

3. Application discovery and mapping 4. Monitor application performance 5. Troubleshooting application performance 6. Setup proactive monitoring based on service levels
1. Deploy AppSpeed

Starting out
AppSpeed Deployment
Meet the installation requirements
Installation is a 3-step process

Server Installation and Configuration Plug-In Installation Probe Deployment
Make sure AppSpeed can monitor the application Post installation two options to run AppSpeed
Evaluation mode
Standard mode
AppSpeed Coverage
AppSpeed auto-discovery and mapping capabilities are bounded by protocols. The current protocols supported are listed below These protocols cover most Tier-1 applications and in general most multi-tier applications (.NET, J2EE, php, etc.).
Support for additional protocols (more databases, storage, remote desktops) is in the roadmap and prioritized per customer requirements.
HTTP, HTTPS Web Services MySQL MSSQL Oracle Exchange
AppSpeed Mapping Resolution

For each supported protocol, once discovery of servers and transactions is done, AppSpeed monitors performance and usage.
For HTTP, HTTPS and Web Services, AppSpeed maps the applications and transactions that participate in every application.
For Database protocols AppSpeed maps the databases, tables, methods and queries that are being used. For Exchange AppSpeed maps RPC commands.
HTTP, HTTPS Web Services
Applications Transactions
Exchange
MySQL
Transactions Databases
MSSQL
Tables
Oracle
Methods Queries RPCs
AppSpeed Deployment Considerations

Each AppSpeed Server can manage up to 32 probes
Each probe can be connected to number to vSwitches based on the number of vNICs assigned to the probe
Additional probes can be installed on the same ESX/ESXi host to allow monitoring of additional vSwitches Protocols not supported for
Virtual Desktop Infrastructure (VDI) DB2, PostGresSQL LotusNotes
AppSpeed does not perform auto-remediation to resolve performance issues
AppSpeed Run-time modes

Evaluation mode
Helpful when starting out
Only discovery and mapping, no performance monitoring Allows excluding servers from subsequent monitoring Resets current state, saves of existing performance metrics
Standard mode
Application discovery and mapping, and performance monitoring Captures and tracks all applications and servers Information overload Reach AppSpeed capacity limits
1. Deploy AppSpeed

Verify AppSpeed is Monitoring Application Traffic

3 different ways to ensure this
Real Time Statistics
Unmapped Traffic view Probes Management view
Need SSL Keys to monitor HTTPS traffic
Application and Server Mapping Unmapped Traffic

AppSpeed automatically detects environment through continuous learning process
Transactions will first appear in Unmapped Traffic view by VMs and protocols Mapped transactions appear in associated applications and servers in Inventory
Monitoring SSL Traffic

To monitor traffic on HTTP sites incorporating Secure Socket Layer (SSL) encryption, you need to configure the SSL Keys for each endpoint (IP address and port pair) where AppSpeed detects SSL traffic. To add an SSL key
In the SSL Management window, select the check boxes for the endpoints in the SSL Pending Endpoints table and click Add/Update SSL Key.
Browse to and open the key file. The key is assigned to the selected endpoints.
1. Deploy AppSpeed

Application Discovery & Mapping

Discovery and Mapping is an ongoing process
3 different ways to ensure this

Application Topology Maps Application to Server view Server to Application view
Application Topology Map
Server to Applications
1. Deploy AppSpeed

Application Performance Monitoring
AppSpeed Views: Slowest Transactions Identify Potential Bottlenecks

What transactions appear slow to end users?
Access by application Tracks slowest transactions for an application by measured response times
AppSpeed Views: Most Used Transactions Identify Transactions with Greatest Potential Impact
What transactions have the most occurrence?
Access by application Transactions appearing here and the slowest transactions will likely need triage
1. Deploy AppSpeed

AppSpeed Views: Transactions Associated Transactions per Application

Access transactions associated with each application by double-clicking appropriate application line in grid or chart
AppSpeed Views: Transactions Transaction Dependencies

Access dependent transactions by clicking on a transaction
Dependencies tab shows dependent transactions
Latency Breakdown
Use Case Finger Pointing and Performance Diagnostics
Latency Breakdown 101

Client Server
RTT
Latency
Application
Application
Infrastructure RTT
Latency = Network Overhead + Network RTT + Infrastructure + Application
Latency Breakdown Definition

Name
Application
Explanation
Measured from the time the server receives the beginning of the request until starting to transmit the reply.
Infrastructure
Measured from the time the server starts transmitting the reply until fully replying to the client's request.
Network Overhead
The cost of packets retransmissions, errors and drops.
Network RTT
The average round-trip time, without failures, from client to server.
1. Deploy AppSpeed

AppSpeed Service Level Management

AppSpeed has pre-defined service levels
OK
Warning Above SLA Unavailable
Application Service Levels
Threshold Settings
Activate SLA monitoring per application Suggestion of thresholds per application
Based on baselines and standard deviation calculations
Modification of thresholds
Event Viewing
Once a transaction crosses a threshold the system issues a basic event
Manage events based on objects, time, severity, etc.

View details of problem in event
Event Details
Alarms Management
Enable alarms for email notifications If alarms are activated and events meet alarm conditions they are gathered and sent via email
Conclusions and Observations

Historical process of performance analysis is manualintensive and requires tribal knowledge Existing tools enable low-level resource and latencybased analysis
AppSpeed extends set of metrics to improve latencybased analysis methods

VMwares automation will continue to improve to speed and simplify this process

EA3347 - Analyzing Application Performance Using AppSpeed

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

EA3347 - Analyzing Application Performance Using AppSpeed

Transféré par

Droits d'auteur :

Formats disponibles

EA3347 Analyzing Application Performance using vCenter AppSpeed

Hemant Gaidhani, Senior Technical Marketing

Managing Performance with Service Levels

Requirements Vendors Guarantees System Managers

Service Level Agreements Business Users

Measurements Policies & Controls Application System Real User Experiences

Feedback Driven Resource Control Loop

Limits Proportions Rates #instances Bandwidth Priority

Resource Controls CPU, Memory Disk, Network

Goals And Policies

Priority Deadline Velocity Throughput

Traditional Performance Management

Shortcomings of Resource Utilization Methods

Layers of a Typical End-to-end Stack

Goal: 0.50s Actual: 1.50s

Does this CPU peak cause this response time issue?

Users measure response-times Administrators measure utilization

How can we create a bridge?

Distributed Applications Pose Additional Challenge

The key is to connect the sub-transactions into a stacked graph:

The AppSpeed Approach

First investigate application level details

Then look further

VMware vCenter AppSpeed Architecture

AppSpeed AppSpeed Server Probe

VMware ESX/ESXi Host

VMware ESX/ESXi Host

vCenter AppSpeed - Architecture

UI integrated into vSphere Client

vCenter AppSpeed - Architecture

Sampled traffic and aggregated statistics

How Does it Work?

Response times & errors

Application topology map

Context | (Virtual) Hardware Layer

Apache on 195.14.144.20:80 MySQL 5.1 on 195.14.144.20:33 06

Endpoints are sometimes called Servers

Context | Application Layer

Outlook Web Access

MAPI Mailbox Server

SugarCRM (a web-based Customer Relationship Management system)

Context | Application Layer

SELECT name FROM contacts WHERE

INSERT sugardb Users SELECT

INSERT INTO contacts

SELECT id FROM users WHERE name=

Context and Terms

Transaction - a single application function

e.g. For example, does the FE transaction cause a DB query?

Analysis Scenarios I see a slowdown, so

How deep does the slowness go?

Which VMs are slow?

Which Transactions are slow?

Plus Usage and Availability monitoring

Each question helps narrowing the problem

2. Verify AppSpeed is monitoring application traffic

2. Verify AppSpeed is monitoring application traffic

Installation is a 3-step process

HTTP, HTTPS Web Services MySQL MSSQL Oracle Exchange

AppSpeed Mapping Resolution

AppSpeed Deployment Considerations

AppSpeed does not perform auto-remediation to resolve performance issues