Keptn is now a CNCF sandbox project bringing a new event-driven approach to continuous delivery and operations. While many are just hearing about Keptn the first time, it is interesting to learn more about how it started, which challenges the team ran into, what they learned about K8s, and running an open-source project. We therefore invited Johannes Braeuer (@braeuer_j) and Andreas Grimmer (@grimmer_andreas) – both Keptn project maintainers and contributors – who have been working on the Keptn project since its inception.
Especially for groups that want to start open-source projects or are on the brink of deciding pro or con Kubernetes should listen until the end as Johannes and Andreas tell us what they would do differently now if they would start today based on the learnings from the past 18 months.
If you want to join the Keptn community, make sure to star our GitHub project, join the Slack channel, and join our regular community meetings!
Johannes Bräuer on Twitter
Andreas Grimmer on Twitter
Getting visibility into .NET code whether it runs on a developer machine, on a windows server on-premise or as a serverless function in the cloud is the day2day job of Georg Schausberger (@BombadilThomas) and Bernhard Ruebl, part of the Dynatrace .NET Agent Team.
In this podcast we hear firsthand about the challenges in bringing observability, monitoring and distributed tracing to the .NET ecosystem. They give us insights about their continued effort to reduce startup and runtime overhead, the innovation that comes out of Microsoft as they are moving towards open standards and the noble automated approach to always validated things don’t break monitored code with the constant update of libraries and frameworks.
We also got both to talk about their developer experience when working with commercial tools such as Dynatrace and its PurePath technology as well as open source tools when analyzing and debugging their own code or helping users figure out what’s wrong with their code.
In the talk both mentioned other tools which we wanted to provide the links for:
IIS Module tracing
Successful Cloud Migrations, large scale Kubernetes & OpenShift deployments, making billions of data points actionable and enterprise-wide Citrix & SAP monitoring. These are some of the projects Kayan Hales, Technical Manager at Dynatrace, and her colleagues at Dynatrace ONE help enterprise customers around the world to implement every day.
We sat down with Kayan as we wanted to learn what really matters to many large organizations as they embark on automating monitoring into their hybrid multi-cloud environments. While we constantly talk about cloud native and microservices it was interesting to hear what the global team of Dynatrace experts is doing on a day-2-day basis. Kayan gives us insights how important it is to think about meta data, tagging strategies and automation before large scale rollouts and that one of the first question you need to ask is: who needs what type of data at which time through which channels.
Why do some organizations still see performance testing as a waste of time? Why are we not demanding the same level of performance criteria for SaaS-based solutions as we do for in-house hosted services? Why are many organizations just validating performance to be “within specification” vs “holistically optimized”?
In this episode we have invited James Pulley (@perfpulley), Performance Veteran and PerfBytes News of the Damned host, to discuss who organizations can level up from performance testing to true performance engineering. He also shares his approaches to analyzing performance issues and gives everyone advice on what to do to start a performance practice in your organization.
Imagine a future where we deploy every code change directly into production because feature flags eliminated the need for staging. Feature flags allow us to deploy any code change, but only launch the feature to a specific set of users that we want to expose to new capabilities. Monitoring the usage and the impact enables continuous experimentation: optimizing what is not perfect yet and throw away features (technical debt) that nobody really cares about. So – what are feature flags?
We got to chat with Heidi Waterhouse (@wiredferret), Developer Advocate at LaunchDarkly (https://launchdarkly.com/), who gives as a great introduction on Feature Flags, how organizations actually define a feature and why it is paramount to differentiate between Deploy and Launch. We learn how to test feature flags, what options we have to enable features for a certain group of users and how important it is to always include monitoring. IF you want to learn more about feature flags check out http://featureflags.io/. If you want to learn more about Heidi’s passion check out https://heidiwaterhouse.com/.
Adrian Hornsby (@adhorn) has dedicated his last years helping enterprises around the world to build resilient systems. He wrote a great blog series titled “Patterns for Resilient Architectures” and has given numerous talks about this such as Resiliency and Availability Design Patterns for the Cloud at DevOne in Linz earlier this year.
Listen in and learn more about why resiliency starts with humans, why we need to version everything we do, why default timeouts have to be flagged, how to deal with retries and backoffs and why every distributed architect has to start designing systems that provide different service levels depending on the overall system health state.
Adrian on Twitter: https://twitter.com/adhorn
Medium Blog Post: https://medium.com/@adhorn/patterns-for-resilient-architecture-part-1-d3b60cd8d2b6
Adrian's DevOne talk: https://www.youtube.com/watch?v=mLg13UmEXlw
DevOne Intro video: https://www.youtube.com/watch?v=MXXTyTc3SPU
Whether you are still researching on whether you need a Service Mesh or simple use a load balancer or if you are already deploying multi hybrid-cloud architectures and Service Meshes help you secure the location aware routed traffic. In both cases: listen to this episode!
We invited Sebastian Weigand (@ThatDevopsGuy) back to our podcast who wrote papers such as Building a Planet-Scale Architecture the Easy Way. In our episode Sebastian walks us through why Service Meshes have gained so much in popularity, what the main use cases are, how you should decide on whether or not use Service Meshes and which challenges you might run into as you expand into using more features.
Steve McGhee (@stevemcghee) is an expert in post mortems and SRE. He has learned the craft at Google, applied it at MindBody and is now sharing his experiences while back at Google to the larger SRE community. Listen to this episode and learn more about how post mortem analysis can be the starting point of your SRE transformation. How it can help reliability engineering to build and engineer systems that fail gracefully instead of causing full crashes or outages.
Steve also went into monitor what matters and only defining alerts on leading indicators with an expiration date – a fascinating concept to avoid a flood of custom alerting in production!
If you want to learn more from Steve or SRE check out these additional resources he mentioned in the podcast: The SRE I aspire to be (SRECon19) and his 2 blog part series on blameless.com.
Keep hearing the terms SLIs, SLOs, SLAs, Error Budgets and finally want to understand what they are, who should be responsible for and how they fit into SRE (Site Reliability Engineering)?
Then listen to our conversation with Sebastian Weigand who has been helping organizations modernizing not only their application stacks but also helping them embrace DevOps & SRE. Learn about who is responsible to define SLIs, what the difference between SLOs and SLAs are and what the difference between DevOps & SRE is in his opinion!
Sebastian, who calls himself “That Devops Guy” (@ThatDevopsGuy), also suggests to check out the latest free report on SLO Adoption and Usage of SRE as well as SRE Books from Google to get started with that practice.
In the podcast she references additional resources which here are the links for: The performance benefits of Variable Fonts, Mandy Michael (@Mandy_Kerr), Isabela Moreira (@isabelacmor) and A/B Testing with React (YouTube).
How do you prepare for a 2Mio concurrent user load that lasts for 7 seconds? What does the load infrastructure look like? How do you optimize your scripts? How do you deal with DNS or CDNs?
In this episode we hear from Joerek van Gaalen who has done these types of tests. He shares his experiences and approaches to running these “special event extreme load tests”. If you want to learn more make sure to check out his presentation and read his blog post from Neotys PAC 2020.
Have you ever burned 30k because you forgot to turn off your test VMs over the weekend? Have you ever accidentally deleted “the production table” because you thought you were connected to your dev database? We often only hear the good stories and not those that teach us about what we should not do in order to avoid disaster!
Join this episode where Justin Donohoo, Founder and CTO of Observian, tells us horror stories from his professional life that taught him great lessons on what not to do when moving to the cloud, re-architecture because of exponential growth or let the intern do things he/she shouldn’t do.
Goranka Bjedov has seen the different sides of Open Source while she was working for organizations such as Google, Facebook or AT&T Labs. Before she takes the stage at www.devone.at later this year she gives us her take on Scott McNealy’s quote “Open Source is free like a puppy is free”. Tune in and hear her thoughts on how to pick the right tools, languages or frameworks, how to grow a an open source project and what things you should definitely avoid.
Starting your new job as Infrastructure Engineer in a large bank with your to-be boss and his key architects just leaving feels like Chaos! Maybe that’s why Tammy Butow has made a career in Chaos and Site Reliability Engineering. In this episode, Tammy shares her experiences of bring reliability into highly complex systems at NAB, Digital Ocean, DropBox or now Gremlin through chaos engineering. You learn about the importance to know and baseline your metrics, to define your SLIs and SLOs and to continuously run your fire drills to ensure your system is as reliable as it has to be.
If you want to learn more check out Tammy’s presentations on speakerdeck and make sure to join the chaosengineering slack channel.
3 years ago, Adam Auerbach explained how he helped Capital One to automate performance into the DevOps Delivery Pipeline. In 2020, where IT Security is a hot trending topic, Adam works for EPAM and is back advocating for the same shift-left he as advocated for when it comes to functional or performance testing. But now – its about baking Security into your practices & culture. And he has a cool word for it: DevTestSecOps!
Listen in and learn which types of security checks can be fully automated in the different stages of the delivery pipeline. Also learn how to prioritize your vulnerabilities as you most likely end up with a lot of noise in the beginning. Adam also highlightes the following open source tools that will help in that transformation: getcarrier.io and reportportal.io.
DesignOps, just as DevOps or NoOps, is targeted towards increasing the efficiency and collaboration between designers and engineers in order to deliver better, intuitive and consistent user experiences. It requires changes in processes, people and tooling and is heavily driven by enabling engineers to become more autonomous when developing and delivering new value for their organization.
Join this podcast and learn from Ursula Wieshofer (@Ursula_W), UX Design Team Lead, as well as from Fabian Friedl (@fabian_friedl), DesignOps Team Lead, on how we live and breath DesignOps at Dynatrace. You will learn about the recently released OpenSource Design System Barista, how it enables our engineers to deliver consistent user experiences across all sorts of software projects and how we manage feedback through the Barista GitHub project for future innovation.
Also make sure to check out the recent blog posts UX Guilds as well as how we deal with the constantly changing requirements of our design teams.
We're back to our regular scheduled show!
Kelsey Hightower (@kelseyhightower) has worn many hats as it says on his bio but we also learned from him that he probably doesn’t have that many hats at home as he has been living a minimalistic life over the past couple of years. A philosophy as we learn in this podcast that also goes well when it comes to building your next platform on Kubernetes.
In this podcast we learn about the do’s and don’ts, how you should plan and test for k8s upgrades, which tradeoffs you have to take as it comes to performance, how to think about developer productivity on k8s and why it is important to read up on security as it relates to the software we build, deploy and run on our k8s clusters.
Thank you Kelsey for supporting our community with your time and expertise. Hope to have you back in the future!
We wrap up the last day of the Dynatrace Perform 2020 conference with an announcement of winners and learnings for the week
Vamos terminando el evento teniendo una platica con nuestro amigo Cesar Quintana quien tambien dio una vuelta por nuestro stand a platicar un poco de su experiencia en esta gran cxonferencia.
Andi Grabner, our man-on-the-street, gets the scoop on:
-NoOps: Reaching zero-incident prod through auto-remediation-as-code with Juergen Etzlstorfer
-Beyond thresholds – Find anomalies and reduce false positives with Thomas Natschlaeger
-Hybrid observability, from enterprise cloud to mainframe and everything in between with Alex Huetter