Operations | Monitoring | ITSM | DevOps | Cloud

Reliability is a constant for every technology, whether it’s cloud, microservices, or AI. Full transcript:  Just a few years ago everybody was screaming about microservices, "That's the wave of the future," and now everybody's looking at AI. No matter what the change in technology hot topic is, your reliability should still be at the forefront of everything that you're doing.

See what reliability means to Ganesh Seetharaman, Managing Director at Deloitte, and why it's more than high uptime. Full transcript:  Reliability to me is not about achieving mythical perfection. It's about embracing complexity, recovering quickly from failures or incidents, and building trust through transparency and adaptability.

Gremlin workshops give your team hands-on training with Gremlin so they can get real results and dramatically improve your reliability. Full transcript:  The goal of our workshops is really to accelerate you and the team in your reliability journey. Whether you're starting out for the first time, or you're a more advanced user, this workshop is really designed for you to take you to the next level.

Reliability results are more than whether your application is up, it's about proactive measurement and keeping it up. Full transcript:  Reliability results in my earlier career was, "Is there any downtime? Are there any errors that are getting thrown?" It's not a proactive way to measure your reliability. If you're measuring it in time of production, it's not gonna be an accurate reflection of what your reliability is. The way that my mindset has changed over time has been a proactive measurement. Before we ship something out, is this gonna be reliable from the start?

Part of the Gremlin Office Hours series: A monthly deep dive with Gremlin experts. Cloud providers like AWS give you plenty of tools to make your workloads more resilient, but it’s up to you to apply them. However, considering how complex some of these tools are, where do you start? And how can you be sure your systems are more reliable as a result?

As someone with Type 1 diabetes, reliability is a way of life for Nick Mason, Sr. Solutions Architect at Gremlin. Full transcript: Reliability isn't just a metric, to me, it's a mindset. As someone that works in site reliability engineering and also someone who lives with type one diabetes, the concept of reliability is deeply personal to me. In tech, reliability means building systems that are going to recover gracefully and in life with a chronic condition like diabetes, it's the same thing.

When your systems are reliable, it means your customers can count on your applications to be there for them. Full transcript:  To me reliability means a good night's sleep, and being able to confidently go to bed and wake up the next day feeling ready to get out there and do my best work and not worry about the experience that our customers might have had through the night.

Reliability means a lot of things to a lot of people, but it’s also essential for every digital business. That’s why we’re talking to reliability experts from all over to find out what reliability means to them and how you can improve it. Transcript:  You know, we're all out here building and operating digital businesses and like nobody's talking about reliability enough. We gotta talk about it. I can't stop talking about it and I've been on call for like 20 years.

Part of the Gremlin Office Hours series: A monthly deep dive with Gremlin experts. Do you know if your services can tolerate losing a node? What about an entire availability zone? Or a region? Large-scale outages aren’t unheard of. When you’re running critical services, it’s vital that those services can keep running even if an AZ or region fails. In addition to failing over, these services also need to scale quickly so traffic shifts don’t overwhelm your systems. How do you prove that a service is both scalable and redundant? The answer is with Fault Injection.

Part of the Gremlin Office Hours series: A monthly deep dive with Gremlin experts. Service meshes bring applications together, but not always reliably. Even the most well-configured Istio deployment can have unexpected reliability risks that aren’t apparent until you’re already in production. Latency, single points of failure, poorly defined APIs—these problems can grow beyond a single service and impact the user experience for your entire application.