Tag: apm

  • APM and Application Stability: Where Two Monitoring Roads Merge and Diverge

    APM and Application Stability: Where Two Monitoring Roads Merge and Diverge

    In software development, application performance management (APM) is one of the grown-ups in the room. Not only has APM been around for a long time, but its solutions have evolved over several generations, making it one of the more mature product categories. 

    APM’s longevity makes perfect sense when you consider its fundamental purpose, which is to provide organizations with a way to understand the performance characteristics of their software. Value is delivered by alerting infrastructure teams when applications are performing slowly or poorly, and APM has the vast experience to do this job well. 

    If APM is one of the old-timers in software development, then application stability is the new kid in town. With the rise of mobile apps and iterative development releases, application stability has answered the widespread need to monitor applications in a new way, shifting the focus from servers and networks to the customer experience. 

    The emergence of application stability has caused some consternation for die-hard APM fans. However, these two solutions embody very distinct monitoring focuses, which leads me to believe there’s room for both tools, as well as different teams for both.

    APM: The Engine for Infrastructure and DevOps Teams

    Before the cloud, organizations supplied their own physical hardware and monitored components such as RAM, disk space, CPU and memory. If you ran out of any of these resources, you were screwed. 

    And that was the beauty of APM: It enabled the people running the applications to anticipate when they’d need more resources. 

    Of course, rather than monitor physical machines, today’s infrastructure, SRE and DevOps teams monitor cloud instances. Gone are the days of running out to Best Buy and lugging back new hardware. Instead, a simple request for a new instance is submitted to a cloud provider, and instant access is received. 

    Rather than make APM obsolete, as some feared, the cloud presents two good reasons for continued reliance on this tool.

    1. Apps Can Be Resource Hogs: A cloud instance is simply a slice of someone else’s computer, which means you still need to know when you’re close to running out of resources on this virtual machine. In fact, extra care is needed these days because you’re likely to run out of space more quickly.
    2. Money Still Doesn’t Grow on Trees: The ease of access to infinite cloud resources means that software companies may fall into the habit of throwing money at problems rather than figuring out how to streamline usage and costs through better efficiency. Companies can end up paying a ton of money to run apps if they continuously spin up more cloud instances without thorough consideration of the cost and need.

    And that’s where APM steps in. Its main purpose is to help infrastructure teams figure out capacity planning. With the cloud, questions shift to include:

    • How can I better manage my cloud instances and optimize usage? 
    • How can I make sure I don’t give ludicrous amounts of money to cloud providers? 
    • How can we tweak and optimize the cloud to reduce costs?

    These are the types of things that APM does extremely well. Anytime you need to figure out how to optimize your current resources or when to buy a new server or cloud instance, APM tells you. This information is invaluable to the people running the applications, namely the infrastructure or DevOps team.

    Application Stability: Where the Tires Meet the Road for Engineering Teams

    Now, let’s be honest, APM doesn’t have its strongest showing when the person who runs the app is also the person who builds the app. And that’s exactly the scenario presented by mobile development and iterative coding. 

    Rather than going through long development cycles, software now gets pushed to the web on a daily basis, and mobile apps tend to have weekly or biweekly release cycles. This release speed is not only encouraged but expected in agile software development.

    That means the chasm between building and running apps has shrunk, especially for mobile apps. More often than not, the people building the apps are the people releasing them. There is no gap. And, with mobile, companies no longer need to worry about expensive physical hardware but rather about the end user experience. The customer becomes the focus.

    Unfortunately, APM is perhaps a little too set in its ways to help you do that. But it’s not APM’s fault. These requirements are not what APM is inherently built to do. It’s great at detecting problems and alerting infrastructure teams so they can toss the issue over the fence to the development team. However, its core strength isn’t providing information on how to fix the problems because it wasn’t built with the developer audience in mind. 

    Trying to refactor APM to help with stability and error issues is like tuning your engine when you have flat tires. They are completely separate components of the car, built for different purposes. You can tune the engine all you want, but it isn’t going to move the car unless you focus on why there isn’t air in the tires.

    In today’s iterative world, development teams care a lot more about how apps are running. There’s a demand for fixing actionable items. Developers want to know exactly what’s broken, what to fix right now and what can wait. In short, developers want aggregation and automation of errors. They want to know, “Do we build or fix?” 

    This trade-off between building new features versus fixing bugs is one of the key factors behind the adoption of application stability management tools. Developers need answers to several questions:

    • Where are the errors in the code?
    • How can we get to those bugs and fix them as soon as possible?
    • How can we tie bug fixing into our planning for the week? 

    Whether running sprints or building in an agile manner, development work is planned in advance. Developers want to figure out how much new feature work will be included in a sprint versus how much bug fixing is required. And they need a tool that helps them automate the answer to that question.

    Benefits of Application Stability

    The beauty of application stability is that it brings together the errors captured by APM and enables developers to see at a glance which ones are worth fixing. As a result, five major benefits arise.

    1. Increased Efficiency: Companies eliminate the problem of infrastructure teams tossing issues over the fence to development teams. Valuable time is saved because application stability tools remove the game of telephone between the two teams and deliver bugs directly to the team that will fix them.
    2. Stronger CSAT: The time to fix bugs goes down dramatically when the person who wrote the code fixes the code. With diagnostic information in hand from the application stability tool, software engineers innately understand what the code does, what the bug means and how to fix it. Faster resolution of bugs that impact the end user experience means that customer satisfaction levels (CSAT) are less likely to drop.
    3. Error Prioritization: Application stability tools group bugs by root cause, making it easy for developers to get a sense of severity at a glance. It’s much easier to determine what to fix first when developers can see which errors are most costly, which affect the most customers, and which bug is impacting a key customer.
    4. Tool Synchronization: Taking it one step further, application stability tools are tied into project management suites. Bugs map directly to tickets created in Jira (or whatever tool is used), and tickets update automatically as priority changes.
    5. Stability Scores by Release: Application stability enables product and development teams to see stability scores by release. Since it’s common to have multiple app versions live at the same time, especially with mobile apps (where DevOps isn’t really involved), companies can’t rely on a single stability score. Teams need to see stability by release so that it’s clear exactly where the errors are and what impact they’re having on users.

    What Percentage of Your Development Team Has a Login to Your APM?

    I’m often asked whether I think application stability will replace APM, and my answer is simple: no, I don’t. APM remains an essential part of developing software, and organizations still need to understand when they’re about to run out of resources and when there’s poor performance. 

    Instead, I see these two solutions co-existing as adjacent categories but helping different teams. Application stability delivers prioritized errors to developers for fixing, while APM works well for enabling ops teams to raise red flags on high error rates and reduce cloud spend.

    Some of you may be thinking to yourself, “Well, my APM product does what you’re describing for application stability, so I’m sure my developers are fine using it.” To which I poise the following challenge: What percentage of your dev team has a login to your APM? What percentage logs in on a daily basis? And, if they do use it, do your developers like it?

    The answers to these questions may surprise you. After all, APM wasn’t really built for developers or for keeping end users happy. In contrast, application stability was born at the customer layer and is designed specifically to monitor the front end and ensure strong customer experiences with web and mobile apps. 

    Once you’ve had a chance to hear from your dev team, it wouldn’t surprise me if you discover that they’re pretty excited about the new kid in town.

    — James Smith

  • Uncover the Secrets in Your Apps Through Observability

    Uncover the Secrets in Your Apps Through Observability

    When it comes to your applications, the question to ask yourself is: “How helpful is monitoring if you aren’t proactively capturing the data you need to understand what is causing the errors you find?” The answer: Not very. That is why it is important for us to go beyond monitoring and work on expanding our capabilities in terms of observability.

    When applied to the world of software, observability is how well you can understand what’s going on inside your application based on accessible outputs. Looking at this from outside the realm of errors and application failures, etc., observability might describe how well a developer understands how a certain feature works the way it does.

    This example clearly shows that the metrics and context needed to attain what we can call a reasonable level of observability depends on the requirements of the individual system. We wouldn’t necessarily expect a developer at one company to understand how the features of another company’s application work behind the scenes. Likewise, an e-commerce application and a healthcare system will require different metrics to be observable.

    Bringing Observability to the Team

    Every company that operates software has at least the most basic level of observability thanks to log files. Unfortunately, in most cases we don’t know ahead of time what’s going to break, meaning no data gets logged. Occasionally, we may have a hunch that a certain method will be more likely to fail but even then, the data that’s written to the logs is usually shallow and requires additional investigation and context.

    A key measure of observability is how well you can answer “why this happened” without needing to ask additional questions. Teams that rely heavily on log files to understand and troubleshoot issues generally have low observability, as we all know that the logs often lead to hours (if not days) of follow-up questions. To improve observability, it’s important to focus on proactive solutions.

    Organizations, especially at the enterprise-level, use much more than log files to collect data around application errors and slowdowns. Application Performance Monitoring (APM) tools also play a significant part in most teams’ tooling stacks. Traditional APM tools provide additional context by helping teams identify when and where their application is experiencing performance or availability issues.

    These tools, and more, are commonly used by companies to monitor application behavior and to investigate the root cause of issues. Each tool that provides additional context into the internal function of the application increases our observability. Once your tool stacks provide the full context needed to understand the root cause of any issue, you’ve reached a reasonable level of observability. 

    Creating a Culture that Supports Observability

    Just like with every other buzzword in the industry–CI/CD, DevOps, etc.–achieving a reasonable level of observability means cultivating a culture that values and supports such a goal. There are several layers that need to be addressed and integrated together, but let’s break it down.

    The first step is to create a quality-focused, team-wide engineering mindset toward system hygiene. From beginning to end all members of the team should be trained to build and employ code with quality, first and foremost. The mindset of engineers must go beyond the desire to write high-level code, but also involve the planning process and understanding the purpose behind code changes. It is using foresight to plan for the unpredictable as much as we can.

    We all know that releasing code to production is basically “sending it out into the wild,” and we can all do a better job of making sure we have all the equipment we need to understand its behavior. That includes our mindset, as it forces us to consider our goal much earlier in development, namely by answering the following questions:

    • What are we trying to improve?
    • How can we measure success or failure?
    • What metrics do we need to measure this?

    Once this has been established, radical transparency and open communication follow naturally and further enable improvements in this area. When standards are established and issues are clearly communicated, problem areas in development can more easily be identified and resolved.

    Without the human aspect in place, no tool in the world can give an organization a reasonable level of observability.

    Conclusion

    Observability is about more than just monitoring your system–it’s about understanding it. In order to achieve a higher level of observability, tooling and culture are two major factors that should be addressed. There are many different ways to attain the best level of observability for your organization, so understanding what you need in order to be proactive is crucial.

    — Chen Harel

  • Cloud Confessions: Full Stack APM Is a Necessity

    Cloud Confessions: Full Stack APM Is a Necessity

    IT environments have become more dynamic and complex, which has created the need for robust monitoring tools. As a result, companies are increasingly adopting more than one platform, catapulting us into the multi-cloud era. Technology professionals are also embracing and acknowledging the need for comprehensive, full-stack application monitoring and management, bringing application performance management (APM) into the mainstream.

    The recent SolarWinds survey Cloud Confessions 2020 reveals even though APM has become mainstream (with a majority of tech pros using APM tools regularly), there’s still work to be done to move beyond troubleshooting. This finding is consistent with last year’s study, in which nearly half of the respondents said troubleshooting was a top-three task they managed daily.

    Tech pros have an opportunity to fully leverage the benefits of APM across the entire application stack, not just for troubleshooting. They should enable tech pros at any stage in their APM journey to realize the value and richness of end-to-end optimization with APM.

    In 2020, implementing solutions to achieve integrated application performance and availability management for any type of organization will become increasingly important.

    The Cloud Confessions survey showcases how application owners, developers and support teams currently use APM tools. It also shows areas where tech pros feel they need more education and support to confidently utilize APM solutions.

    Cloud Confessions Key Findings

    This survey explores how extensively technology professionals are using APM tools, whether on-premises or for SaaS-based application management and how they monitor these environments. It also showcases areas where tech pros feel confident in their APM tools and strategies, as well as challenges and avenues for building confidence.

    The key findings show:

    1. Tech pros are using APM tools, employing a nearly even mix of SaaS and on-premises to support the three architectures most often found in modern environments. Despite this, confusion around which tools are ideal for specific IT environments is consistent across application owners, developers and support team roles.

    • Nearly nine in 10 tech professionals are using APM tools in their environments.
      • 59% are using APM for monolithic (traditional on-prem) app development architectures.
      • 40% are using APM for N-tier service-oriented architectures.
      • 39% are using APM for microservices.
    • The top three most commonly deployed tools in support of APM strategies are:
      • Database monitoring (64%).
      • Application monitoring (63%).
      • Infrastructure monitoring (61%).
    • Two-fifths of tech pros face challenges due to lack of awareness of what APM solutions are currently offered and confusion over which currently offered APM solutions are best for their needs (respectively).

    2. Overall, tech pros are confident in their ability to manage and monitor applications on-prem, in hybrid environments and in the cloud; this confidence mostly sits within their ability to troubleshoot.

    • Over eight in 10 (84%) respondents are confident in their ability to successfully manage application and infrastructure performance.
    • Two-fifths (40%) of tech pros surveyed are most confident troubleshooting application issues and monitoring application availability and performance (respectively) given their existing skillset, followed by one-third (32%) of tech pros confident in collaborating with team members.
      • Troubleshooting and monitoring as the top two areas where tech pros have the most confidence is consistent with last year’s findings—in 2019, troubleshooting app issues was the number one activity tech pros spent their time on, with 48% of respondents choosing this as a top three task.

    3. The largest challenges tech pros face when monitoring and managing application and infrastructure performance relate to an existing knowledge and skills gap. As a result, tech pros have continued to deal with the troubles of troubleshooting, despite nearly all using some type of APM tool in the last 12 months.

    • When ranking the challenges, tech pros said:
      • Lack of training for personnel was the top challenge (57%), followed by lack of awareness of what APM solutions are currently offered (44%) and confusion over which currently-offered APM solutions are best for our needs (42%).
      • All other challenges were at, or under, the 30% rate.
    • Nearly eight in 10 (78%) tech pros report spending less than 10% of their time proactively optimizing their environments (vs. reactively maintaining).
      • In 2019, 77% of respondents reported spending the same amount of time on proactive optimization.

    4. Tech pros value the business insights delivered from APM tools, but greater skills development is needed in establishing KPIs and communicating IT performance to the business.

    • The top three business insights tech pros gain from APM tools include:
      • Ability to prevent applications outages (73%).
      • Ability to prevent app slowdown related to performance and/or capacity (63%).
      • Ability to improve user/customer experience (62%).
    • Tech pros are collecting these business metrics, but there’s a need to bridge the gap between business metrics collected and tech pros’ confidence in their ability to communicate performance to the business.
      • 34% of tech pros feel they need to improve their current skillset/ability to track impact across key business metrics to more confidently manage their organization’s IT environment, followed by 30% of tech pros who feel they need to improve their current skillset/ability to troubleshoot application issues, improve the performance of application code (29%) and manage/ensure/improve end-user performance (29%) (respectively).

    The key findings uncover the importance of knowing which combination of APM elements are right for your environment. Today’s environments are highly complex and distributed, involving microservices, N-tier, monolithic and commercial off-the-shelf (COTS) applications. This means the potential benefits of APM are even greater in modern contexts, as long as tech pros take time to educate themselves on the right tools for their environments.

    While APM tool usage is widespread, it’s not nearly as effective as it could be—an important distinction to business leaders in charge of digital transformation efforts. When we understand the APM world beyond troubleshooting, the possibilities for application performance optimization open up across the stack and across previously siloed teams.

    APM, when used to its potential, can be the great unifier of tech pro teams all working toward the goal of having highly available, well-performing applications and it can change the way modern businesses operate in the age of performance.

    — David Wagner

  • Dynatrace Extends AI Reach of APM Platform

    Dynatrace Extends AI Reach of APM Platform

    Dynatrace, at its Perform 2020 conference today, extended the reach of the Davis artificial intelligence (AI) engine it makes available via its application performance management (APM) platform to include deeper ties with mobile applications along with an ability to track key performance indicators (KPIs) such as revenue trends and customer churn.

    In addition, Dynatrace has enabled one-click integration with web analytics tools such as Adobe Analytics.

    Those capabilities are in addition to deeper integration between the Davis AI engine and Kubernetes that was announced earlier this week at the conference.

    Mike Maciag, chief marketing officer for Dynatrace, said usage of APM platforms is expanding beyond IT teams to include business users at a time when organizations are building and deploying more digital business applications. Most of those emerging applications revolve around mobile computing devices so Dynatrace is also extending the reach of the Davis AI engine to provide digital experience management capabilities, including advanced analytics and segmentation of mobile app user sessions, auto-instrumentation for additional mobile platforms such as React Native and tvOS and insights into third-party mobile applications components, he said.

    Specifically, Dynatrace multi-dimensional analytics now include crash reporting workflow and granular segmentation capabilities spanning health, performance and usage metrics across all app components and user actions. That capability will eliminate an APM blind spot most organizations have today, said Maciag.

    With more than 200 billion mobile applications having been deployed at a cost of $120 billion in 2019, Maciag said it’s apparent the scope of the challenge requires additional help from an AI engine.

    Coupled with an ability to now track how application performance is impacting KPIs, Maciag said there is now an opportunity to unlock a gold mine of business data that is locked up in observability platforms using modules such as the Dynatrace Digital Business Analytics.

    To further enable that capability, the Davis AI engine within that module provides automatic, real-time alerts on anomalies that might impact the business now using a wider array of data sources.

    It’s not clear to what degree business users might rely on APM platforms to surface events that could impact business outcomes. Most business users rely on either business intelligence (BI) applications or traditional spreadsheets to manage the business. However, as more processes become digitized using software APM platforms can surface events long before they are ever reflected in a BI application or spreadsheet. In fact, chances are good that business leaders are more likely to be able to affect the ultimate outcome sooner should they choose to analyze events in real-time via an APM platform.

    In the meantime, as application environments become more complex, reliance on APM platforms continues to grow. Once used mainly to keep track of only the most mission-critical monolithic applications in the enterprise, organizations are now tasking DevOps teams to manage entire business processes end to end basis. The challenge, of course, is most of those business processes consist of a wide variety of front and back-office applications that more often than not were built using entirely different frameworks.

    — Mike Vizard

  • Survey Finds Much Room for APM Improvement

    Survey Finds Much Room for APM Improvement

    A survey of 317 application owners, developers and support team professionals in the U.S. and Canada published by SolarWinds finds that while reliance on application performance management (APM) tools is widespread, most IT teams are still relying on these tools to react to events rather than to proactively improve application experience and performance.

    The survey finds 9 out of 10 IT professionals are making use of APM tools that are either deployed on-premises or accessed via a software-as-a-service (SaaS) platform. Nearly 8 in 10 respondents spend less than 10% of their time proactively optimizing their environments, according to the results.

    In fact, the biggest APM challenges identified by survey respondents were lack of training for personnel (57%), followed by a lack of awareness of what APM solutions are currently offered (44%) and confusion over which APM solution best fits their needs (42%).

    Jim Hansen, vice president of products for application management for SolarWinds, said some of those challenges stem from the fact that there are too many APM tools to deploy and master. Survey respondents are employing a mix of database monitoring (64%), application monitoring (63%) and infrastructure monitoring (61%).

    IT management is further being complicated by the adoption of a wide variety of application architectures. According to the survey results, organizations are applying APM tools to manage monolithic (traditional on-prem) app development architectures (59%), N-tier service-oriented architectures (40%) and microservices-based applications (39%).

    Hansen said as organizations increasingly move away from monolithic applications, the need for a more proactive approach to APM across the full stack will become more apparent. The level of dependencies between microservices especially will drive organizations toward APM platforms capable of correlating events across both applications and the underlying infrastructure on which they depend, he noted.

    Less clear is to what degree IT teams are comfortable using the analytics surfaced by APM tools to automate the remediation of any given issue. According to the survey results 84% of respondents are confident in their ability to successfully manage application and infrastructure performance, with 40% reporting they are most comfortable from a confidence perspective to use APM tools to troubleshoot application performance issues. The top three insights survey respondents said they gain from APM tools are the ability to prevent application outages (73%), the ability to prevent app slowdown related to performance and/or capacity (63%) and the ability to improve user/customer experience (62%).

    In terms of areas for improvement, survey respondents identified improving their current skillset/ability to track impact across key business metrics (31%), followed closely by the need to improve their current skillset/ability to troubleshoot application issues (30%). The ability to improve the performance of application code and manage/ensure/improve end-user performance tied at 29%, respectively.

    Of course, troubleshooting an existing issue is one thing. Proactively using APM tools to prevent issues from occurring represents a more advanced approach to managing IT in keeping with best DevOps practices. It will be interesting to see how much the adoption of N-tier and microservices applications will foster further adoption of best DevOps practices.

    Most organizations today have embraced DevOps practices to varying degrees. However, as IT becomes more complex to manage in the age of the hybrid cloud it’s now only a matter of time before legacy approaches to managing IT as simply no longer practical to employ.

    — Mike Vizard

  • Four Ways to Modernize Processes and Measure Performance With APM

    Four Ways to Modernize Processes and Measure Performance With APM

    Change is everywhere and the stakes are high. For 2019, businesses are on track to spend over a trillion dollars on digital modernization, according to a recent study from IDC.

    A crucial part of modernization is the growing number of IT organizations using the latest in dynamic, cloud-scale technologies to develop applications. As a result, technology professionals in the businesses you serve must now work with a much more complex and dynamically changing tech stack.

    When building and maintaining an app, it’s becoming even more common to have hundreds (or thousands) of pieces of code in containers being continually reconfigured and brought in and out of production. And many of these operations take place in customer-facing applications.

    The stakes are high, because if something goes wrong operations could halt. It’s therefore vital to understand the underlying technologies throughout an organization’s IT environment to better equip customers with the tools needed to be successful. Application performance management (APM) tools that simplify stack management, whether it’s on-premises, hybrid or fully cloud-native, provide a level of visibility needed for modern businesses—and they work across multiple cloud environments, such as AWS or Azure.

    As a channel partner, you need to be prepared to help your businesses and their customers through this modernization process. 

    Try the following to help your customers modernize business processes.

    Help Them Realize Software Is Now Business-Critical

    As IT departments move from on-prem infrastructure and a mix of commercial off-the-shelf (COTS) and monolithic custom applications to increasingly adopted cloud-based Kubernetes microservices applications, they’re accelerating the adoption of software at the core of all their business processes. The result? Business is increasingly dynamic and responsive—new applications are built and delivered to market faster than ever. But companies are also at risk now when things don’t go well—that strategic app could degrade or fail.

    All the tech layers underpinning these applications are also becoming more sophisticated, dynamic and interwoven—and making it still harder to administer as they continuously change at an even faster rate.

    Focus Your Customers on Core Competency

    There are plenty of open-source tools out there for your customers to use to build their own monitoring. The biggest obstacle for businesses rolling out their own apps while using an open-source tool is core competency. 

    If, for example, your customer is a wholesale plumbing supply company, is their competency sourcing plumbing supplies or knowing how to write instrumentation code for all their plumbing supply chain applications? Help them focus on what they’re good at and give them tools to manage the rest.

    Perhaps you have a large financial services customer who is spending tens of millions, across multiple years, on a team of outsourced experts to write precisely the code required. This is an extremely time-consuming and costly effort, but financial institutions do this because their needs are highly specific and mission-critical, and the cost of not doing it is even higher. 

    If you look at real-time high-frequency trading environments—where billions of dollars are moved in matters of tenths of a second—you come to understand the stakes justifying these herculean efforts. All of which supports the need for APM tools to help empower the tech pros in-house who monitor and manage these high-speed trading environments.

    At the other end of the spectrum are the small tech companies with a new idea they’re out to promote. But when it comes to most companies, their core competency is often not monitoring and managing their infrastructure and applications. It’s understanding the market requirements for their custom apps and getting those apps to market quickly. At the same time, organizations of all shapes and sizes are still confronting the reality that to successfully deliver modern applications we must shift from pure infrastructure performance metrics to the KPIs that best demonstrate end-user experience.

    Ultimately, many of the organizations described above have either focused on IT as a core competency or, in the absence of dedicated tech teams (at SMBs, in particular), they have outsourced management of their complex, dynamic tech stack and custom application builds. In both instances, APM tools are a necessity and it’s prime time for the channel to deliver those services.

    Be the Most Viable Modernization Partner

    By understanding the needs of modern organizations as they grapple with their complex tech stacks, you can ensure you have the right set of tools for your customers. 

    Provide full-stack capabilities for today’s businesses to manage their applications and keep operations running smoothly. Cater to unique business problems and equip your customers with APM tools based on their needs—advanced logging, trace metrics, performance optimization and full-stack visibility across applications and the compute infrastructure on-premises, hybrid and cloud. Help them check all their functional boxes.  

    Measure Performance with Full-Stack APM

    In all cases, your customers should be measuring performance. Because every company uses a mixture of digital technologies, arming them with full-stack APM will help gain visibility into performance throughout the business. With APM, businesses can see if their system is degrading—and fix it before disaster strikes. That’s the business value for APM—it gives visibility into the complexity underpinning today’s application environments. Full-stack APM provides this visibility, whether the apps are cloud-based, on-premises or hybrid.

    But here’s the reality—not all APM tools are the same. Traditional APM solutions weren’t built for the environment IT departments now have, with the addition of containers and microservices-based applications to their existing monolithic and n-tier/SOA applications. Those solutions were made to manage hundreds or thousands of objects with slower rates of change, not the tens of thousands, or even hundreds of thousands to millions of objects IT works with today.

    Also, note the ephemeralness of container-based microservice applications able to live and die in a matter of seconds or less. There’s no time to automatically install a traditional agent, let alone do so manually. The container’s life span is shorter than the time it would take to do such instrumentation. Direct them instead toward a full-stack APM solution with complete coverage of all application architectures: monolithic, n-tier/SOA and microservices based. With anything less, they’re running at a higher risk of brand damage and revenue impact.

    By being the experts on APM, providing full-stack visibility and measuring performance, your customers will find modernization success.

    — David Wagner

  • APM for All: Simplifying the Complexity of Cloud

    APM for All: Simplifying the Complexity of Cloud

    As companies adopt hybrid and even multi-cloud strategies, their IT departments are beginning to use dynamic technologies to build new application features on top of existing back-end business systems. Most organizations now have a blended, multi-cloud architecture where public clouds are integrated with the existing on-premises, private or hybrid cloud infrastructure and applications.

    This means, for all the agility, flexibility and scalability the cloud affords us daily, the cloud is also a source of increased complexity for technology professionals required to assure the availability and performance of the application environment. This, in turn, is expected to have a substantial impact on overall management. Gartner predicts that by 2020, “75% of enterprises will experience visible business disruptions due to infrastructure and operations (I&O) skills gaps.”

    It’s vital, then, to first understand the underlying technologies supporting application availability and performance throughout your entire IT environment. Next, you must understand how your technologies are dynamically interacting with each other in both development and production. And you need to know this not just at the various levels of the application stack itself—across all infrastructure as well as services, function calls and code—but for various types of applications themselves: monolithic, service-oriented architectures (SOA) and microservices-based.

    That’s why, whether on-prem, hybrid or cloud-native—and whether you’re running AWS, Azure or Google Cloud (IaaS or PaaS)—you need comprehensive visibility into your complete infrastructure and application stack. Application performance management (APM) gives you this visibility into your IT environment by simplifying, and more importantly, normalizing, app stack management. 

    The Case For APM

    APM has significant business value. In today’s environments, an IT team typically no longer has only one application per virtual machine—but rather dozens of virtual machines per physical host (whether on-premises, private or public cloud), with hundreds or thousands of containerized microservices per virtual machine. Additionally, these business environments with hundreds (or many thousands) of containers are continually being reconfigured and brought in and out of production underneath customer-facing applications. If something goes wrong, the digital operations can collapse. And they all need to play nice together since the underlying resources are shared.

    At the same time, the game has changed. The red, yellow and green glow of infrastructure dashboards now has less bearing on whether you’re really delivering high-quality user experiences. Instead, success metrics are now based on evolving real-world, end-user experiences. You are customer-facing, because clients interact with you through your applications and websites. If your site is slow, you lose money and it negatively impacts the business brand.

    To fix the problem, you need specifics. For example, is the transactional performance slow because you don’t have enough compute? Or is it slow because the application code is bad? These factors are interrelated. In our dynamic, shared-and-virtualized everything environments, it’s challenging to understand where the true causes of your problems are.

    When Amazon went down for an hour during Prime Day last year, experts estimated the company lost 100 million dollars in sales. Imagine the impact of a potential outage during the holiday season. Of course, those are Amazon-sized numbers. But scale down those Godzilla figures to your size, and it still hurts—either through lost revenue or damaged brand reputation.

    With APM, you can see all the metrics and find out how the application’s performing over time. You can see it degrade, giving you time to figure out why it’s slowing—before it stopped getting you your raw materials on time. You can understand down to the line of code, or database query, exactly what, where and why it’s slow.

    But what are we talking about when we talk about APM? Gartner has pointed out the historical confusion on terms. There’s also a matter of differing capabilities among APM tools. Some are geared toward monolithic applications; others for Java and the web (and other applications) and still more are tuned for microservices. Beyond that, there are full-stack APM solutions that can measure it all.  

    Normalizing IT Management With APM

    APM strategies and toolsets aren’t all the same. By my count, there are three iterations of APM implementations. First, there’s APM dating from when all tech was monolithic, of which the best example is the old CA Wily Introscope. Then came a second generation, which covered areas such as SOA, Java and the web—a good example here would be AppDynamics and the old Dynatrace. After that comes a version of APM tuned specifically for microservices and containerized application environments, such as the new Dynatrace and Instana.

    In some cases, the actual APM technologies themselves haven’t kept up to date with the underlying infrastructure changes. That’s especially true for microservices. There are some legacy APM solutions that don’t support microservices in containerized application environments. On the flip side, some new companies in the APM space only operate in the microservices space. They are container-based, and don’t support old monolithic code. They also don’t support n–tier/SOA application environments.

    Most customers, however, have mixed environments. Almost no one is operating with 100% microservices in containers operationally managed by Kubernetes.

    By my reckoning, modern APM systems should monitor it all, because everything is mixed and likely to stay that way, if history is any indication. Companies still rely upon massive databases of proprietary information—databases of business records. They’re just building all-new applications in front of them.

    If you posit that it’s now more important than ever to ensure availability and performance as experienced by the user, then you need APM across all those three categories of applications and their environments, including public cloud providers such as AWS and Azure. You need full-stack APM.

    Getting Started

    Before you do anything else, first remember your due diligence. Ask around and seek out first-hand knowledge about the APM solution vendor. Don’t just trust them to give you objective advice on how good they are; there’s a great deal of hype in the APM market that can often cloud our understanding of a certain solution’s actual function. So, where do you start? Typically, it’s best to start your thinking as if you were the end user coming into your application and infrastructure stack. This means monitoring, measuring and understanding the real performance of your web-based or custom applications. You should start with the customer (external-facing) side and then work your way back in through the stack from a monitoring perspective. Next, monitor, measure and understand the performance metrics of the application itself. Here you’ll find critical capabilities, such as distributed transaction tracing and code profiling, to be critical to truly understand how all the application components relate from a performance perspective. Finally, while it’s essential to also know how your infrastructure components are performing, it’s critical to do so in full application performance context. This application-context infrastructure monitoring must encompass both performance instrumentation as well as all logs associated with your application and related infrastructure.

    Start small for quick success and to build a foundation from which to make APM more broadly successful for your organization. Start with one, or at a most a handful, of applications needing the greatest attention. Prove value and success and then ramp up adoption from there.

    In all cases, remember—unless you’re solely relying on serverless computing, with only microservice-based applications in containerized environments, you’ll need visibility across the three application architecture types: monolithic, SOA and microservices. Otherwise, you’re not getting all the information you need.

    It’s always been the goal of IT throughout all technology revolutions—whether it was mainframe, time-sharing, client-server or distributed, and whether it’s hybrid or full-on public cloud—to get a single pane of glass for operational management. True, full-stack APM delivers that view.

    — David Wagner

  • Predictions 2020: The Future of APM Strategies and Tools

    Predictions 2020: The Future of APM Strategies and Tools

    As 2019 comes to an end, it’s safe to say that multi-cloud strategies are here to stay. We can predict that 2020 will bring an ever-increasing demand for application performance management (APM) tools and services.

    So what does the future of APM look like? Let’s dive in.

    Multi-Cloud Strategies Increase the Demand for APM Tool Adoption

    Companies are increasingly adopting more than one platform—either for financial leverage or to create a time-to-market or feature race between the platforms. To remain competitive, public cloud providers must offer unique features or capabilities differentiating them from competitors. This has created an upsurge in new and more complex technologies, increasing the need for APM tool adoption.

    Logs Will Be Recognized as Key Aspects of APM

    APM is a puzzle made up of user experience, metrics and traces, and logs—and each piece must be incorporated to achieve full-stack visibility and ultimately seamless app performance. However, a healthy app is not characterized solely by top performance, but also availability—making a log management solution that monitors availability, enables proactivity and reacts quickly to remediate problems key.

    In 2020, implementing solutions that achieve integrated application performance and availability management for any type of organization, including those operating on-premises and/or cloud-based applications across all mixes of cloud environments, will become increasingly important and prioritized.

    APM Skills in a Cloud-First World

    The nouns have changed, but the verbs remain the same: APM skills are among the top skills tech pros want to develop in the coming year, according to the recent SolarWinds IT Pro Day survey, Building Confidence for Tech Pros of Tomorrow. However, in 2020 tech pros will begin to recognize that many of the skills they already possess are sufficient to manage the new realm of integrated solutions in the cloud. Tech pros can leverage some of the same skills they could before as the nouns have changed, but the verbs remain the same. Where we used to have server or virtual machine, now we have containers. But the verbs? They’ve always been focused on optimizing performance, ensuring availability and planning capacity.

    In 2020, the extent to which tech pros will discover they don’t need to fear new nouns (more than they did when they moved from client virtualization) will increase.

    Universal Adoption of APM Tools

    As environments become more dynamic and complex, the opportunity for applications to break increases—creating the need for robust monitoring tools. In 2020, as buyers see the benefit of leveraging APM tools on a regular basis rather than only in critical moments, the market will adjust accordingly. We can expect easier-to-implement solutions that are more highly valuable and affordable. The paradigm that APM tools have to be expensive will be broken once and for all.

    Want to learn more about what to expect in 2020? Join us Jan. 23 for our Predict 2020 Virtual Summit  featuring discussions from some of the industry’s best and brightest offering up their visions for the future. Sign up today for this free daylong virtual event.

    — David Wagner

  • Instana Delivers Automated Node.js Tracing for AWS Lambda Functions With Zero Code Modification

    Company to Provide End-to-End Tracing Across Multiple Serverless Functions and Server-Based Microservices

    Las Vegas at AWS re:Invent – December 3, 2019 – Instana, the leading provider of real-time application performance management solutions for microservice and cloud-native applications, today announced the ability to trace serverless Node.js functions running on AWS Lambda. The new capabilities, which require zero code modification, deliver superior native serverless tracing automatically, providing performance metrics beyond, and independently from, X-Ray.

    “As companies continue to push the envelope in creating smaller, more dynamic services, developers will use serverless functions more often, and in more critical applications,” said Mirko Novakovic, co-founder and CEO of Instana. “By providing Native Node.js tracing on AWS Lambda, Instana helps application stakeholders like DevOps see how individual functions are performing call by call, but also provides the necessary details developers need to make their code perform as expected.”

    The new capabilities are an extension of Instana’s unique AutoTrace™ feature, which captures end-to-end distributed traces of all requests with no sampling. The new serverless monitoring and tracing feature is included with Instana’s Application Performance Management solution for microservice and cloud-native applications, with no additional cost.

    “Application environments and the technologies utilized in these environments are always going to improve with advancements in platforms,” said Pavlo Baron, Instana CTO and co-founder. “Instana is committed to providing the most comprehensive visibility into applications and application platforms, all with the same best-in-class automation that our users have come to expect.”

    Instana AutoTrace for AWS Lambda is a big step forward for developers and DevOps teams responsible for developing, deploying and maintaining applications that include serverless functions built with Node.js. Key capabilities include:

    • Automated native tracing for AWS Lambda functions written in Node.js for all supported Node.js libraries and frameworks
    • Zero code modification, representing huge productivity gains for development, DevOps and operations teams
    • Tracing through other programming languages, platforms and deployments

    All data from Lambda function traces is seamlessly integrated into all Instana analysis capabilities including End User Monitoring, Unbounded Analytics™ and  Application Perspectives™. New functionality also includes out-of-the box contextual Lambda Function Overview Dashboards that include function name, function version, AWS region, interdependencies with other functions and services along with all other critical Lambda runtime metrics. Information from Instana’s Lambda Node.js tracing is combined with other performance information, including CloudWatch to provide the most comprehensive view of service health and performance.

    Unlike other APM solutions, Instana fully automates the entire lifecycle of application monitoring including application discovery and mapping, monitoring sensor and agent deployment and health monitoring of application infrastructure. When any changes occur to dynamic applications, Instana recognizes that a change has occurred, automatically makes the appropriate adjustments to maps, monitoring thresholds and health dashboards.

    Instana is highlighting the new Lambda serverless tracing capabilities at Amazon re:Invent in Las Vegas (booth #511). Visit https://instana.com/serverless for more information.

    ###

    ABOUT INSTANA
    As the leading provider of Automatic Application Performance Monitoring (APM) solutions for microservices, Instana has developed the automatic monitoring and AI-based analysis DevOps needs to manage the performance of modern applications. Instana is the only APM solution that automatically discovers, maps and visualizes microservice applications without continuous additional engineering. Customers using Instana achieve operational excellence and deliver better software faster. Visit https://instana.com to learn more.

  • DevOps Chats: App Attention Index and The Era of Digital Reflex, with AppDynamics

    DevOps Chats: App Attention Index and The Era of Digital Reflex, with AppDynamics

    Application performance company AppDynamics (acquired by Cisco in 2017) recently released its 2019 edition of the App Attention Index Report. The 2019 report is subtitled The Era of Digital Reflex. Joining me on this episode of DevOps Chats is Steve Long, AppDynamics regional CTO and technology strategy.

    Digital connections are a near-constant. Interacting with our world through digital apps and transactions are omnipresent: making a restaurant reservation using OpenTable, making payments using an app or our smartphone digital wallet and checking our smartphones to plan and move through our day. Thus the name of the report, The Era of Digital Reflex.

    In addition to insights from the report, Steve and I talk about measuring the customer’s experience, tying performance back to the desired business outcoming, strategies for finding problems and reducing the time it takes to fix problems. Join us on this compelling discussion about application performance, customer experience and business outcomes.

    As usual, the streaming audio is immediately below, followed by the transcript of our conversation.

    Transcript

    Mitch Ashley: Hi everyone, this is Mitch Ashley with devopsy.kinsta.cloud, and you’re listening to another DevOps Chat podcast. Today I’m joined by Steve Long. He’s regional CTO and technology strategy with AppDynamics. Today we’re going to be talking about the 2019 edition of the App Attention Index Report findings, The Era of Digital Reflex. Whoa, that sounds heavy. Steve, welcome to DevOps Chat.

     Steve Long: Thanks for having me today, Mitch. It’s a pleasure to be here today.

    Ashley: Sorry, I kind of put on my ‘60s accent. “Whoa, man, heavy.” Would you start out be introducing yourself? Tell us a little bit about what you do and of course, in case somebody doesn’t know what AppDynamics does and what AppDynamics is about.

    Long: Yeah, sure, absolutely. So I’ll go back a little bit in time. I was a vice-president of technology operations for a media company and then my last job before joining AppDynamics, I was a chief information officer for a financial tech company, a large banking services company. And I joined AppDynamics because–for two reasons. One was finding problems in the sea of–no longer a needle in the haystack–it’s a needle in a needle stack, at this point. With all of the complexities happening, it changed my career. And when Cisco and AppD joined and that merger took place, I couldn’t think of, you know, two companies that I would love to be part of, that when they joined–you know, after I left being a chief information officer to come and help drive technology strategy for AppDynamics.

    So AppDynamics is a application performance management company that back in the dawn of the day I became one of their first 30 customers, about nine years ago, and really attaching to the run time and basically looking and analyzing your application performance. If the application is the north star of your business and typically how businesses are driving revenue and transactions, we’re at the forefront and the heart of that, to be able to tap into that and give an MRI to what’s happening in your cloud, your data centers and what’s happening with the complex technology running in the business.

    So that’s a little bit about AppDynamics. We’re an application performance company and part of Cisco, and driving businesses to really see into what’s happening in their technology ecosystems.

    Ashley: Excellent. Well you share something with me, and that is both the kind of end consumer of technology like this is a CIO but also a tech person in the product, the tech vendor. So that’s fantastic. I enjoy sharing that with you. Now tell us a little bit about the App Attention Index Report and what that’s about–what it measures, what kind of information that it discloses for us.

    Long: Yeah, so “The Era of Digital Reflex” is the title, but at the core we’ve really entered into really consumers saying they use digital services almost like you would a human, like an extension of your body, like a reflex. And today we’re doing that almost automatically or unconsciously. And that shift in consumers–like if you look past five years ago, we had to proactively do that. Now, with something in the palm of your hand, you don’t realize it, but now you’re relying on digital services like every day and it’s really helping you get your jobs done and your life duties, and you’re taking decisive actions by it being a reflex.

    And it’s kind of a wake-up call for the industry and businesses, because at this point we’re looking at the performance of these applications being application loyalty and it’s taken over to be the new brand loyalty. So if businesses really want to stay competitive, they really have to have a really flawless experience for their users. Otherwise it impacts their brand loyalty and their application loyalty and other things. So that’s the heart of the report at a high level.

    Ashley: Makes total sense. I mean, you’re talking about our digital world and our connection to it. It’s not only true today, but it’s even more so–every day there’s a new function we do on our phones, on our computers, on our TVs, on whatever device is connected to some cloud somewhere. It’s almost all a digital transaction.

    Long: Yeah, absolutely.

    Ashley: So tell us a little bit about this year’s report–what some of the findings were. What would be some of the most interesting things that came out of it?

    Long: I’d like to actually use an example that I have personally, and it’s based on the report. So I actually had a lunch with colleagues, a friend and a customer last week, and it was about six of us. And I said, “Hey, just out of curiosity, how many applications have you guys used today?” And to a one, they looked at their phone and all kind of raised their heads back up and one rattled 13, one 17, one 12, one 19. I was like, “How did you do that?” And they were like, “Well we tend to close out our applications at the end of the day and it’s 2 p.m. and I counted up from the last application used to now.” And I was blown away. And so I did the same thing and went back to the last one that I hadn’t closed and counted and I was at all 11 at that point in time, at 2 p.m. And I thought to myself, “Wow, okay.”

    And then I asked–the secondary question was, “Well, did any of those give you any problems? And I’m relating back to the app index, because if it had a problem, what did you do?” and the first example that came back was, “I had a reservation at a restaurant last night and I had to go close one and go to the other because it didn’t have my reservation, so I ended up having–for every application that I have, I have a competitor.” And if it’s really sticky, maybe like banking or something else, maybe they don’t, but they’ve got a few ride shares, a few travel apps, a few restaurant apps. And it’s really that wake-up call, because the metric that comes out of the report is about 55% of the people can’t go without their mobile device for up to four hours.

    I did that today before this, just to see if I could do it. And right before I got on here I had to give up, because I needed to see if I had a notification or a text or something that I had missed. And so personally it is that reflex, that extension. It’s what we do now unconsciously.

    Ashley: I think I’d rather hold my breath than try to live without my digital–

    Long: No doubt. No doubt.

    Ashley: So when you count the number of applications that people are using, do you count like, for example, on your phone you can look to see, how much battery time did you consume with different applications is another way to measure effectively kind of usage. How do you look at it?

    Long: Well I mean, it’s habitual. So we just looked at ones that were open. But I mean, if I go back and look at my day, my alarm goes up and I pick up my phone. And the first thing I did there was, “Now that I have my phone in my hand, I’m going to look at an application.” My schedule, maybe my e-mail, maybe a text. And we’re basically saying now that the first thing we do is not talk to humans; it’s to look at our apps. And nowadays–you know, if I go back five or six years, my house is now fully connected. So I’m looking at my security camera and any events, I’m looking at my thermostat. Did I leave my air conditioning or heat on? Is my car charged? You know, and do I need to set the thermostat in there? Is it 100 degrees out and do I need to put the AC on before I get in my car? And all of a sudden I’ve got energy usage tools.

    So these applications can be anything from a browser-based service, but they’re there to help you with your life. And then as you get to work it becomes even more–more of a need, with reminders and you know, calendaring and everything going on in your work world and sharing documents and collaboration. And that’s why at 2 o’clock you can hit somebody who’s had 20 and in a day they can be hitting 30 to 50. So it’s pretty amazing what these digital services are doing and how intrinsic they are to our daily lives.

    Ashley: Well it’s amazing, because one of the things–I’m guessing I’m probably not part of your report–but occasionally I’ll look to see how many connected devices or IP addresses have been allocated in my home. And it has gone from a dozen to two dozen to over 70 in a year and a half.

    Long: Wow.

    Ashley: And that’s just as I kind of went to a connected home. And every one of those is not just talking to stuff in the home. It’s talking to the cloud, you know, for the temperature management, for the door locks, for the security system, whatever–it’s all talking to something, if not me or one of my family members through an app on the phone or browser.

    Long: And think about when they don’t work and they can’t talk to that cloud or digital service. And since it’s an extension of your human interactions, now you can have expectations that are super high that you just had a disruption, and it can impact your mood. It can cause frustration. It can do things that you don’t even know are happening. And that’s why we call it–you know, it’s a reflex now. It’s intrinsic, it’s unconscious and it can cause strife in our lives when it doesn’t work.

    Ashley: That’s a really good point, because we always think about networks as end consumers as speed, but the reliability has also gone up significantly, and it’s going to have to increase in reliability moving forward, because that’s–it’s a reflex, it’s a dependency, it’s an expectation, it’s a customer satisfaction measure, right? Of what that experience is like.

    Long: Yeah, and I think the expectation just a few years ago was much lower, and every year that goes by–I think three quarters of the people we queried–that their expectations had gone up. And it’s growing and growing, and the tolerance levels now have also become more important, and these services are just more important because they’re prompting a higher demand and better experiences, so that businesses can help you with your daily lives. And so the  net of it all is we’re hungry for very positive digital experiences, and we’re willing to pay for that and have them be more personalized and know who you are and kind of know what you want, and that’s a huge differentiator between businesses competing with each other.

    Ashley: Interesting. As you looked at this data, were there different ways that you slice and dice, segmented–you know, home versus business or mobile versus browser or any of those kind of ways of looking at the information, to gather some interesting facts?

    Long: Yeah, we did. We have a crosscut of that. Mainly though looking at the consumer base side and how it interacts with the businesses and how the expectations of the consumer are there and need to be met and exceeded. The experiences need to grow. I know in our daily interactions from AppD, we look at e-commerce companies and banking and a number of different online services, and it’s pretty clear that the performance, the loyalties are pretty clean cut when you have a performing app versus a non-performing app. And the impact it has on the consumer. And so those can transcend almost every industry. It’s almost industry-less, where the application performance wins.

    You know, every hundred milliseconds of latency–you know, that causes some level of distress, and when you start to get into situations where something might take 10 seconds, in industry A that might be acceptable because it’s a longer-term type of transaction. But in industry B, which may be more of a real-time field, like I need a ride or I need a stock trade or I need something like that, 10 seconds is unacceptable. And if you’re not able to measure that and have application performance, you can’t dissect what your problem is because ultimately it’s your business transaction which leads to your experience–a journey that you’re going through, your business journey–and at the end of that rainbow is the actual business outcome that you’re looking for. And whether that’s a sale or moving money or buying a ticket or a new shirt, that’s the key, is having that business outcome.

    And the more we tie application performance to that business outcome, we’re better off as a business. At AppDynamics we look at all of the way to the edge, to the browser, to the device, to the data centers, to the cloud, but we also tack into that the ability to look at money or what the business KPI that’s being impacted. Because if you have a seasonal event like an inventory level dropping or a loss of money or you’re making more money because of a promotion, wouldn’t you want to know that your performance or your lack of performance–what the impact is to businesses?

    Ashley: It’s interesting too, because it wasn’t very long ago–I mean, maybe just a few years ago–where we’re almost solely reliant on things like an NPS measurement or call times–things that we do in the call center. And outside of that, you know, one person tells five people when they have a bad experience and you don’t really know those kinds of things. But now, in this age of data for everything, you know, the last time somebody used my Lyft app, “Oh, it was poor performance. We haven’t seen them in three weeks.” Maybe they went to Uber. I may not know that, but I know what their last–there’s data there to mine and to go after, where some of the telemetry information about performance could indicate some symptom that might’ve led to a consumer change in behavior.

    Long: Yeah, and it’s no longer–we talk about expectations and not meeting them, but the downside is that is your reputation risk. I mean, if you get an issue reported to you from internal or you know, somebody inside, that’s one thing, versus it being reported to your call center–that’s another thing–versus somebody switching to a competitor and posting it on a social media site. Now you’re not only worried about stock price and revenue risk; you’re talking about reputation risk. And that reputation risk really does tie back into those expectations not being met, at whatever level it is. So reputation and how, you know, media out there is picking up on that and promoting that when it’s negative–for a reason, because it’s a shared experience.

    Ashley: This may be a bit of an impossible question, so I recognize that up front. Is it possible to measure what customers’ expectations are? Is it too big of a moving target? Is it too many variables? Or is it something we can get a handle on? How do you address that?

    Long: Well, I firmly believe we can. And say that coming from the customer side of AppDynamics, but also–you know, businesses know their business, their KPIs, what outcomes they’re looking for. And if you don’t measure it, you can’t really make change in a positive way. So we see digital transformation–Agile–you know, we’re seeing BizDevOps–those are all things to really move businesses to become more efficient, drive the right decisions around the right business outcomes they’re looking for. And you know, I always say you do have to focus on the application performance. Being a past CIO, I tried to put myself in the customer’s shoes. I mean, if you don’t have a robust way to look at application performance then you don’t have that safeguard or those guardrails that you can put up to make sure that, you know, number one, your mission-critical applications are working, but number two, it’s the user experience. And being able to measure that and seeing that all the way from the edge to your cloud services.

    And the dependencies. I mean, think about it, the number of SaaS providers, cloud providers, third-party data that you’re touching just to execute a login on any application site, it could span hundreds of transactions. And if any one of those little things go wrong, you’re not focusing on application performance or you can’t measure it, and it could have a negative user experience.

    Ashley: Very good point. Because there are very few, maybe if any, closed ecosystems, to throw the “ecosystem” word in there. You really are reliant on a lot of other providers to come together to deliver that overall experience, that service, that functionality.

    Long: Yeah, and that’s how you get your business outcomes. So I do think that it’s achievable and you know, that performance and correlating it to the business performance and the business outcome–that’s really the objective companies are setting, and why they’re moving to APM and companies that are expanding out to give them business metrics on top of APM and consumer metrics on top of APM. Because it’s that trifecta. And if you think about it, there’s lots of ways you can look at logs or network flow data, but at the application, since it’s the central north star of the business, it’s the most granular and contextual data that you can get to see whether or not your business is performing. So that when you have that granular and contextual data down to the line of code maybe not performing, you’re able to look at the two most important metrics to any company, which is finding and fixing problems and reducing the time it takes to get to solutions on either side of that. So the faster you find them and fix them–whether it’s a ten-second issue that you can automate out of your system, or if it turns out to be a ten-hour outage, those are radical, you know, separations that we see in companies by just implementing the right tool set, the right performance measurements and really driving their businesses to reduce those risks in any company.

    Ashley: Okay. Maybe one last thing to kind of touch on–were there any other interesting findings, notable things? Maybe kind of a small little quirk thing that was “Wow, we didn’t expect to see that,” any other things to glean from the report?

    Long: No, I think we’ve covered it. At a high level I always suggest, put yourself in the consumer’s shoes. Really have a robust way to look at performance, and tie that back to the business outcomes. Because ultimately the business teams have a really hard time understanding IT and engineering, but the IT teams actually can make that leap. They can tend to look at the business challenges and situations, take that complex technology of all the ecosystems and translate that into showing the business what’s actually happening under the covers in a meaningful way. And that’s the basis of the report, is that the expectations are rising, the issues are out there. Finding them and fixing them, and really, put yourself in the consumer’s shoes, because it’s only going to grow, the dependency. And the flawless application wins.

    Ashley: Great. How do folks get a hold of this? How do they get to The Era of Digital Reflex report?

    Long: It’s posted on our AppDynamics website. It’s AppDynamics.com, and you can go ahead and get it there, and we’d be happy to share that.

    Ashley: Excellent. For you to download, I assume?

    Long: Yep, sure is.

    Ashley: Nice. Okay, well excellent. Thank you so much, Steve. Appreciate you being on DevOps Chat with us.

    Long: Thanks, Mitch. It was a pleasure, and I appreciate the invite.

    Ashley: Absolutely. I want to thank my guest today, Steve Long, regional CTO with AppDynamics. And of course we want to thank you, our listeners. We appreciate the time that you spend listening to us and ____ some feedback that you give. This is Mitch Ashley with devopsy.kinsta.cloud. Have a great day, and be careful out there.

    — Mitchell Ashley