text stringlengths 0 2.35k |
|---|
**Outro:** \[56:37\] |
**Mat Ryer:** Have you learned how to play the riff? |
**Matt Toback:** I have not yet. But I have time. |
**Mat Ryer:** Okay. You should learn it. |
**Matt Toback:** On the airplane to Whistler I'm gonna take the piece out. My seatmate won't be terribly happy with that, but... |
**Mat Ryer:** "Please put your seatbacks and basses away. We're coming in to land." |
**Matt Toback:** You could do upright in the seat, maybe... |
**Mat Ryer:** You'd definitely get a ticket of like a double-bass. But you could also do Seinfeld links with it. You could make a little joke, a zinger to the staff... |
**Matt Toback:** Ba dom ba dowm bum bum |
**Mat Ryer:** Just do a bit of bass... That would be good, wouldn't it? \[laughter\] |
**Nayana Shetty:** Yeah, that would be nice. \[laughter\] |
• Observability strategies discussed |
• Nayana Shetty from Lego Group as guest expert on SRE and microservices |
• Challenges of scaling hundreds of microservices and maintaining reliability |
• Importance of site reliability engineering (SRE) in software development |
• Chronosphere mentioned as an observability platform for cloud-native teams |
• Rebuilding infrastructure as a service (SRE) and avoiding reinvention |
• Naina's experience with monitoring at GrafanaCon EU in Amsterdam |
• Tom joining the company and acquisition of Causal |
• Financial Times' monitoring challenges and legacy tools |
• Similarities between past and current monitoring use cases |
• Importance of thinking about future sustainability and operability |
• Carrot and stick approach to encourage teams to think about monitoring observability from the start |
• Observability and monitoring |
• The "carrot and stick" approach for motivating teams to prioritize observability |
• Importance of considering the long-term consequences of design decisions |
• Difficulty in retrofitting observability into existing systems |
• Designing for failure and error handling |
• Myths about building systems that will never fail |
• The importance of not immediately blaming the processor or physics when writing code that doesn't work |
• Benefits and limitations of pairing and mobbing in software development teams |
• Progression from manual testing to QA to SRE, and how it relates to incorporating testing into code |
• Observability and its integration with code, including the potential for a "click" moment where it becomes second nature |
• The importance of understanding criticality levels of applications and building observability around that |
• Two-level monitoring (application and system level) for different types of applications |
• Use of methods such as "use" and "red" to measure application performance and determine criticality |
• Monitoring should focus on business value rather than individual product team value |
• Investing in monitoring is worthwhile if it saves the company money by reducing downtime |
• Cost to operate and maintain monitoring systems is a key consideration |
• Mono repos can make it easier to apply changes across all relevant areas at once |
• Capability monitoring may be more effective for centralized teams, but its value varies depending on individual team needs |
• Centralized monitoring and communication challenges |
• Importance of showing value beyond just meeting requirements |
• Need for teams to be incentivized to use solutions with clear benefits |
• Difficulty in driving adoption without being overly prescriptive |
• Role of APIs in simplifying instrumentation |
• Common mistakes: providing too little or too much, not considering the product's life cycle |
• Challenges in implementing effective monitoring strategies |
• Challenges with saturation and alerting in monitoring systems |
• Importance of continuous experimentation and iteration in monitoring and observability |
• Value of delivering a complete solution to customers, not just tools or parts |
• Benefits of "you build it, you run it" approach, where teams are responsible for their own tools and data |
• Role of drills and incident simulations in preparing teams for real-world problems |
• Importance of practice in team environments |
• Interconnectedness of tasks and need for repeated practice |
• Value of drills vs shadowing in team learning |
• Benefits of using workshops and triads to practice skills |
• Use of documentation as a tool for learning and improvement |
• Introduction of Honeycomb for unified understanding of business drivers |
• Discussion of Acuity platform and its relation to Argo CD and Kubernetes |
• Kelsey Hightower's explanation of Argo CD as a transition from traditional CICD and how it represents each step in a workflow as a container snippet |
• Alert fatigue and the importance of having fewer, more relevant alerts rather than many irrelevant ones |
• Strategies for managing alert fatigue, including auditing and removing unnecessary alerts |
• Designing a system to prioritize alerts and remove unnecessary ones |
• Discussing the importance of regular "sanity checks" on alert systems |
• Sharing experiences with implementing emoji-based labeling for important alerts |
• Examining how open-source tooling affects transferability between organizations |
• Exploring the challenges of introducing new tools and processes in a new organization |
• Identifying core aspects of monitoring, including logging, metrics, alerting, tracing, and notifications. |
• The speaker endorses open source tools over proprietary ones due to ease of use and community support |
• Open source technologies are preferred for their transferability and ability to be taken with employees when they leave an organization |
• The speaker suggests focusing on capabilities rather than specific tools, such as observability, logging, metrics, and alerting |
• Recommended tools include Loki for logging, Prometheus and Graphite for metrics, Grafana and Kibana for visualization, and Slack or email notifications for alerting |
• The speaker relies on DevOps and monitoring communities to stay informed about emerging trends and technologies |
• Customer problem-solving approach |
• Value creation and multiple solutions |
• Prioritizing capabilities and principles over tools |
• Applying core principles across teams and companies |
• Practical advice for speaking and conference organization |
• Nayana Shetty's past talks and availability online |
• Matt Raya's wrap-up and closing remarks |
• Promoting the show to listeners and encouraging them to share it with friends |
• Mentioning Changelog++ membership program and its benefits |
• Asking for support through ads and membership |
• Announcing a free pack of stickers for new members |
• Expressing gratitude to sponsors (Fastly) and contributors (Breakmaster Cylinder) |
• Previewing an upcoming guest appearance by Dead Program |
[0.00 --> 2.78] Hey everyone, Jared Santo here, GoTime's producer. |
[3.24 --> 8.40] This episode is a bit different than what you're used to, but hopefully it feels familiar as well. |
[8.74 --> 13.44] We are helping our friends at Grafana Labs produce a podcast all about observability. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.