AppSphere 15 - How AppDynamics is Shaking up the Synthetic Monitoring Product Space

This deck outlines what needs to be built in terms of data extraction, analytics, and other open source technologies. Finally, we’ll also discuss commercial alternatives and what features and functions are critical when monitoring micro-services based applications. Attendees of this session will walk away with a clear understanding of: -What is changing with software, and why? -What challenges are faced with these changes? -How to overcome these challenges. This deck was originally presented at AppSphere 2015.

Team Beachbody is a leading consumer fitness brand. In order to attract and retain customers, it is critical to provide an outstanding customer experience. Just as Beachbody workouts help customers get into shape, Team Beachbody found that they needed to apply the same rigour to their own website and apps to shape the end-user experience for their customers. In this session, learn how AppDynamics helped Beachbody adopt a DevOps culture with incentives a governance plan, and easily consumable process to hammer and chisel their apps and organization into shape. Like before and after photos showing the success of their customers, see how the Beachbody DevOps journey led to improvements in Direct and Network Marketing, Beachbody LIVE, and On-Demand Digital delivery. This deck was originally shared at AppSphere 2015.

Blue Cross Blue Shield Association (BCBSA) provides health insurance to over 105 million Americans through its network of 36 separate health insurance companies. It has been operating for over 80 years and is accepted by over 90% of doctors in the US. BCBSA has been mining its large healthcare data warehouse to ensure a great consumer experience while addressing an exponential increase in demand for its web services. It implemented AppDynamics to help address issues with system performance, slow response times, and increased time to resolve issues that were impacting customer satisfaction. AppDynamics helped identify inefficiencies in code and queries that were improved to enhance performance and scale capabilities to support growing demand.

Learn how Gannett used AppDynamics to make performance data actionable so product and development teams could collaborate to resolve issues faster by knowing exactly what the impact is of a performance problem and where to look to resolve it with correlated server side snapshots and combined Real-User and Synthetic monitoring to provide: -Consistent/Repeatable data for more sensitive and faster alerting -Deeper diagnostic data -Very specific availability/functionality monitoring of critical user flows -Assertions on page content/behavior -Dynamic baselines for tighter and more realistic performance thresholds This deck was originally presented at AppSphere 2015

AutoTrader has many tools to help solve problems, but they didn’t quite have them all. Their tool-belt was exceptionally stocked, but they were just missing that one key tool to help them really excel at rooting out their issues: AppDynamics helped fill that gap. Many of AutoTrader’s systems were already being supported by competing products, but after giving the product a few weeks to prove itself, it became very clear that AppDynamics was able to provide new insight into systems that were missed by other tools. The product has helped AutoTrader in many ways including reducing time-to-resolution for outages, rooting out inefficient code, and optimizing their services. These optimizations have led to a better customer experience, easier troubleshooting for support, and increased stability across all their platforms. This deck was originally presented at AppsSphere 2015.

AppDynamics Winter '16 (4.2) features new and enhanced APM, server, analytics, database, and EUM capabilities. Check it out!

This document compares the application performance monitoring (APM) tools AppDynamics and New Relic. It discusses their supported languages and environments, key features for backend, frontend, and mobile monitoring, how each tool helps users solve errors, pricing differences, and concludes that AppDynamics is better for on-premise use while New Relic caters more to startups and smaller businesses.

Oceanwide started its AppDynamics journey three years ago and relies heavily on it for its investigations of critical issues. Its usage—a mix of proactive alerting and reactive usage—has allowed Oceanwide to reach high standards of availability. Striving to adopt a DevOps culture, the broader adoption of AppDynamics across the company is a key focus. In this session, we will discuss how to work with developers and QA staff in their adoption of AppDynamics as well as key initiatives that enable them to use the solution as a common language when interacting with the operations team. Key takeaways: o How to promote and nurture the adoption of AppDynamics in developer and QA scrums o Key elements of a successful DevOps cell built around AppDynamics o How to establish AppDynamics as the common language between development, QA, and operations For more information go to: www.appdynamics.com”

The Container Store uses AppDynamics in their development lifecycle to gain visibility into their test environments and applications, set performance expectations before production deployments, and decrease performance test result reporting times. Some benefits included being able to identify testing requirements and gaps, fine tune alert policies prior to production, and getting results in 20 minutes instead of 5 hours. The presentation provided best practices around continuous monitoring, testing, and collaboration between development, operations, and business teams.

