Operations | Monitoring | ITSM | DevOps | Cloud

Outages don’t have to be part of your life and engineers don’t have to burn out being a hero. Spread out your effort and build reliability without the drama. Transcript:  You should be great at dealing with outages, but your customers don't care. There's no medals here. No one should have incentive to be paged. There's nothing good about being in a war room for 10 days or in the holiday season in 12 hour shifts around the clock just in case something happens.

Amin Momin of @CapgeminiGlobal talks about reliability takes dedicated effort beyond just using the cloud and setting up failover. Full transcript: There are two misconceptions about reliability. One is people only think failover is reliability. Just doing the failover, that will be enough from the reliability point of view. That's the first one. And the second one: we are deployed into the cloud, so it is the service provider's responsibility to provide the reliability.

Reliability takes the whole team working together. Full transcript:  If you really want to get good at measuring your reliability, then you have to work together as a team. Once your software engineer organization has decided, "We're gonna test these applications to make sure that they have redundancy, availability, resilience." Just stick to that framework that you come up with as a team.

Proactive, regular reliability work is boring, repetitive, and EFFECTIVE. And if leadership wants the incredible results it brings, they have to encourage the right behavior.

Consistent systems are reliability systems according to Ganesh Seetharaman, Managing Director at @Deloitte. Full transcript:   Strong reliability is demonstrated when systems consistently work as expected even during peak demand or unexpected events. When issues do happen, they are resolved quickly and transparently so users experience minimal disruption. Reliability also means data integrity. No matter how much stress the system is under, information needs to be accurate and secure.

Ultimately, a system is reliable when customers and engineers can count on it. Full transcript:  When I get to hear stories like, "Hey, we just had our holiday sales event kick off and everything went smoothly and I didn't have to wake up in the middle of the night." That is really the true definition of reliability these people that are constantly hands-on keyboard in charge of making sure that people like myself and like you aren't impacted when we're going to, for example, buy a new pair of sneakers, or we're going to get some sort of limited edition release that's coming out, right?

“Reliability must be a crucial outcome for all of the architectures.” —Anish Behanan from @CapgeminiGlobal.

Reliability Intelligence draws on Gremlin expertise with every test to show you how the test failed and recommended remediation.

Hiring good engineers is important, but it’s not enough to prevent outages. You need to measure and track your risk to get real results. Full transcript:   My name's Jeff Nickoloff. I'm a principal engineer here at Gremlin.  What I hear non-technical functions talk about is really they are much happier to sort of lean on their great engineers. Oh, we've got a great engineering culture. "We don't have reliability issues because we hire the best people.".

Chaos Engineering is great, but by itself it can create bottlenecks that limit your reliability journey. FULL TRANSCRIPT: One of the things we've learned while building Gremlin and being the first Chaos Engineering tool to market is with all the greatness that comes with this approach, we've learned some of the downfalls, some of the drawbacks. And one of those is how you scale this practice.

Are your teams truly ready when they ship code? Amin Momin of @CapgeminiGlobal talks about how true reliability is the absence of uncertainty. Full transcript: Reliability to me signifies the absence of uncertainty.  Whenever we go to production, we don't want anything to be unknown.