The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
We’re a small startup (10 people at time of writing) with big ambitions, particularly when it comes to our product. With so many things we want to do, it’s important for us to be structured the way we approach our work, without being so process-driven that we lose all the benefits of being small and nimble. As we’re still new, and the team is growing all the time, very little is set in stone.
We wrote this article in response to a question asked in our Slack Community. Click here to join hundreds of technology leaders discussing best practices for incident response! ✨ We know a thing or two about incident response. As such, we're often asked to advise when companies are designing their incident response processes. A common question is "How do you design your incident severity levels?". It's a great question given how central they are to incident response!
When you think of who uses feature flags, your mind most likely goes to developers. In general, feature flags are closely associated with software engineering. But Site Reliability Engineers, too, can benefit from feature flags. SREs may not be the ones to create feature flags, but they should work closely with developers to ensure that the applications their teams support include feature flags.
Runbooks have been a game changer for many incident response teams, and we just made it easier for you to get up and running with them. Runbooks reduce toil for responders and ensure consistency in your incident management processes.In the thick of trying to resolve an issue, remembering things like emailing customers is likely the last thing on responders minds but yet forgetting to do so can be detrimental.
Over the last few years, our world has become increasingly digital, from streaming and shopping to work and health care. Customers want these digital experiences to be seamless. This has become a key priority for all businesses as well, as they depend on happy customers to drive sales and brand reputation. To ensure these seamless digital experiences, technology teams have doubled down on reliability, user experience, and building new features.
With our February update, it is now possible to centrally configure how Signls should be notified. And of course, each team can have a different configuration of their notification preferences. This also includes response and escalation settings. In addition, it is now possible to set different notification patterns per day and time of the day, e.g. to notify via different channels at night than during office hours.