The document discusses the challenges of modern application monitoring and proposes a unified monitoring approach using AppDynamics. It notes that current monitoring tools often live in silos, lack context, and make it difficult to pinpoint the root cause of issues. A unified monitoring solution like AppDynamics breaks down these silos by providing a single view across infrastructure, applications and end users with situation-aware data and views. It aims to move organizations from reactive monitoring to more proactive approaches through intelligent anomaly detection, automatic runbook automation, and leveraging analytics to better understand patterns and trends.

This document discusses AppDynamics' capabilities for monitoring Docker containers: - AppDynamics provides unified monitoring of applications running in Docker containers, allowing visibility into both application and Docker metrics from a single interface. - An extension is available that collects Docker metrics using the Docker Remote API and displays them alongside application data in AppDynamics' dashboards. - A demo environment on GitHub contains an example of an application deployed in Docker containers that can be monitored end-to-end using AppDynamics.

Within IT Operations teams, one of the biggest pain points is problem isolation. Identifying which infrastructure component is responsible for a slowdown or outage is still extremely challenging due to fragmented tools without context. Visibility into servers and networks requires subject matter expert who come equipped with their own tools and preferences. AppDynamics' approach of unified monitoring helps tear down these silos with application context visibility into both the server and network. We will discuss and, of course, demonstrate how using AppDynamics Unified Monitoring helps narrow down application-impacting problems, which are a result of infrastructure, leading to dramatic reduction in MTTR. Key Learning: - What are the challenges facing today's infrastructure and operations teams? - Why it makes sense to correlate application performance (APM) with infrastructure - What are real world infrastructure problems affecting business transaction performance? - How to get, share, and socialize Infrastructure visibility provided by Unified Monitoring This deck was originally presented at AppSphere 2015.

The Xerox Government Solutions Health Enterprise Portal supports all of the Health Care Program and Decision Support needs for MMIS management for several states. The solution is based on different IBM products, leveraging IBM Digital Experience and WebSphere Portal Server, WebSphere Application Server, Smarter Process and IBM Security Solutions. To ensure the best possible performance for the users of this major enterprise solution Xerox and IBM worked on optimizing the performance of the solution. To monitor and troubleshoot the solution and optimize the performance AppDynamics Performance Management was used. The session will explain the business drivers, use cases, and architecture choices selected for deployment. We will also discuss in detail how the team leveraged AppDynamics and other tools to optimize and manage the performance of the enterprise health care solution. Join us for a real world showcase how performance was optimized for a state of the art enterprise Health Care solution. This deck was originally presented at AppSphere 2015.

This session will describe in detail why the World Bank chose AppDynamics for its Application Performance Management (APM) solution to align with its revamped enterprise monitoring strategy. The World Bank historically had many monitoring tools that were implemented in silos. Hear straight from this customer about the benefits of a consistent enterprise monitoring strategy in the wake of a tools consolidation. Key takeaways: o Benefits that the World Bank achieved by consolidating monitoring tools o Overall monitoring strategy and the value proposition AppDynamics allowed the World Bank to realize o Using AppDynamics every day for faster problem resolution and rapid service restoration For more information go to: www.appdynamics.com

The document discusses the challenges of managing the performance of revenue-critical applications deployed in hybrid cloud, virtual, and physical environments. It introduces AppDynamics as a solution that provides wide and deep visibility into distributed applications. AppDynamics dynamically scales applications in the cloud and other environments, is easy to deploy and use, and provides value quickly. The document also announces the free AppDynamics Lite product.

Accenture’s internal IT organization powers a digital business that supports the company’s growth strategy. To operate globally and virtually requires pervasive technology to be applied differently, and more quickly than ever. With hundreds of applications and platforms underpinning operations, monitoring, managing, and improving performance of applications is important. To help Accenture deliver high-performing enterprise apps to support 370,000+ employees in 120 countries, it deployed AppDynamics. Accenture’s performance engineering team undertook innovative programs to drive adoption. Explore Accenture’s deployment and maintenance approach, means of accelerating adoption, and keys to transforming digital operations. Key takeaways: • How Accenture internally deploys AppDynamics across hundreds of unique applications and provides periodic updates • How Accenture drives performance monitoring from a top-down perspective and standardizes its operations mindset across critical applications • How Accenture enables more than 1,000 users to track application performance within AppDynamics For more information go to: www.appdynamics.com

