1. APPLICATION PERFORMANCE
MONITORING FRAMEWORK
AND EVALUATION APPROACH

2. 2
 Components of an Application Performance
Monitoring (APM) Framework
 Approach to evaluating an APM Framework
 Example Shared Service offering
Objective/Agenda

3. Components of an APM Framework

4. 4
 The APM Framework is defined by five distinct
dimensions of, or perspectives on, end-to-end
application performance.
 While each of these five perspectives are distinct
and often deployed by different stakeholders, true
insight into application performance is only gained
through interaction and interlocks between these
perspectives.
Definition of an APM Framework

5. 5
1. End User
Experience
End to End Performance
2. Runtime
application
architecture
HW, SW and the
communication between
them
3. User-defined
transaction
profiling
Real and synthetic
transactions
4. Application
Context Monitoring
Resources consumed by the
application thru the
interaction with HW and
SW
5. Analytics
Proactive identification
and remediation of issues
either automated or
manual and Capacity
Planning
APM Framework Components
How the user
views
performance
How IT groups
view
performance
How the
business views
performance
What REAL
performance
is
What IT does
to fix
performance
issues
Key Takeaway: Framework components are additive and deployment of each
component provides additional insight into application performance

6. Evaluation Approach

7. 7
 Create a current inventory of existing Application
Performance Monitoring tools in use
 Identify areas of overlapping or redundant
capabilities and gaps in APM Framework
components
 Provide options on an integrated APM Tool Suite
 Propose a set of shared service offerings for APM
 Monitoring, alerting and dashboards
Evaluation Objective

8. 8
 Information Security Office
 Enterprise/Solution Architecture
 Technology/Infrastructure Services
 Servers, Storage, Network
 IT Service Management
 Service Desk
 Incident, Change, Problem, Release Management
 Application Support Groups
Suggested Participants

9. 9
• Distribute overview
and pre-work
• Interviews with
Stakeholders
• Compile Interview
results
Identify Current
Situation
• Analyze inventory
against APM
Framework
components
functionality
• Evaluate against
Gartner Magic
Quadrant
• Create Map/Gap
Analysis outcome
Conduct Map/Gap
Analysis
• Outline options on
creating Integrated
APM Tool Suite
• Invest, Remain,
Replace, Retire
alternatives for
APM tools
Create Options
for APM suite
• Create a proposed
set of APM shared
service offerings
Proposed Service
Offerings
Evaluation Process

10. 10
 Application inventory/list categorized by criticality -
Tier 1,2, 3
 Monitoring tools inventory/list for:
 Server
 Storage
 Network
 Database
 Services
 Application Framework - .Net or Java
 Transaction monitoring – real or synthetic
Pre-work from Participants

11. 11
 Low-hanging fruit is typically found in Runtime
Application Architecture (Infrastructure Monitoring) area
– Ping, CPU, Disk and Memory
 Start with agentless monitoring as this tends to be an
easier hurdle to overcome than agent based monitoring
 Dashboards provided to customers show both their
applications and the infrastructure they are hosted on
 Crawl, walk, run - grow shared service offerings based
upon customer need/demand
Findings from Other Clients

12. Examples

13. 13
Proposed APM Shared Service
Offerings
Foundational Elements
Runtime Application Architecture, Alerting and Dashboards
Application
Context
Monitoring
User Defined
Transaction
Profiling
End User
Experience
Incident
Ticketing
Tier 1
Mission Critical
Application
Context
Monitoring
User Defined
Transaction
Profiling
Tier 2
Business Critical
Incident
Ticketing
Incident
Ticketing
Tier 3
Business Important
Widespreadbusinessstoppage.
Significantexposureforcustomer’spublic
reputation.Possiblefinancialimplications
Businessstoppagebutworkaroundsexist,
Moderateexposuretocustomer’spublic
reputation.Possiblefinancialimplications
Littletonobusinessstoppage.Littletono
exposuretocustomer’spublicreputation.
Littletonofinancialimplications