So we've done APM. Now what?

437 views

Published on

When APM came to the forefront five or so years ago, we all thought we’d finally found the answer to our visibility challenges. Almost every organization implemented some form of APM. The truth is these solutions, for the most part, delivered. APM today is doing exactly what it’s supposed to be doing. But it is still not enough.

APM has fallen short in two separate areas. One is not addressing the multitude of data – in addition to the metrics gathered by APM solutions – that must be analyzed to determine application health. The second is the failure to predict the global shift from an ITIL-based IT Ops strategy to a DevOps/Application Support structure; from silos of information to a merged architecture where everyone has access to the data and views they need.
APM is now just a piece of an end-to-end visibility and control solution.

In this webinar, Rodney Morrison, SL's VP of Products, discussed the disillusionment of APM, and did a walk-through of several use cases of companies who are leading the way to the new era of end-to-end visibility and control of their critical applications and infrastructure.

Learn how these companies are able to:
• See only the events that matter to them with enough context to show why they matter
• Provide access to end-to-end, time-correlated monitoring metrics for faster troubleshooting
• Enable custom, real-time holistic views of application configuration, dependencies and data flows for more intuitive understanding of application performance
• Automate manual processes such health checks and stop and start scripts to work faster and reduce errors

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
437
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • RTView Enterprise Monitor is packaged together with RTView Classic, which allows for deep customization of Enterprise Monitor, including the creation of custom Solution packages. Separately entitled Solution packages are available, covering a variety of different technologies that may be part of your application architecture.
  • For an organization to successfully adopt a common end to end monitoring platform it has got to be flexible. Otherwise business units will stray from the solution and defeat the cost saving intent for reducing the number of point solutions.At the heart of RTView Enterprise Monitor is RTView Classic which is a product that has been used for over a decade for rapid development of real-time information systems.RTViewClassic is used to create custom views for Enterprise Monitor, Custom Solution packages to bring data and events from specific technologies or monitoring tools, and custom alert rule templates. Solution packages come with a wide variety of predefined alert rule templates. Alert rule templates allow one rule definition to apply to many monitored configuration items in EM. Once an alert rule template is created, end users can configure a global alert threshold to apply to all configuration items as well as overrides for specific items. Those alert templates can be managed from the EM alert administration console to set thresholds, overrides, enable/disable and activation policies dynamically at run-time without requiring rule base updates to the system.
  • So I am going to go over fairly quickly two uses cases today. One from a small organization and one from a very large IT organization. The first one is a small to medium logistics firm which manages transportation and shipping of goods worldwide. To manage those processes they have applications running on 200 Virtual Machines. Their application architecture includes Oracle Weblogic, Oracle RAC DB, Oracle Coherence,TIBCOBusinessWorks, TIBCO EMS, and TIBCO BusinessEvents.Prior to implementing Enterprise RTView, they had HP OpenView and Foglight for looking at infrastructure metrics.They had worldwide support teams which were a combination of typical operations and app support and needed more visibility into their application architecture to better predict when issues were going to occur and have the data to repair them quickly.
  • Their end users could now view the available services in their organization and at a quick glance determine which service is going to be impacted the most by the current state of health of their infrastructure.
  • They can also look at the health state of a service over time, to see when the service was in a critical condition, and whether that has been trending toward worse service levels or is perhaps cyclical.
  • Each service can also be viewed by the types of supporting infrastructure it depends on and whether any of those components are in a state of performance degradation.
  • Once a service or a component of a service has been identified as in a state which might cause performance issues, users can drill down and look at the important performance metrics across the time range of concern.
  • In a few week the Devops teams now have end to end visibility of all supporting architecture components in production test and dev environments. These teams heavily used service and component level criticalities to better fine tune the summary service heatmaps so that they properly indicate which issues must be addressed first. The also implemented notification for service alerts which indicate a combination of critical events that will be sent to the party responsible for that service.In the future they also plan to implement the ability for entitled users to instigate complex restarts from the monitoring interface to resolve issues when discovered
  • The next use case is a very large IT organization which first began implementing RTView EM for the Investment Bank and then after successes there moved on to implement the solution for the Retail bank.There are 10 to 20 major departments in this organization with 100s of applications and roughly 90,000 hosts. Initially Operations used Tivoli, Netcool and Ganglia to monitor infrastructure metrics. The application teams did a variety of things including runbook procedures each shift, in-house solutions, APM tools and SMS/Email notifications from the Ops teams. Typically those were not used as much because there was just too much noise for them to be useful.Their main problem was that the app support teams were not effective enough in reducing downtime and not cost effective.
  • Their end users could then get a heatmap which was filtered by role to show only the service which the role was responsible for
  • App support teams act like NOC teams, in that they have very specific alert lists that are filtered only for the areas of their concern and they can own, suppress or close those alerts from the management console. They can also optionally view the alerts being handled by the infrastructure teams, if that helps analysis.
  • Now most major department areas have end to end role based views for operations and application support teams. Individual business units are happy because they can extend the centrally provided solution and are not stuck with limitations on data or visualization necessary for analysis. Hundreds of support team members world wide readily adopted the new solution and work flow with success.Upcoming enhancements to the system included new performance data and integration with ServiceNow.
  • So to conclude, RTView is extremely flexible which is important when you need to fine tune the data you need to present and analyze to efficiently cover your monitoring needs. Its scalable and manages large data sets, which allows you to determine exactly the granularity and history necessary to optimize your application performance. And it provides Service Health, Event correlation and management and Drilldown to metrics in a role based fashion. And that is extremely important to make your support teams efficient at being aware of issues that are in their domain and not have additional noise to filter out when trying to do analysis.
  • So we've done APM. Now what?

    1. 1. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.1 So We’ve Done APM, Now What? Rodney Morrison - VP of Products, SL Corporation End to End Visibility
    2. 2. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.2 Webinar Agenda • What is APM? • APM limitations • Disruptive technologies and Monitoring Trends • End to End Visibility • RTView Enterprise Monitor • Use Cases
    3. 3. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.3 What is APM? • End User Experience • Transaction Monitoring • Deep Dive • Other features – Topology mapping – Analytics
    4. 4. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.4 APM limitations • Point solutions targeted to an application architecture • Don’t include all relevant data • Disruptive technologies like cloud make them obsolete • Need to be integrated into a general monitoring solution
    5. 5. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.5 Monitoring Trends – Disruptive technologies • Open source and low cost infrastructure monitoring tools • Cloud platforms • Devops • Big Data / Application Performance and Availability • Analytics
    6. 6. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.6 Monitoring Trends – Disruptive technologies • Open source and low cost infrastructure monitoring tools • Cloud platforms • Devops • Big Data / Application Performance and Availability • Analytics
    7. 7. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.7 Monitoring Trends – New Requirements • Reduce operational costs for support teams • Reduce number of point solutions in organization • Make teams more productive – Enable teams to share information with transparency – Provide teams with focused information to do their job – Automate remedial action
    8. 8. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.8 What’s Next ? – End to End Visibility • Incorporate all performance data – Infrastructure, network, middleware, application, APM • Performance data management and storage • ECA – Event correlation and analysis • Service Model • Role/environment based for devops models
    9. 9. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.9 RTView Enterprise Monitor Central Server Presentation Layer Your Systems Existing Monitoring Tools Infrastructure Middleware Custom & Packaged Apps CMDB Alert Definitions Dependency Mapping Reporting Solution Packages Java Clients REST Interface History SQL Notifications Alerts Email VoicemailSMS Historian Browser Clients Desktop TabletMobile Phone Alert Server and Directory Config Server Display Server SL RTView Enterprise Monitor Architecture TIBCO EMS TIBCO BusinessWorks TIBCO BusinessEvents Oracle WebLogic Server IBM Tivoli Netcool Oracle Coherence VMware vSphere Many More + Custom SPs
    10. 10. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.10 RTView Enterprise Monitor VMware Amazon EC2 System Metrics Generic JVM Apache/ Tomcat IBM Websphere RTView Enterprise Monitor ~ Collects, analyzes and visualizes data from multiple disparate sources Oracle Glassfish Oracle WebLogic Oracle Coherence TIBCO EMS (JMS) TIBCO BusinessWorks TIBCO BusinessEvents Custom Packages TIBCO ActiveSpaces RTView Classic and many more...
    11. 11. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.11 RTView Classic • Custom Views • Custom Solution Packages • Custom Alert Rule Templates
    12. 12. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.12 Case Study – Logistics Firm • ~100 Virtual machines (VMWare), TIBCO, Oracle • HP OpenView/Measureware and Foglight/ESX • 24/7 combo ops/dev support team needed to increase efficiency, reducing incidents and time to repair
    13. 13. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.13 Central Config Server Historian Browser Clients RTView Enterprise Monitor Central Display Server VMWare Oracle Weblogic Oracle DB Central Alert Server and Directory TIBCO BusinessWorks TIBCO EMS TIBCO BusinessEvents
    14. 14. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.14 Service Heatmap • Provides information about Service health
    15. 15. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.15 Service History • Provides information about Service health over time to expose patterns.
    16. 16. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.16 Service health by supporting components • Provides information about whether a component is used and the Service health of the component
    17. 17. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.17 Drilldown • Users can then drill down to look at gathered metrics relevant to a service for analysis of behavior
    18. 18. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.18 Case Study – Results • Support teams now have end to end visibility of all supporting architecture components of their services • Heavily used service and component level criticality indicators • Implemented Notifications for Service alerts which indicate a combination of critical conditions which would be sent to the responsible party • Plan to implement automation for complex restarts of services.
    19. 19. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.19 Case Study – Large Investment & Retail Bank • 10-20 Departments, 100s of applications, 90,000 hosts • Ops – Tivoli/Netcool, Ganglia • Application support – Runbook, in-house solutions, APM, SMS/Email notifications from Ops • Problem – App support teams not effective enough in reducing downtime and not cost effective
    20. 20. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.20 Central Config Server RTView Enterprise Monitor Historian Browser Clients Devops - Customization with RTView Builder Central Display Server Tivoli/Netcool Ganglia APM tools Central Alert Server and Directory Satellite Display Server Messaging Autosys Satellite Alert and Directory Server RTView Builder Logfile Runbook
    21. 21. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.21 Health State By Department • Top Level Heatmap indicates health state across an entire enterprise • Colors indicate impact alerts have on supporting apps and services
    22. 22. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.22 Alert Management • Role based alerting let teams filter out alerts they are not directly responsible for and manage their resolution.
    23. 23. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.23 Case Study – Results • Major Department areas now have end to end view • Departments have extended their solution for specialized views, additional performance data and automation • 100s of support team members world wide readily adopted new solution and work flow with success • New work includes integration with ServiceNow
    24. 24. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.24 RTView Enterprise Monitor End to End Visibility • Flexible • Depth in Middleware monitoring • Scalable for large performance data collection • Provides Service Health, Event correlation and management and Drilldown to metrics in a role based fashion.
    25. 25. © 2012 SL Corporation. All Rights Reserved. © 2013 SL Corporation. All Rights Reserved.25 RTView Enterprise Monitor Questions ?

    ×