Cloud and microservices! With applications moving into these spaces, how do you monitor the platforms with performance in mind? The session will give you an under-the-hood view into the AppDynamics story for the new .NET landscape, and an end-to-end view of the Azure technologies and how we tie into it. Hear an architectural breakdown of the AppDynamics agent for Azure; the user experience design with continuous integration in mind; and the move to decouple dependency to support the Open Web Interface for .NET. Key takeaways: o How AppDynamics monitors the cloud o How to use AppDynamics to monitor the cloud o Designing for microservices o How the .NET agent is changing to decouple dependency on IIS For more information go to: www.appdynamics.com

Apps are continually changing: the way users engage with and find new content and application types is becoming more engaging. The key user interface change creating these compelling applications are single page apps. Measuring these is a challenge due to the number of frameworks and technologies used today. AppDynamics has created compelling new technology to measure real user experience for these new frameworks. Key takeaways: - Why customers choose Single Page App frameworks to deliver better user experiences - A model for effectively monitoring the performance of SPA apps - How AppD delivers on this model with a focus on Angular.js - How to think about "asyncronous" calls in a SPA world This deck was originally shared at AppSphere 2015.

Part I: Introduction to Cloud Computing - What is Cloud Computing? - Classification of Cloud Computing Part II: Introduction to Google App Engine - What is Google App Engine? - Why Google App Engine? - Core APIs & Language Support - Google App Engine for Business - Google App Engine Customers - Q&A

This document discusses how to develop PHP apps faster for the enterprise. It recommends automating deployment, implementing continuous integration and testing, and shifting testing left to catch bugs earlier. Automating infrastructure is also important to fully rebuild environments automatically after failures. Upcoming episodes will cover high availability, performance optimization, and other topics. Faster deployment cycles through automation can enable faster application development and feedback from users.

SMAC Toronto presentation with Mobile as the main theme for this event. Demos using IBM Worklight, Cloudant, App Inventor, and BLU Acceleration for Cloud

With businesses built around software now disrupting multiple industries that appeared to have stable leaders, the need has emerged for enterprises to create "software factories" built around the following principles: Streaming customer feedback directly into rapid, iterative cycles of application development Horizontally scaling applications to meet user demand Compatibility with an enormous diversity of clients, with mobility (smartphones, tablets, etc.) taking the lead Continuous delivery of value, shrinking the cycle time from concept to cash Infrastructure has taken the lead in adapting to meet these needs with the move to the cloud, and Platform as a Service (PaaS) has raised the level of abstraction to a focus on an ecosystem of applications and services. However, most applications are still developed as if we're living in the previous generation of both business and infrastructure: the monolithic application. Microservices - small, loosely coupled applications that follow the Unix philosophy of "doing one thing well" - represent the application development side of enabling rapid, iterative development, horizontal scale, polyglot clients, and continuous delivery. They also enable us to scale application development and eliminate long term commitments to a single technology stack. While microservices are simple, they are certainly not easy. It's recently been said that "microservices are not a free lunch". Interestingly enough, if you look at the concerns expressed here about microservices, you'll find that they are exactly the challenges that a PaaS is intended to address. So while microservices do not necessarily imply cloud (and vice versa), there is in fact a symbiotic relationship between the two, with each approach somehow compensating for the limitations of the other, much like the practices of eXtreme Programming.

As delivered to the Cloud Foundry Summit 2014 in San Francisco, CA: With businesses built around software now disrupting multiple industries that appeared to have stable leaders, the need has emerged for enterprises to create "software factories" built around the following principles: * Streaming customer feedback directly into rapid, iterative cycles of application development * Horizontally scaling applications to meet user demand * Compatibility with an enormous diversity of clients, with mobility (smartphones, tablets, etc.) taking the lead * Continuous delivery of value, shrinking the cycle time from concept to cash Infrastructure has taken the lead in adapting to meet these needs with the move to the cloud, and Platform as a Service (PaaS) has raised the level of abstraction to a focus on an ecosystem of applications and services. However, most applications are still developed as if we're living in the previous generation of both business and infrastructure: the monolithic application. Microservices - small, loosely coupled applications that follow the Unix philosophy of "doing one thing well" - represent the application development side of enabling rapid, iterative development, horizontal scale, polyglot clients, and continuous delivery. They also enable us to scale application development and eliminate long term commitments to a single technology stack. While microservices are simple, they are certainly not easy. It's recently been said that "microservices are not a free lunch". Interestingly enough, if you look at the concerns expressed here about microservices, you'll find that they are exactly the challenges that a PaaS is intended to address. So while microservices do not necessarily imply cloud (and vice versa), there is in fact a symbiotic relationship between the two, with each approach somehow compensating for the limitations of the other, much like the practices of eXtreme Programming.

