FireHydrant is now available through AWS Marketplace
AWS Marketplace + FireHydrant: your path to easier compliance, consolidated spend, and faster procurement.
The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
AWS Marketplace + FireHydrant: your path to easier compliance, consolidated spend, and faster procurement.
Over the last 18 months at incident.io, we’ve done a lot of migrations. Often, a new feature requires a change to our existing data model. For us to be successful, it’s important that we can seamlessly transition from the old world to the new as quickly as we can. There are few things in software where I’d advocate a ‘one true way,’ but the closest I come is probably migrations. There’s a playbook that we follow to give us the best odds of a smooth switchover.
At incident.io, we deal with small incidents all the time—we auto-create them from PagerDuty on every new error, so we get several of these a day. As a team, we’ve mastered tackling these small incidents since we practice responding to them so often. However, like most companies, we’re less familiar with larger and more severe incidents—like the kind that affect our whole product, or a part of our infrastructure such as our database, or event handling.
When a serious incident occurs, time is essential. Streamlining different components of the incident response and management process can help minimize the time it takes to resolve an incident. Proper streamlining also helps reduce downtime, restore functionality, and potentially curtail the overall impact of an incident-not to mention the costs incurred during these events. This article examines several areas of incident management, the potential challenges of manual implementation, and how an automation platform can alleviate these challenges to provide a streamlined incident response process.