Alerting for
Modern DevOps Teams
Introducing Signals. Available this Winter.
It’s time to bring alerting and incident response together in a consolidated platform that helps you:
-
Stop paying a monthly fee for users who were never paged, streamlining your incident management program and reducing overall incident costs.
-
Make always-on systems compatible with personal life through easy-to-manage subscriptions and notifications (plus on-call shifts and substitutions), all inside Slack.
-
Page teams and services, and realize the promise of “you build it, you own it” while rapidly improving assembly time.
-
Reduce noisy alerts and only amplify the signals that require incident response.
In the beginning, mitigating incidents was truly a game of whack-a-mole.
An incident arose, and anyone holding a mallet beat it down as quickly as possible.
Over time, tools like PagerDuty came on the scene, and the Google SRE book was published. We started building software with reliability targets in mind, and had a primitive way of sounding the incident alarm and bringing in the firefighters.
Time marched on, and a new generation of tools was born. Now, when those responders were called up, they knew what to do. They began streamlining incident response efforts, creating sources of truth, and training their teams. There was just one problem.
Responders kept innovating. Alerting tools didn’t.
The way we build software continues to evolve and become more complex. And responders continue to adapt. They’re moving from monoliths to APIs and services, quantifying their downtime, and bringing even more control to the chaos of incidents with purpose-built software that works the way they do.
But alerting tools are still stuck in the past — as if microservices don’t exist and teams don’t own their services — and we need to keep moving forward.
It’s time to start thinking about the full incident lifecycle, from ring to retro.