Operations | Monitoring | ITSM | DevOps | Cloud

Part of the Gremlin Office Hours series: A monthly deep dive with Gremlin experts. Pop quiz—what are all of the dependencies your services rely on? If you’re like most engineers, you probably struggled to come up with the answer. Modern applications are complex and rely on dozens (if not hundreds) of dependencies. Many teams rely on spreadsheets, but manual processes like these break down over time. What if you had a tool that found and tracked dependencies for you?

For a lot of teams, incident management can be a bit of a headache. It's stressful. It's not optimized. The whole process can feel like it's being held together with tape. Worst of all? Responders are the ones feeling the brunt of it. But in reality, your customers are, too. Think about it: But honestly, the situation doesn't even have to be so dire. Things can be, generally speaking, totally fine. But you recognize that there are some things that you can do to make incident response really shine at your organization.

DevOps solutions have evolved quickly over the last few years. Software catalogs have bloomed beyond service registries and runbooks into comprehensive, centralized engineering sources of truth. With ever-expanding developer tool sets, can teams achieve the flexibility needed to address this fragmentation while continuing to tailor software catalog entries to their unique domains and contexts?