Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Wug application monitoring and analytic

155 views

Published on

WebSphere Integration User Group Application Performance Monitoring presentation

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Wug application monitoring and analytic

  1. 1. © 2015 IBM Corporation1 IBM Systems - Middleware Application Monitoring and Analytics Stephen Ferguson, Senior IT Specialist Stephen.ferguson@uk.ibm.com
  2. 2. © 2015 IBM Corporation2 IBM Systems - Middleware Agenda APM Overview APM Challenges Identifying Root Cause Across Multiple Components Key APM Capabilities Integration Middleware Resource Monitoring WebSphere Deep Dive Diagnostics How Can Analytics Help
  3. 3. © 2015 IBM Corporation3 IBM Systems - Middleware Understand the end-user experience Follow changing workloads Mobile devices & smart endpoints Private, public & hybrid clouds Highly virtualized applications, storage & networks Discovery Visibility into application resources End User Experience Transaction performance monitoring to ensure SLA compliance Transaction Tracking Rapid problem isolation through transaction path analysis Diagnostics Domain-specific operations tools for diagnosis and repair Predictive Analytics Proactive Management to reduce outages & improve business performance shared data & common services See steps across the cloud Application Performance Management provides: Application Performance Management provides the actionable insights required to optimize performance, manage risk, and reduce costs in your application environment
  4. 4. © 2015 IBM Corporation4 IBM Systems - Middleware IBM Performance Management Portfolio Code level visibility into your applications and the health of your application servers. Find performance bottlenecks in application code. End user experience and resource monitoring of servers, web servers, application servers, databases and cloud workloads. Application Developer End user experience, transaction tracking, and resource monitoring of all your application components. The best option for managing your critical applications in production. IBM Monitoring IBM Application Diagnostics IBM APM  Ensure every client experience is great, by isolating application performance bottlenecks.  Gain visibility into complex business processes that encompass the entire IBM middleware stack.  Avoid outages by knowing what parts of application’s infrastructure are not working right.  Recognize customer slowdowns with end user monitoring.  Troubleshoot and resolve issues with from a single UI with integrated analytics.  Isolate what lines of code are impacting application performance.  Spend less time debugging with log files and obscure help desk tickets. Eric the Application Developer Olivia the Application Owner Deployable On Cloud, On Premises, or Hybrid (both combined) Kevin the IT Operations specialist
  5. 5. © 2015 IBM Corporation5 IBM Systems - Middleware APM Challenges
  6. 6. © 2015 IBM Corporation6 IBM Systems - Middleware APM Challenges  Understanding Application Topology – Some environments are static with single point of failure – Some environments are clustered and highly redundant – Some environments have auto-scaling – Some environments run in hybrid environments  Response Time – Ultimately, the health of the infrastructure components is not very important if the application response time is good. – Conversely, component health may look good, but end users may be experiencing slow performance – It is critical that end user experience be good and meet SLAs.  Monitor key resources including infrastructure and middleware and: – Know when a component is unhealthy. What is the right threshold? – Get the expected behavior from the developers and lines of business. They either don’t know or you don’t have the time to gather requirements
  7. 7. © 2015 IBM Corporation7 IBM Systems - Middleware Identifying Root Cause Across Multiple Components
  8. 8. © 2015 IBM Corporation8 IBM Systems - Middleware General Approach 1. Start with Response Time Monitoring – Add Java Script Injection for end-user experience 2. Monitor the Infrastructure including hypervisors 3. Resource Monitoring of key infrastructure Components 4. Discover Topology via Transaction Tracking and monitor instance level transactions 5. Synthetic Transactions 6. Diagnostic Deep Dive 7. Add Analytics
  9. 9. © 2015 IBM Corporation9 IBM Systems - Middleware Adoption Model: Getting started quickly with a clear path to deeper insight Increase visibility into component KPIs, faster problem diagnostics Add application agents 50% reduction in MTTR ClientValue True End-to-End Monitoring Increased Visibility Start Simple No visibility Reactive, ad- hoc and slow to repair Avoid real user impact with early warning of performance problems Robotic Monitoring Avoid outages by up to 40% View end user experience. 98% improvement SLA compliance. Real User Monitoring Hours Days Weeks View status of key application and lines of business APM/UI Find sporadic, difficult-to-isolate problems Expanded Agent- based Transaction Tracking where appropriate Effort with IBM’s SmartCloud Application Performance Management Predict hot spots, Customer behaviour, Capacity requirements Predictive Analytics Reduce capacity related outages by 68% Fast approach to discover and view topology and isolate problems Agentless transaction topology Eliminate Bridge calls; finger-pointing!
  10. 10. © 2015 IBM Corporation10 IBM Systems - Middleware Without Application Performance Management With Application Performance Management 1. You don’t know there is a problem until your users complain 1. Identify performance issues 2. It’s hard to figure out where the problem is occurring 2. Isolate where the problem is occurring 3. Finding the cause and resolving a problem costs time, people, and resources 3. Find the root cause of the problem Application Performance Management When there are outages or slowdowns, users are affected ? ?? ? ?
  11. 11. © 2015 IBM Corporation11 IBM Systems - Middleware Continuous monitoring with APM Know your end users Key visibility into your end users and app performance to optimize User Experience and speed up cycle times Diagnose problems 90% faster Deep, detailed diagnostics to resolve application issues quicker and spend more time innovating Reduce Outages by 50% or more Predict performance before going live and maintain full visibility into your hybrid applications Improve Availability by 60-90% Dev, Test and Ops collaborate over a single platform to optimize the performance of production applications Intelligently spot performance issues and resolve problems in your applications and infrastructure to keep your revenue flowing. Develop /test Steer Deploy Operate Learn more at IBM Service Engage
  12. 12. © 2015 IBM Corporation12 IBM Systems - Middleware Keys to Successful APM  Dev, Operations, and Lines of Business MUST be looking at the same metrics. – Think about the following scenario: • Operations is debugging a problem. They see a Warning in their console saying that Garbage Collection rates are high. They are looking at a metric that discusses the number of GC’s per minute. The number is 237 • The problem is handed off to the LOB SME. They have their own favourite WebSphere monitoring tool and report the number of GC’s, but it reports it as a count over a 10 second period. The number is 37 • Finally, the LOB SME can’t resolve the problem and hands off to the application developer. The developer brings up a different deep dive tool and see’s the number of milliseconds spend doing GC. Note: All 3 personas are looking at different values and spend a lot of time trying to explain what they are seeing. Time is wasted with each person trying to explain what they are seeing.  Logging is key when developing applications: – You must define a tracing standard so that it is easy to parse out error message from the logs and easy to look up diagnostic codes – Define a log standard and stick to the standard – With the growth of log analytics, this is even more important to have good diagnostic content. Good timestamps. Include time zone data in timestamps or use UTC time – Don’t forget that application performance data can be logged. When logging performance data, time sequencing is important for analytics.
  13. 13. © 2015 IBM Corporation13 IBM Systems - Middleware Keys to Successful APM  Discovery of Business Application Topology and Resources – With auto-scaling and provisioning tools, you must ensure that all components are monitored and you understand the relationships to assess a problem. – All servers/middleware must be monitored as soon as they are provisioned – Using Transaction Tracking capabilities, we can automatically detect application topologies for .NET and J2EE based applications. – Tivoli Application Dependency Discovery Manager (TADDM) can do a much deeper discovery including network and storage components
  14. 14. © 2015 IBM Corporation14 IBM Systems - Middleware Keys to Successful APM  Leverage Analytics for early identification of problems and faster diagnosis. – Log Analytics helps you understand the patterns that are affecting the business application • You might find that 30 percent of your problems over the past few months have a single root cause – Use Expert Advice to search for solutions to the problems • It is key to have good log data available via the a knowledge base that is accessible to the Log Analysis server  Predictive Insights for multi-variant analysis of metric data – Stream time sequenced performance data into Predictive Insights – Early identification of anomalies – Understand which performance metrics have a relationship  Leverage Deep Dive Diagnostics to tune applications before going into production  With workloads like auto-scaling capabilities, PureApp, IBM Cloud Orchestrator, IBM Workload Deployer (IWD), etc., embed monitor agents into the workloads so that monitoring is in place as soon as the workload is provisioned.
  15. 15. © 2015 IBM Corporation15 IBM Systems - Middleware Key APM Capabilities
  16. 16. © 2015 IBM Corporation16 IBM Systems - Middleware Monitor Response Time – Monitoring Response Time • Monitor the performance of the application by monitoring web traffic • Run synthetic transactions to ensure that consistent and good performance is happening from multiple locations • Monitor end user experience via Java Script Injection or IBM HTTP Server Response Time module • Best at monitoring web traffic, but can monitor other traffic
  17. 17. © 2015 IBM Corporation17 IBM Systems - Middleware Synthetics and Resources – Monitor key OS, hypervisor, and middleware metrics – Data gathered historically for reporting and for use in Capacity Planning – Be able to threshold on important metrics such as Heap Utilization after GC – ITM v6 has Synthetic Response Time monitoring. Version 8 will have synthetic capabilities later in the year.
  18. 18. © 2015 IBM Corporation18 IBM Systems - Middleware Transaction Tracking Application Topology Instance Topology  Includes timing for each segment Double Click to Drill Down
  19. 19. © 2015 IBM Corporation19 IBM Systems - Middleware Detailed Resource Monitoring
  20. 20. © 2015 IBM Corporation20 IBM Systems - Middleware Integration Server Status
  21. 21. © 2015 IBM Corporation21 IBM Systems - Middleware Message Flow Drilldown (top half)
  22. 22. © 2015 IBM Corporation22 IBM Systems - Middleware Message Flow Drilldown (bottom half)
  23. 23. © 2015 IBM Corporation23 IBM Systems - Middleware Processing Node Drilldown
  24. 24. © 2015 IBM Corporation24 IBM Systems - Middleware Queue Manager Status
  25. 25. © 2015 IBM Corporation25 IBM Systems - Middleware Transmission Queues Drilldown Click on the “Transmission Queues – Top 10 By Depth” widget on the MQ Widgets Overview page to drill down to the details of the transmission queues NOTE: Only the top 10 are shown on the widgets overview page, but all transmission queues will be shown here in the drilldown
  26. 26. © 2015 IBM Corporation26 IBM Systems - Middleware Queues With High Depth Drilldown Click on the “Queues with High Depth– Top 5” widget on the MQ Widgets Overview page to drill down to the details of the queues NOTE: Only the top 5 are shown on the widgets overview page, but all queues with high depth will be shown here in the drilldown
  27. 27. © 2015 IBM Corporation27 IBM Systems - Middleware Queues Not Being Read Drilldown The design of this page is similar to the “Queues With High Depth” drilldown except only queues showing an “Inputs Open” value of 0 are displayed NOTE: Only the top 5 are shown on the widgets overview page, but all queues not being read will be shown here in the drilldown
  28. 28. © 2015 IBM Corporation28 IBM Systems - Middleware Channels Not Running Drilldown Click on the “Channels Not Running– Latest 5” widget on the MQ Widgets Overview page to drill down to the details of the channels NOTE: Only the latest 5 are shown on the widgets overview page, but all channels not running will be shown here in the drilldown
  29. 29. © 2015 IBM Corporation29 IBM Systems - Middleware Indoubt Channels Drilldown Click on the “Indoubt Channels– Latest 5” widget on the MQ Widgets Overview page to drill down to the details of the channels NOTE: Only the latest 5 are shown on the widgets overview page, but all Indoubt channels will be shown here in the drilldown
  30. 30. © 2015 IBM Corporation30 IBM Systems - Middleware Queue Manager Events Drilldown Click on the “Queue Manager Events – Latest 5” widget on the MQ Widgets Overview page to drill down to the details of the queues NOTE: Only the latest 5 are shown on the widgets overview page, but all events during the set time span (4hrs by default) will be shown here in the drilldown
  31. 31. © 2015 IBM Corporation31 IBM Systems - Middleware Listeners Not Running Drilldown Click on the “Listeners Not Running – Latest 5” widget on the MQ Widgets Overview page to drill down to the details of the listeners NOTE: Only the latest 5 are shown on the widgets overview page, but all listeners not running will be shown here in the drilldown
  32. 32. © 2015 IBM Corporation32 IBM Systems - Middleware Critical MQ Errors Drilldown Click on the “Critical MQ Errors– Latest 10” widget on the MQ Widgets Overview page to drill down to the details of the errors NOTE: Only the latest 10 are shown on the widgets overview page, but all errors during the set time span (4hrs by default) will be shown here in the drilldown
  33. 33. © 2015 IBM Corporation33 IBM Systems - Middleware Deep Dive Diagnostics
  34. 34. © 2015 IBM Corporation34 IBM Systems - Middleware Deep Dive Diagnostics  Who needs Deep Diagnostics? – Software Developers: • Optimize their code • Find problems in code logic by finding long running methods • Tune and optimize before Software goes into production • The cost of finding problems before a product goes into production is – Operations/SME’s • When a problem occurs that can’t be isolated using Resource metrics, enable deep dive diagnostics  Key data: – Request Sequence including timings – Stack Trace, Methods, Context  When required, 100% transaction capture  Tunable to collect the right amount of data when needed
  35. 35. © 2015 IBM Corporation35 IBM Systems - Middleware Deep Dive Diagnostics  Websphere  .NET  Ruby  Node.js WebSphere Requests: Click on View Request Sequence to drill down Yes indicates that there is deep dive data
  36. 36. © 2015 IBM Corporation36 IBM Systems - Middleware Deep Dive Diagnostics  This is the request sequence for the individual request that was selected.  You can see that we capture the Event Type (servlet, method, EJB, JDBC, web service, portal)  The CPU Time is captured for each event type as well as the event name
  37. 37. © 2015 IBM Corporation37 IBM Systems - Middleware Deep Dive Diagnostics  Request Stack Trace for WebSphere including Method Summary – Note: Servlets will show request context, but no stack trace Select a method, EJB, JDBC, Web Service, Portal, and view the Stack Trace
  38. 38. © 2015 IBM Corporation38 IBM Systems - Middleware How Analytics Can Help
  39. 39. © 2015 IBM Corporation39 IBM Systems - Middleware Application Performance Management Event Management Applications | Systems | Workloads | Wireless | Network | Voice | Security | Mainframe | Storage | Assets Business Outcome Capabilities IBM Big Data Platform IBM or 3rd Party Solutions Operational Environment System & Log Monitoring Optimize Optimize across your IT app infrastructure Search Search quickly across massive amounts of data Faster Problem Resolution via Search Predict Predict problems before they occur Proactive Outage Avoidance Optimized Performance RaveSPSS InfoSphere BigInsights WatsonStreams Cloud Insights IBM SmartCloud Analytics Introducing IBM IT Operations Analytics Capabilities
  40. 40. © 2015 IBM Corporation40 IBM Systems - Middleware Uses fully automated behaviour learning algorithms to establish “normal”. Then applies real-time assessment of current conditions, to detect anomalies as they are emerging and before they become service impacting Predict Challenge: Reacting to performance thresholds is not enough – to ensure your mission critical applications are always available 24X7, you must prevent outages by predicting problems before they become service impacting
  41. 41. © 2015 IBM Corporation41 IBM Systems - MiddlewareChallenge: To diagnose service problems in applications and the infrastructure supporting them involves analyzing incredible amounts of data Logs Metrics EventsDocs IT Operations App Support Service Desk Search and Visualize Normalize Consolidate Collect Insight Packs Search
  42. 42. © 2015 IBM Corporation42 IBM Systems - Middleware
  43. 43. © 2015 IBM Corporation43 IBM Systems - Middleware IBM Service Engage Find out more
  44. 44. © 2015 IBM Corporation44 IBM Systems - Middleware

×