The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
Constantly juggling IT incidents can be exhausting as you try to track and resolve them before they escalate into disruptions. With each incident demanding prompt and precise attention, keeping up takes significant work. However, you can manage these challenges more efficiently and with less stress and less risk by optimizing your incident-tracking process.
Although FireHydrant has spent five years focused on what happens after your team (erg, I mean service 🙄) gets paged, the topic of alerting often comes up in discussions with our community. People are tired of paying big bucks for software that’s expensive, bloated, and hasn’t seen much innovation. Clearly, there’s a problem here – and we’re tackling it head on.
It has been lightly revised and reposted with his permission from the original article on Medium. Leading major incident responses can be extremely stressful. You have to quickly gather an ad-hoc team, figure out what went wrong, identify a fix and make sure this doesn't make things worse, all the while with senior leadership breathing down your neck. Are we having fun yet? Many people think having a dedicated incident commander role will solve the problem.