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
1 min
Using to root-cause transient issues (like JVM garbage collection)
Shoreline makes it easy to collect diagnostic information when you're doing a root-cause analysis of an issue.
3 min
Shoreline makes Production-Ops smarter and faster
Often people try to build a solution like Shoreline on their own. Here's why they fail.
3 min
Actively Managing Systems to Improve Utilization
We're all being asked to do more with less now a days. For those of us in production operations, one of the best ways we can do that is eliminate waste with automation to drive higher utilization.