Downloaded 23 times
Uploaded byTheo Jungeblut
Debugging,Troubleshooting & Monitoring Distributed Web & Cloud Applications at SoCal Code Camp San Diego (07/27/2013)
The document discusses debugging and troubleshooting in distributed web and cloud applications, emphasizing the differences between monolithic and distributed architectures. It highlights various tools and methods, such as Microsoft Intellitrace and AppDynamics, that aid in monitoring and performance analysis, while addressing the challenges developers face due to increasing complexity and data volume. It calls for a combined development and operations (DevOps) approach to improve visibility and success in application management.
Debugging,Troubleshooting & Monitoring Distributed Web & Cloud Applications at SoCal Code Camp San Diego (07/27/2013)
- 1. Debugging, Troubleshooting Distributed Web & CloudApplications San Diego, July 27th, 2013 SolCal Code Camp
- 2. Theo Jungeblut • Engineeringmanager & lead by day at AppDynamics in San Francisco • Coder & software craftsman by night • Architects decoupled solutions tailored to business needs & crafts maintainable code to last • Worked in healthcare and factory automation, building mission critical applications, framework & platforms • Degree in Software Engineering and Network Communications • Enjoys cycling, running and eating theo@designitright.net www.designitright.net
- 3. Warning • Contains alsoproprietary software • This areas are pointed out • Please walk away now, if that is not acceptable for you, it’s okay
- 4. Overview • Inquiry aboutthe Status Quo • Some Facts -> Dev Process & Ops Reality • Monolithic Applications • Debugging & Logging • Distributed Applications • Side Effects you need to troubleshot • Performance Counter • Microsoft IntelliTrace • AppDynamics • Summary • Q & A
- 5.
- 6. How agile areYou?
- 7. The Impact ofProcess * from Wikipedia: http://en.wikipedia.org/wiki/File:Agile-vs-iterative-flow.jpg
- 8. How many releases doyour company have a year?
- 9. Typical Releases aYear* 58% 17% 21% 3% 2+ months monthly weekly daily http://www.appdynamics.com/blog/2011/12/14/storm-clouds-in-2012-summary-of- appdynamics-apm-customer-survey/
- 10. Development + Operations= DevOps * from Wikipedia: http://en.wikipedia.org/wiki/File:Agile-vs-iterative-flow.jpg
- 11. Difference between Dev& Ops Dev • Getting / being agile: need for frequent updates with new feature and bug fixes • Achieves stability trough running latest Ops • Highest goal: stable execution flawless execution, by knowing the environment and software • Achieves stability through careful rollouts
- 12. “The Past/Present”* Web Server DBUser *or maybe still your present?
- 13. “The Past/Present” -Architecture Data Access Layer Business Logic Layer Presentation Layer DB
- 14.
- 15.
- 16. Traditional Debugging Advantages • Visibilityfor executed code path Disadvantages • Performance impact • Requires software installation • Often not possible in production • Typical does not find easily distributes issues • Only real time results
- 17. Log Files Advantages • Outputadjustable without restart • Accepted in Production Disadvantages • Manual, time intense creation of log statements • Manual, time intense process of result review • Limited scope & visibility • Potentially high performance impact based on IO
- 18. “The Present/Future”- Architecture MicrosoftMSDN: http://msdn.microsoft.com/es-es/architecture/gg189193
- 19. “The Present/Future” ASP.NET MVC 3/4 (IIS) User WASTomcat Azure Web Role SQL Server MySQL Active Directory Azure Worker Role WAS 3rd Party Web Services Java Application MongoDB 3rd Party Web Services WCF HTTP
- 20. The (Netflix) DistributedReality * * http://techblog.netflix.com/2012/06/netflix-operations-part-i-going.html
- 21. What has thisto do with Debugging and Troubleshooting?
- 22. Who does reallyknow how their application is performing?
- 23.
- 24. Concurrency http://en.wikipedia.org/wiki/File:Smithposter.jpg • Deadlocks • RaiseConditions • Unexpected complexity • …
- 25. Data Volume http://en.wikipedia.org/wiki/File:Smithposter.jpg • constantlyincreasing • Volume hides details • Handling volume impacts resources • …
- 26.
- 27. Who is Performance Testing everyrelease?
- 28.
- 29. Dev + Ops= Success • DevOps has to be a combined approach • Mostly no visibility in real performance & production state
- 30. IntelliTrace™ • “Flight Recorder”for your Process • Records configurable details • Allows offline analysis • Microsoft specific Tool in Visual Studio Let’s take a look http://msdn.microsoft.com/en-us/library/hh398365.aspx
- 31. Summary IntelliTrace Advantages • Allowsgreat visibility into single process/AppPool • Allows to play back test or production issue Disadvantages • Limited to Single Process / AppPool Visibility • Should be only temporally enable in production • Requires configuration effort for balance between details & performance
- 32. Performance Counter • Collectmachine wide and process specific data • Allows on- and offline analysis • Microsoft specific tool build into Windows http://www.codeproject.com/Articles/8590/An-Introduction-To-Performance-Counters
- 33. Summary Performance Counter Advantages •Huge OOTB support in Windows/IIS/etc. • Low overhead • Extensible Disadvantages • Collecting application specific data requires source code changes
- 34. AppDynamics • Application PerformanceManagement • Optimized for Production • Monitoring instead of investigating • Providing the “Right-Data” Let’s take a look http://www.appdynamics.com/products-editions.php
- 35. Summary AppDynamics Advantages • Worksin production on high performance sides • Monitors, Notify, Troubleshoot • Allows instance handling in cloud environments • Free lite version Disadvantages • Full version not free • Does not include every application detail
- 36. Build your ownOpinion (for Free) • Lite Version free but limited • 30 days free Trial of Pro & Azure Version http://www.appdynamics.com/products-free-download.php
- 37. Summary • Understand DevImpact to Ops Execution • Understand the business impact of production issues • Monolithic is simpler to Troubleshoot • Distributed is more complex • The right tools can make a Big Difference
- 38. Downloads, Feedback & Comments: Q& A Graphic by Nathan Sawaya courtesy of brickartist.com theo@designitright.net www.designitright.net www.speakerrate.com/theoj www. slideshare.net/theojungeblut
- 39.
- 40. … thanks foryou attention! And visit and support the www.sandiegodotnet.com Please fill out the feedback, and… www.speakerrate.com/theoj