Operations | Monitoring | ITSM | DevOps | Cloud


Speedrun to Signals: automated migrations are here

When we launched Signals to the world, we were excited to hear how our product resonated with many teams. But with that excitement came an understandable concern: how much time and effort will I have to put in to move from my existing provider to Signals? We hear you — that’s why we built the Signals Migrator tool. And we’re open sourcing it.

FireHydrant is now AI-powered for faster, smarter incidents

Over the last five years we’ve seen our customers run 583,954 incidents more efficiently thanks to a shared workspace, powerful Runbook automations, and auto-captured data. Yet despite a great deal of progress, incident efficiency hasn’t achieved peak potential. We talk to a lot of folks that are still stuck in the muck: new responders struggle to get up to speed quickly, incident commanders wade through post-incident drudgery, and knowledge silos prevent comprehensive improvements.

3 questions to ask of any DevOps tool in 2024

Is your DevOps tool stack out of control? I feel like every day, I talk to someone who feels this pain. The technological golden age of the past few years created a lot of niche tools, but now that CFOs and boards alike are demanding budget restraint, many of these tools are being scrutinized. The reality of the situation is that it’s not good enough for a tool to do one thing anymore.

Finally: alerting and on-call scheduling for how you actually work

TL;DR You deserve a better alerting and on-call tool. So we built Signals. In our early days, we often used the tagline, “You just got paged. Now what?” It encapsulated how FireHydrant solved for all of the messy bits that come after your alert is fired, from incident declaration all the way through to retrospective. At the time, we saw alerting and on-call scheduling as a solved problem.

New MTTX analytics to drive your reliability roadmap

Analytics are great. We can all agree there. But not all analytics are created equal. FireHydrant has long offered incident analytics dashboards that provide an in-depth look at the entire incident lifecycle. You can see how incidents impact services and teams, understand retrospective participation and completion, and even get insight into follow-ups. But great analytics do more than simply organize data. They help you tell a story.

The revolution in critical incident response at Dock: efficient integration and service improvement

In this article, we will explore how Dock is working to significantly enhance its response time to critical incidents, emphasizing effective integration between tools as key to success. We will address how we challenge the conventional approach by shifting the focus from Mean Time to Acknowledge (MTTA) to Mean Time to Combat (MTTC), a customized metric that measures the time between incident detection and effective communication involving professionals capable of resolving it.

The alert fatigue dilemma: A call for change in how we manage on-call

Once the unsung heroes of the digital realm, engineers are now caught in a cycle of perpetual interruptions thanks to alerting systems that haven't kept pace with evolving needs. A constant stream of notifications has turned on-call duty into a source of frustration, stress, and poor work-life balance. In 2021, 83% percent of software engineers surveyed reported feelings of burnout from high workloads, inefficient processes, and unclear goals and targets.

Better Incidents Winter Bonfire: Inside On-Call

Engineers are bombarded with pages left and right. There's uncertainty about how to escalate. A constant blur exists between what's urgent and what can wait. This never-ending ping-pong game takes a toll. Burnout creeps in, and your engineering culture has taken a nose dive before you know it.