�ݺ�ߣ

Editor's Notes

• #4: Multimodal dynamics in the enterprise are creating a disruption in application platforms, processes, and more. Organizations have multiple “gears” running, and only Dynatrace has invested to meet these new demands. <Nicolas’ notes below> What we see in our customer base is more of a “multi-modal” application environment than a simple bi-modal environment Apps of record need a unique monitoring approach – these are most often packaged apps – ERP, SCM, CRM, Mail, Directory Services and Vertical apps – SAP, Oracle Fin, Netsuite, SFDC, Workday, Microsoft Exchange/Office, Active Directory, Citrix/VDI, Epic, Guidewire, Windchill and so on. These applications do not lend themselves to container based instrumentation – but they must be managed. In fact, we see SLA focus increasing – and shifting – from inside-out, average and component health only to outside-in, with user and transaction level visibility required. As cost cutting continues around apps of record, tooling consolidation alongside up-leveling SLA management is fueling our DCRUM & Cloud Monitoring offerings. Right now, the transformation of apps of engagement is where the action is. We’re seeing (a) a shift from service-based apps and message buses, to containerized and API driven apps, including use of micro-services for certain new components, (b) an increase in “true DevOps”, from agile through continuous integration to continuous deployment and delivery, and (c) the acceleration of the business as an equal participant, and critical success factor, in app success, thirsty for more and more visibility and insight into user experience, behavior, conversion rates, entry and exit points – basically, the facts about every user journey, all the time, in real-time. Digital transformation initiatives are top down driven, the digital teams are expanding rapidly – Nike, GM, Citi, The Hartford – and they’re being led by appointed digital leaders – VP of Digital, Chief Digital Officer, CIO of Digital. This is where our AppMon + DX offerings shine – still the enterprise leading offerings gaining over 200 net new customers/quarter, driving over $300m in business for us in 2015. But there is yet another “mode” - we are seeing an increasing number of leading companies explore the future – revolutionary new digital apps built on revolutionary new cloud native architectures and approaches. These apps are hyper-scale, hyper- dynamic with an extremely tight teaming of dev-ops-biz. These teams often report outside of IT, to the CMO or CDO, are not encumbered with current standards or thinking, and are exploring new digital revenue streams and business models. These revolutionary new apps need a revolutionary new monitoring approach (see Gartner on Why APM must change, 2016). (a) they cannot be instrumented with “introscope” type bytecode instrumentation used by CA, AppD and NewRelic; (b) they need to anticipate the exponential growth in measurement points, services and process interdependencies and frequency of change with advanced self-learning and AI analytics; and (c) provide all stakeholders a contextually relevant view, but from a single source of truth/data, for more relevant intelligence, high value innovation and optimal collaboration. This is why we built Dynatrace – and this is why Dynatrace will eclipse New Relic as the Cloud Native APM of choice by 2018.
• #8: If you don’t see the whole picture you think you focus on the right thing. But if you don’t get a holistic overview of your application environment, you might miss very important things and, yes, this usually depends on what you’re actually interested in, and the operation mode of your OpenStack cluster (private, public, ...) Still, getting a clear picture of what’s going on overall is important, otherwise you miss events, errors, things, ...
• #9: Do you and your people have the right focus what’s important? from a business perspective UX is important, so are applications, the cloud platform is “just there” and needs to work
• #10: Do you and your people have the right focus what’s important? from a business perspective UX is important, so are applications, the cloud platform is “just there” and needs to work
• #11: Do your people have the right focus? It’s like the DevOps story all over again, that application teams and operations teams need to work closely together - cultural change is necessary for that and technology can only be an ambassador One single tool, that serves all stakeholders, and shows consistent data to everyone can also help in working closer together
• #14: This auto-discovery is really important, because it allows to create the real-time Smartscape that we talked about. It’s the map of all your interdependencies, all your moving parts, across every layer of your infrastructure. Smartscape gives you the horizontal view within each layer, datacenters, hosts, processes, services and applications. But it also gives you the vertical view that goes between the layers, to show what services are dependent on which processes, which hosts and so on. We’ll see more of that in the demo. This screenshot is from a real customer, an online retailer with a fully containerized environment. It’s a relatively simple example with 142 hosts, but you can see how complex it becomes with all of the services and dependencies. Seeing this visualized shows you how hard it is for a human being to truly understand all of the dependencies in your environment. In this example, you see some red bubbles that tells you something is wrong. Already this system is so complex that you can’t find out the cause of the problem using a classical approach to monitoring. That’s where our Artificial Intelligence engine comes in to play. It’s built on top of Smartscape, and this is how we’re able to provide answers to the most complex challenges in your dynamic environment. Other solutions might also tell you that there is a problem in a particular host or a particular service, but they can’t tell you the impact that has on the rest of your environment, how many users are affected by the problem, or what is the root cause. That’s because they don’t understand how the services are integrated into the rest of your environment.
• #16: Now let’s talk about how we make all of this happen. It starts with a key technology we call the OneAgent. OneAgent is a huge advancement from what you may know as the Dynatrace agent. It is a key enabler for monitoring the entire stack from the bottom up. Starting from the bottom with the infrastructure, it includes network packet analysis on the host, which allows you to find networking issues even in a public cloud environment. Working up from there, OneAgent will help in your cloud environment, regardless whether you use Cloud Foundry, Open Shift, OpenStack, etc. This is also auto-discovered and tied into your Smartscape. Of course, you still may have issues with disk and classic OS environments, so we also cover this automatically. The next layer up includes the various application components and services. Not only do we automatically discover your web and application servers, but also NoSQL databases and any other type of process and log analytics. This is all tied together in context and mapped to their processes, which is key. It’s not a separate log analytics tool like Splunk. Last but not least, the OneAgent goes all the way up to the end user experience. We automatically instrument your web pages and your mobile applications (in a semi-automatic fashion) in order to monitor the end user experience. You don’t have to configure each process to use an agent, you simply install the OneAgent onto each of your hosts. It’s preconfigured and the command line is provided from within the Dynatrace platform. That’s all there is to it. The OneAgent auto-discovers all of your key technologies and services.
• #21: Paul Cormier, RedHat No doubt, monitor UX: $, customer satisfaction, that they come back and use your services again No doubt, monitor apps: services/database perf, resource issues, ... No doubt, monitor OpenStack: instances, services, supporting services, log files ... the list goes on. Three-way split, different interest groups: CFO (memory utilzation?), CTO, COO
• #24: Update of the Payment Service of one of the rookie developer that are convinced that you have to write everything on your own and reinvent the wheel on a daily basis.
• #31: Putting it all together now. With large environments, manual introspection and correlation and log browsing won’t cut it anymore ... people don’t scale as well ...
• #32: Putting it all together now. With large environments, manual introspection and correlation and log browsing won’t cut it anymore ... people don’t scale as well ...