Presented at Gluecon 2014 by James Urquhart and Rob Dickinson of Dell.
"Mining" for application performance "gold" is harder than ever before. Applications are becoming parts of larger complex systems, and developers need to understand how the system behaves as much as how each application behaves.
Following transaction details is an excellent way of monitoring application performance in these systems, and triggering automation activities such as autoscaling and recovery.
2. Software Group
IntroducingDellSoftware
• QuestSoftware, Enstratius are the foundation
•Part of “World’s Largest Startup” with 110k people
•Sponsors at GlueCon and Velocity
•6 employees in Boulder (shameless hometown plug)
8. Software Group
How do we handle thiscomplexity?
Observe,Measure and Filter
Understand Intrinsic
Latencies
Understand the
Transaction Path
Understand User Behavior
Understand Resource
Contention
Improve Logical Complexity Tune, Balance, Scale
How are your tools andtechniques helping you dothis today?
10. Software Group
Applications Should be Definedby Activity
How doyoutroubleshootandassessproblemsin complex dynamicenvironments? How areactivities
identified andunderstood?
11. Software Group
System Complexity is Emergent/Entropic
WhataboutNoSQL?RoR?Ansible?AWS?(ormagic unicorns?)
Complexityis linkedwith marketsuccess, is driven bycustomers,contributors,competitors,investors,
partners,even time itself
Complexity doesn’t really fade,
but takes onnew forms
12. Software Group
CompleteDiscrete Transaction Traces
• Enduser data(navigation timing andfull content)
• Transactionpathandparametersandtiming
• Relatedbackendresources(databases,queues)
• Full detailofusersession in context
Web
server
App
server
DB
server
End users Internet Firewall
Traceand mergebeforeaggregation
Related Infrastructure
18. Software Group
The only way to ensure
resilienceat scaleis to
makeeachagent (or cluster
of agents) as“self-resilient”
as possible.
19. Software Group
In an automated system, provisioning, scaling,
failure tolerance, and disaster recovery are
different names for the same workflows
• The trigger for the workflow is the
distinguishing characteristic
• All are executions of the same workflows
addressing insufficient or excess computing
resources
• All tend to focus on at the workload level
20. Software Group
Anything you can monitor can serve as a
trigger for a scaling workflow
• Raw resource utilization
• Basic application metrics
• Understanding the transaction path
21. Software Group
Aggregated and/or discrete
transaction data can help identify the
proper workload to
scale/recover/etc.*
*No way of predicting exactly which measure
is best for all time
24. Software Group
How do we handle thiscomplexity?
Observe,Measure and Filter
Understand Intrinsic
Latencies
Understand the
Transaction Path
Understand User Behavior
Understand Resource
Contention
Improve Logical Complexity Tune, Balance, Scale
How are your tools andtechniques helping you dothis today?
You experience complex adaptive systems every day. In ecosystems…
Give an example of an end to end resolution that follow this path:
* Hi IO on one DB Shard due to a lot of users logging in and doing expensive activity
Give an example of an end to end resolution that follow this path:
* Hi IO on one DB Shard due to a lot of users logging in and doing expensive activity