The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
Cattle, not pets is a DevOps phrase referring to servers that are disposable and automatically replaced (cattle) as opposed to indispensable and manually managed (pets). Local development environments should be treated the same way, and your tooling should make that as easy as possible. Here, I’ll walk through an example from one of my first projects at incident.io, where I reset my local environment a few times to keep us moving quickly.
Around six years ago on a Wednesday morning, software professionals worldwide were startled by a tweet from GitLab stating that they had accidentally deleted their production data, causing their site to go offline. Unfortunately, at that point in time, the open-source code repository giant had no idea that it would take them another 36 hours to restore their systems only to learn that 5,000 projects and 700 new user accounts were affected while they were fixing the outage.
IT people know that data is king, especially in optimizing IT operations. However, figuring out which metrics to collect and how to collect them can be challenging. IT teams have to factor in what IT directors, team managers, and the people overseeing operations want, what they’re concerned about, and what they consider important.
Several challenges impact customers and operations of utilities and energy companies, including aging infrastructure, cybersecurity threats, inclement weather, operational failures and transmission interruptions. These challenges can cause prolonged service disruptions, potentially leading to customer attrition and irreversible damage to businesses. Responding quickly and efficiently to incidents is critical to minimize damages or contain potentially dangerous scenarios.