This document discusses how IBM's UrbanCode Deploy product can be used to automate application deployments across hybrid cloud and multi-platform environments. It provides examples of how UrbanCode Deploy supports deploying applications to systems like IBM z/OS, distributed systems, private clouds, public clouds and PaaS platforms in an automated and unified manner using patterns and templates. The document also discusses reference architectures and case studies for implementing continuous delivery pipelines spanning both on-premise and cloud infrastructures.

App modernization projects are hard. Enterprises are looking to cloud-native platforms like Pivotal Cloud Foundry to run their applications, but they’re worried about the risks inherent to any replatforming effort. Fortunately, several repeatable patterns of successful incremental migration have emerged. In this webcast, Google Cloud’s Prithpal Bhogill and Pivotal’s Shaun Anderson will discuss best practices for app modernization and securely and seamlessly routing traffic between legacy stacks and Pivotal Cloud Foundry.

Adopting DevOps is not a “one-and-done” project. It is adopting a mindset, a culture. It is a commitment to a journey of continuous improvement by adopting a set of capabilities and practices that are based on Lean principles. Adopting DevOps requires process improvement, automation of the processes using tools, and organizational change to enable a DevOps culture. The question then becomes – where does one start?

Speaker: Kent Mitchell - Sr. Director of Product Management, Zend Technologies Developing today’s cloud-connected mobile applications is complicated. You have to develop mobile clients for each platform and form factor. You have to develop back-end services that run in the cloud to provide all the “heavy lifting.” You need to integrate to social networks and existing legacy systems. And the entire system has to scale seamlessly when you have the break-out success you know you’re app will bring. See why the combination of Zend, RightScale, PHP, and Apache Cordoba give you the solution you are looking for in the modern mobile world.

The document describes a case study of CollabNet implementing a CI-as-a-Service solution for a large financial services company with over 4000 users across 100 teams developing over 150 applications using multiple technologies. The solution involved provisioning Jenkins servers on demand using Lab Management, integrating tools like TeamForge, Subversion, Nexus and SonarQube on a common platform to provide standardized CI tooling and processes managed by a dedicated build engineer. This helped establish a collaborative development culture, improve productivity and reduce costs.

No matter the metric, serverless is definitely gaining interest. It’s the dream of every developer, supplying the ability to deploy services in the cloud in no time, automatically scale them, enjoy automagic management by a cloud provider—and, most important, keep it all cost effective! How does this dream become a reality? This session covered what serverless is all about and the benefits of running your apps in the serverless environment. It covers the monoliths-microservices-functions progression and when, where, and why to use serverless architecture and how Project Flogo fits in to the overall picture

Software development should not be a “black box” to the business, customers or other developers. Instead collaboration across stakeholders should be the norm--business, development and operations teams. Forrester recently reported that 13% of organizations doing Agile link “upstream” agile planning with ‘“downstream” development. As a result, executives continue to have only limited or no visibility beyond the initial planning stage of what is in a particular release. It’s not their fault, because today’s tools focus on upfront planning and don’t give you visibility into what’s happening in development. Often times that visibility is too late resulting in software that gets delivered and does not meet the customer’s needs. Join CollabNet’s most experienced senior solution architects as they explain how you can you gain real time visibility into all stages of the development process—from ideation into production through deployment. Imagine what can your teams get done if all stakeholders are able to collaborate together and view real time feeds into all stages of the delivery pipelines within a single easy-to-use system. Who Should attend: Any executive or manager interested in learning how to get traceability and visibility across the enterprise-- particularly, into the build and release management functions of their application lifecycle. What will be covered: An enterprise-scalable reference architecture for CI, CD, and DevOps The importance of build management, release management and application release automation integration A blueprint for scaling business agility across a large development organization How does CollabNet help organizations solve these problems A demonstration of TeamForge’s capabilities using Git/Gerrit, Code Review, Jenkins, Nexus, Artifactory, Chef and Automic