Rootly

"Legacy players in the space have only focused on step one of the entire incident management process — which is simply getting paged. Too many companies were paying a lot of money for this rudimentary ability. So now you get this feature with Rootly On-Call, but it's combined with our holistic platform that is collecting data throughout the entire lifecycle, through incident resolution." - JJ Tang for International Business Times Thank you to IBT Media for this piece highlighting Rootly is ushering in a modern era of incident management tooling 🚀 https://lnkd.in/dusDy3Vy

We’re looking forward to our meetup this Thursday with OpsLevel and the best and brightest Engineering leaders in Toronto! Want to join us? Leave a comment and we’ll do our best to get you on the list (it’s nearly full!)

Our Reliability Advocate Ashley Sawatsky will be speaking at DevOpsDays London about why incident playbooks can only take you so far. If you're planning to go, let us know! Haven't secured your ticket yet? Comment on this post and we'll send you a discount code 🎟️

Wise words on SRE anti-patterns from Ricardo Castro, FanDuel's Principal SRE 💡 "SRE is no exception when it comes to having anti-patterns. We see this in Agile, with DevOps, CI/CD, etc. It’s really about understanding “Where might we be going wrong?”, and to understand that, we need to understand “What are we trying to achieve?”. Companies can be quick to fall into new fads and think of them as the new tool or process they need to adopt, rather than asking themselves what problem they need to solve in the first place. Start with the problem and go back to first principals, then look at the tools and resources available, and pick the best one to solve it."

POV: You just declared an incident and not a single person has DM'd you "is something broken?" because Rootly already pushed a beautiful, clean incident announcement to your channel of choice, and is automatically keeping it up-to-date as the incident progresses 😌 Save time, build trust, keep your DMs clear. That's the magic of Rootly in Slack ✨ Our Incident Announcement and Incident Update blocks in Slack just got a little facelift. See the improvements in this week's changelog ➡️ https://lnkd.in/eQ9e4GY2

Introducing two brand new Humans of Reliability 🥳 These brand new episodes feature Mason Jones (Director of Engineering, Internal Platform at Zapier) and Ricardo Castro (Principal SRE at FanDuel). Tune in to hear us chat about: 🌱 The magic of startups and Mason's experience building engineering teams from 0-1 🔁 Ricardo's take on SRE anti-patterns and why Kubernetes isn't *always* the right answer 🇯🇵 How Mason's love of Japanese music led him to found his own record label 🪜 Ricardo's experience reaching the Principal level in SRE Both of these episodes are live now on our website YouTube channel! Enjoy! Watch now 🍿➡️ https://lnkd.in/gByTQ2xq

Calling all Toronto Engineering Leaders 📢 We're hosting a meetup with our friends at OpsLevel in downtown Toronto this month. This invite-only event is open to senior leaders in SRE, DevOps, Platform Engineering, and other related crafts. Whether you're looking to share insights, swap stories, or enjoy a cold one with some of the brightest minds in the industry, this is the place to be. Want in? Request an invite by sending us or JJ Tang a DM here, or emailing [email protected]. Space is limited and our events fill up quick, so the sooner the better 🥂

❌ "Rootly is a tool for incident experts." ✅ "Rootly is a tool that *creates* incident experts." One of the best parts of working with industry-leading reliability teams at companies like Canva, Cisco, and Elastic is that we learn alongside them and use those learnings to democratize the craft of incident response through our product. We're lowering the barrier to world-class incident response so companies of any size and stage can be equipped to handle their hardest days. What does this look like in practice? A platform that's packed with tried-and-tested practices, education, and default settings that actually work—all in a beautifully simple interface. Take a look at our Configuration pages to see what we mean.

Want to implement on-call without making your engineers miserable? Seasoned SRE Krishna Vinnakota shared his tips for reducing the burden of on-call shifts on Humans of Reliability, including: 📆 The sweet spot between on-call shifts that are too frequent (leading to burnout) and too infrequent (causing responders to feel nervous due to being "out of practice") 🤝 Using backup rotations so responders are supported when they need it 🌎 Building distributed teams so everyone gets a solid night's sleep without disrupting your 24/7 coverage ❤️ Creating a blameless culture that prioritizes the customer experience

"When we experience a stressful event, the amygdala, an area of the brain that contributes to emotional processing, sends a distress signal to the hypothalamus. This area of the brain functions like a command centre, communicating with the rest of the body to energize our fight-or-flight response. When this happens the part of the brain that is responsible for reasoning shuts down." 🧠 😬 It's a no-brainer (pun intended) that this is a problem for incident responders — we need to be able to manage cognitively complex thinking and decision-making tasks under pressure in order to respond to incidents effectively and learn through the process. So how can we contend with these challenges? Learning expert Sorrel Harriet distilled research into the subject into 8 practical tips for maintaining responders' capacity for learning in stressful situations on the Rootly blog: https://lnkd.in/gPP8RwAK