Back to videos

How to Reduce On-Call Incidents

Shoreline's recent survey found that 48% of incidents are straightforward and repetitive while 55% of them escalate beyond the 1st line on call. If your on-call sucks, you must find a path to make incidents incidental.
2 min

Let me explain.

We did a recent survey at Shoreline and found that::
- 48% of incidents are straightforward and repetitive.
- 55% of them escalate beyond the 1st line on call.

That means even if someone from your 2nd or 3rd line is not on call this week, they’re still actively on call because a lot of the incidents are reaching to them anyway.

You can reduce incidents by asking yourself these 2 questions:

1. How do I automate these straightforward and repetitive things away?
2. How do I empower my 1st line with clear guide rails on diagnosing and dealing with an event before deciding to escalate it?

Thus, by automating repetitive things and providing your 1st line with pre-built diagnostics and a safe set of repair actions, you can:
- reduce the labor they have to put in,
- reduce the downtime for customers, and
- save your engineers from the frustration of being on call all the time.


View more Shoreline videos

Looking for more? View our most recent videos
7 min
Debugging an eCommerce Microservice - High Request Latency Debugging with Shoreline
Charles Carey, Shoreline CTO, walks us through Shoreline's automated runbook experience.
2 min
Why You Should Automate Production Ops
Most of the on-call issues are commonplace, which means they happen again and again. It’s important to automate these issues because it’s a one-time investment, doesn’t make mistakes, and stays with you forever.
3 min
How to Boost Reliability Without Hiring More SREs
How can companies increase reliability without hiring an army of engineers?