Metrics Driven DevOps - Automate Scalability and Performance Into your Pipeline

Editor's Notes

• #2: Get your own Dynatrace Personal License @ http://bit.ly/dtpersonal Dynatrace Personal is the full Dynatrace AppMon Product. After 30 Days Trial Period it automatically converts to FREE FOR LIFE for your Local Workstation Apps If you want to learn more check out my YouTube Tutorial Channel @ http://bit.ly/dttutorials
• #3: I love metrics! And I think we need to make metrics-based decisions. There are different types of metrics and different visualizations
• #4: This is what you see when you walk in our engineering labs. Did I break the build?
• #5: The most basic metric for everyone operating software. Did my last deployment break anything? Is the software still available from those locations where my users are accessing the software? Use Synthetic Monitoring: http://www.dynatrace.com/en/synthetic-monitoring/
• #6: Even if the deployment seemed good because all features work and response time is the same as before. If your resource consumption goes up like this the deployment is NOT GOOD. As you are now paying a lot of money for that extra compute power Screenshot from Dynatrace AppMon
• #7: Another example. Deployment changed the memory allocation behavior of the app -> high object churn rate results in high GC -> results in high CPU!! Screenshot from Dynatrace AppMon
• #8: If you test for scalability make sure the application scales „linear“ – or at least as linear as possible. Not like in this case where twice the load required 4.8X the number of containers. Screenshot from Dynatrace AppMon -> comparing two Transaction Flows!
• #9: Using Docker or other container, cloud environments? Make sure you know how to monitor Screenshot from Dynatrace AppMon: https://community.dynatrace.com/community/display/DL/Docker+Monitor+Plugin
• #10: Monitor your end users after you deployed something. Learn who the are. Screenshot from Dynatrace AppMon & UEM: http://www.dynatrace.com/en/user-experience-management/
• #11: Monitoring user experience and impact on conversion rate Screenshot from Dynatrace AppMon & UEM
• #12: Understand user behavior depending on who they are and what they are doing. Screenshot from https://github.com/Dynatrace/Dynatrace-UEM-PureLytics-Heatmap
• #13: Does the behavior change if they have a less optimal user experience? Screenshot from https://github.com/Dynatrace/Dynatrace-UEM-PureLytics-Heatmap
• #14: Seems like users that have a frustrating experience are more likely to click on Support Screenshot from https://github.com/Dynatrace/Dynatrace-UEM-PureLytics-Heatmap
• #15: Another cool example of conversion rate compared to technical metrics
• #16: Where do all these metrics come from?
• #17: They come from tools. I work for Dynatrace and we provide all these metrics – but there are also other tools out there that do that job
• #18: Lets take one quick step back – why are we doing all of this? We all know that since then the world got divided into two big parties. So – just out of curiosity: who is using Apple vs Android? And who is using Windows?
• #19: The phones not only changed the way we communicate – it disrupted many other technologies as well. Look at this! Pope Election in 2005. A SINGLE hand up with an old phone taking a picture
• #20: In 2013 the „picture“ is totally different. The smart phones and tablets not only changing the way we communicate but also disrupting many other things such as taking pictures, getting light when you need one (torchlight), measuring your steps, ...
• #21: So – just to see the difference again in one picture!
• #22: Why are people so crazy about DevOps?
• #23: Because new innovative companies are disrupting existing markets by delivering better services faster
• #24: Annd IoT will show us a lot of new markets and we will see a lot of new companies that deliver new services for new use cases
• #25: This is Boston February 2015!
• #26: My IoT Example on smart roofs knowing how much pressure is on them already – notifying firefighters to clean them before it is too late: great use case for insurance companies.
• #27: We know that everyone these days can build a globally successful business with just an idea and a laptop. Such as Mark Z or the two tech brothers (12 & 14) founders of GoDimensions. They develop 12 Apps so far with more than 35k downloads. Their idol? Steve Jobs!
• #28: Just to get the basics covered: I hope everyone has their own definition of DevOps by now. It is a lot of things depending on whom to list to our which blogs you follow.
• #30: In case you are a “DevOps Virgin” I definitely recommend checking out The Phoenix Project (the DevOps Bible) and Continuous Delivery (which is what we actually all want to achieve): Deliverying software faster with great quality and without all potential mistakes that a manual and rigid process brings with it
• #31: They really follow the stories of the first generation Unicorn Companies
• #32: Several companies changed their way they develop and deploy software over the years. Here are some examples (numbers from 2011 – 2014) Cars: from 2 deployments to 700 Flicks: 10+ per Day Etsy: lets every new employee on their first day of employment make a code change and push it through the pipeline in production: THAT’S the right approach towards required culture change Amazon: every 11.6s Remember: these are very small changes – which is also a key goal of continuous delivery. The smaller the change the easier it is to deploy, the less risk it has, the easier it is to test and the easier is it to take it out in case it has a problem.
• #33: But it is not only about delivering features faster – it is also about delivering fast features! These stats come from here: http://nft.atcyber.com/infographics/infographic-the-importance-of-web-performance-20140913
• #35: But don’t make the mistake to blindly follow every unicorn out there  Taken from http://www.hostingadvice.com/blog/cloud-66-devops-as-a-service/
• #36: Its not about giving Devs Direct Access to Ops Deployments
• #37: If you just automate a process that hasnt yet had enough time for quality you will just produce bad software -> but faster 
• #38: If you have the freedom to add more features more rapidly make sure you measure if they are used. If not – take them out. This avoids piling up Technical and Business Debt
• #39: We can solve this by combining metrics (which we‘ve seen before) and measure them from Dev to Ops
• #41: I get most of my stories from my Share Your PurePath program which is a free offering for our Dynatrace Free Trial & Personal License users: http://bit.ly/dtpersonal
• #42: Because this is what might happen: If „Being DevOps“ just means you just increase the number of deployments then you are bound to fail. Here is an example of a bad web application. When deploying this more frequently you will end up in more war rooms
• #44: They had a monolithic app that couldnt scale endlessly. Their popularity caused them to think about re-architecture and allowing developers to make faster changes to their code. The were moving towards a Service Approach
• #45: Separating frontend logic from backend (search service). The idea was to also host these services potentially in the public cloud (frontend) and in a dynamic virtual enviornment (backend) to be able to scale better globally
• #46: The Backend Search Service Team did a lot of testing on their backend services. Scaling up and down on demand. All looked pretty good! They gave it a Thumbs Up!
• #47: On Go Live Date with the new architecture everything looked good at 7AM where not many folks were yet online!
• #48: By noon – when the real traffic started to come in the picture was completely different. User Experience across the globe was bad. Response Time jumped from 2.5 to 25s and bounce rate trippled from 20% to 60%
• #50: The backend service itself was well tested. The problem was that they never looked at what happens under load „end-to-end“. Turned out that the frontend had direct access to the database to execute the initial query when somebody executed a search. The returned list of search result IDs was then iterated over in a loop. For every element a „Micro“ Service call was made to the backend which resulted in 33! Service Invokations for this particular use case where the search result returned 33 items. Lots of wasted traffic and resources as these Key Architectural Metrics show us
• #51: They fixed the problem by understanding the end-to-end use cases and then defined backend service APIs that provided the data they really needed by the frontend. This reduced roundtrips, elimiated the architectural regression and improved performance and scalability
• #52: Lessons Learned!
• #54: Got this story also covered here: https://www.infoq.com/articles/Diagnose-Microservice-Performance-Anti-Patterns If we monitor these key metrics in dev and in ops we can make much better decisions on which builds to deploy We immediately detect bad changes and fix them. We will stop builds from making it into Production in case these metrics tell us that something is wrong. We can also take features out that nobody uses if we have usage insights for our services. Like in this case we monitor % of Visitors using a certain feature. If a feature is never used – even when we spent time to improve performance – it is about time to take this feature out. This removes code that nobody needs and therefore reduces technical debt: less code to maintain – less tests to maintain – less bugs in the system!
• #55: To sum it up: It starts with engineers. Do not even check in bad code. Look at the data tools such as dynatrace tell you!
• #56: And this is how it looks like with Dynatrace AppMon Test Automation Feature. We automatically montior every single test execution in your CI and analyze these metrics per Test and per Build. We automatically detect regressions as every metrics per Test will be baselined. This allows us to STOP A BUILD before it moves to other phases in the pipeline
• #57: Once deployed into production make sure you keep monitoring key metrics per feature. Screenshot from Dynatrace AppMon & UEM where we can monitor usage and key metrics per Feature / Business Transaction
• #58: In Production we monitor the same metrics for our services. Seeing if a recent deployment had any change in # of SQL calls for a particular feature or the # of internal Service Calls. Helps us to make sure that we do not make bad deployments – or at least be aware of it right away to take countermeasures, e.g: rollback or fix
• #59: Make sure you understand your end users Screenshot from Dynatrace AppMon & UEM: http://www.dynatrace.com/en/user-experience-management/
• #60: And learn to understand „how your users tick!“ Screenshot taken from https://github.com/Dynatrace/Dynatrace-UEM-PureLytics-Heatmap
• #61: If we do all that we can build a beautilful pipeline where quality metrics are enforced along the way!!
• #62: With that we can make our users happy 24/7 – at any load
• #66: Good news is that we have stories about the next generation Unicorns – Make sure you learn about how these companies transferred there business
• #67: Read the full story on my blog: http://apmblog.dynatrace.com/2015/05/29/velocity-2015-highlights-from-last-day/ Adam Auerbach from Capital One at Star West 2015 and Velocity 2015 Not a small software startup -> but an established financial company that transformed the way they develop and especially „Continuously Test“ Software!
• #68: Watch the full Verizon story from our PERFORM 2015 Recordings There is also going to be webinar in June where Nita goes into more details