List of videos

Chris Riley - Senior Technology Advocate @ Splunk Responding to incidents is not just about wiring up the right tools, it’s also a strategy and process to know how to respond, how to record details of incidents, and how to learn from them after everything has been resolved. There has been a lot of confusion about the relationship of incident response to incident management, and alerting. In this session we will talk about the differences and the best practices for these key processes in healthy cloud operations environments. Expect to learn in this session. 1) What is an alert and how does it feed incidents 2) What is the difference between incident response (IR), and incident management (IM) 3) What are the best practices for IR and IM tooling 4) How incidents are being handled in modern dev environments We will also talk about on-call scheduling, shift-left, and how machine learning supports incident response strategies. Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk

Hari Krishnan - CEO @ Polarizer Technologies Does your team have to deal with performance issues late in their dev cycle? Does this lead to a lot of unplanned work in your sprints? What if I told you, that your team can validate performance-related hypotheses right within your sprints and on their local machines? Attend this talk to know more. Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk

Josh Armitage - AWS Practice Lead @ Contino How can you strip over-processing out of your value stream? How can you understand and communicate what “good enough” looks like? How can you systematically challenge and remove assumptions from you consumers? In supporting enterprises in DevOps & agile transformations across three continents, I discovered a common theme, stories talk of what is to be enabled, but not how well it needs to perform. Recently, upon joining a platform team drowning under the weight of their backlog, I experimented with SLOs being the beating heart of our product development flow. To do this, we: - Revisited all previous core usecases and determined meaningful SLIs and SLOs - Made SLOs an inherent part of defining features - Built a lightweight infrastructure to translate technical changes to business events - Made a dashboard to transparently broadcast our SLOs - Made SLOs be the core of conversations with our consumers By doing this, we: - Removed assumptions from consumers, driving more meaningful conversations about value - Created a beachhead for a more data driven culture - Created a common understanding of what “good enough” looked like - Became better focused on maximising value delivery, over redundant gold plating of features You’ll learn: - How to adopt an SLO driven product development flow - From the mistakes we made along the way - Tips and tricks for defining SLOs for low frequency usecases - How to drive more impactful conversations Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk

Yishai Beeri - CTO @ LinearB If you only measure one metric this is it: Cycle Time. It is probably the most underrated and least understood metric in engineering. Yet this is the metric that comprises the most important aspects to measure in your engineering process. Here’s why. High performing teams know it’s a marathon and not a sprint, that a steady and swift flow of value wins out in the end, and shipping many small improvements quickly in aggregate translates to great gains for your organization (in the spirit of kaizen). The way to do this is by ruthlessly removing productivity killers like context switches, work in progress culture, and dead value that isn’t shipped. By measuring the process, and not the individuals you are putting your emphasis on the team effort, which is great for culture - in contrast to highly toxic individual performance metrics. This talk will focus on how to fine-tune and get Cycle Time right. It’s a mix of improving your planning, interfaces between product and engineering, communication, review and quality gates and release mechanisms, essentially everything your engineering process encompasses. If you can game this metric, then you will realize huge gains for your entire dev process and engineering organization. Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk

Marco Coulter - Technical Evangelist @ Tech-Whisperer.com The concepts of SLI, SLO and Error Budget are there to balance risk (rates of change) and reward (business contentment). Using such metrics as red lines to punish teams, or force acceptance of risk by the business is missing the point. My experiences from SLA’s in service contracts for hospitals inform this conversation identifying that SLI, SLO and Error Budgets are better as a basis for conversations about the stress an application can withstand, and the three dimensions the measures should cover. This session takes Goodhart’s law from economic policy as a frame for reconsidering SLI’s and SLO’s, and offers a few hints for approaching the negotiation meetings. Leave this session inspired to approach your SLO negotiations in the best possible way. Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk

Andrew Kirkpatrick - Staff Engineer @ PartnerStack Maintaining your whole infrastructure using Terraform and reusable modules makes most of our lives easier, but when those less familiar with “DevOps” want to create or update resources, you usually either have to train and enable them to use Terraform, or handle the request yourself. However what if you could offload the execution of those changes to a centralised tool and just review both the code and output being submitted for review? Atlantis, Terraform Cloud or env0 can act as a PR-based feedback loop for a hosted Terraform executor to make self-service a little bit easier. Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk

Filipi Pires - Principal Security Engineer @ Talkdesk Practical demonstration of how a Developer can use a SAST tool for static analysis in code vulnerability, executing it in source code, byte code and/or binary and identifying security holes during the development process, analyzing many languages and codes, like as, C, C #, Java, Kotlin, Python, Ruby, Golang, Javascript, JSON… And searching for key leaks and security flaws in all files of your project, as well as in Git history and in addition to receiving a managerial view with all this analysis information. Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk

Rob Richardson - Developer Advocate @ Cyral Are you looking to rapidly deploy your content? Are Docker containers in your future? Come for this demo-only presentation where we start from scratch, build up a DevOps pipeline in GitHub Actions, and deploy to Kubernetes. Once setup, commit, and watch the magic flow into place. You too can automate your deployments. Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk

Yshay Yaacobi - CTO @ Livecycle It has become increasingly difficult and time consuming to start working on a new codebase, especially in a polyglot microservice world. Using several patterns and developer containers we can create an amazing developer experience that will allow anyone to instantly deep-dive into coding on any machine. This talk will introduce the concept of a self-contained repository - a repository that contains all relevant information for workstation/dependency configuration, build, debug, CI/CD, secrets (encrypted), docs and more that reside in the repository. We’ll explore the idea of a development container and how we can use free OSS technologies (like Git Docker & Docker Compose, Kubernetes, GPG, VSCode, Tilt…) to create a stable development environment that works out-of-the-box and provides all the power, speed and capabilities of modern development & cloud native tooling. Live code examples will be showcased as part of this talk. Other talks at this conference 🚀🪐 https://www.conf42.com​/sre2021 — 0:00 Intro 1:16 Talk