Back to videos

How Notebooks Empower Your On-Call Teams

Some issues can't be automated. For things that require human judgment, we provide on-call teams with notebooks that are optimized for operations. That way you know what action to take and when.
2 min
play_arrow
Summary

Some issues aren’t automatable. For things that require human judgment, we provide your on-call teams with Jupyter-like notebooks that are optimized for operations.

Here’s how it works:

These notebooks get pre-populated with all the diagnostic information when an issue happens and include the entire decision tree with mark-down cells that describe what action to take and when.

Unlike a typical runbook, this isn’t a static object. It allows you to run something instantly, motivating you to keep it up to date.It’s useful for not just the DevOps team but also the support team.

You don't want to give your support team SSH access into the box, but won’t it be great if they could:
- diagnose and detect which issue should go to which engineers, or
- (even better) fix the issue themselves?

Our notebooks provide them with the required guardrails and definitions to do so.

Thus, it’s super valuable for:
- your team – because issues don’t circle among lots of people.
- your customer – because their downtime reduces dramatically.

Transcript

View more Shoreline videos

Looking for more? View our most recent videos
2 min
Shoreline Incident Automation Overview
Shoreline’s Incident Automation Platform was built to reduce manual and repetitive work, so that you can repair issues faster, increase team productivity, and eliminate thousands of hours of degraded service.
5 min
Reliability Engineering: The Southwest Debacle
Because it's less expensive and quicker for passengers, Southwest operates on a point-to-point model. Any disruptions in one route affect the entire chain. But to engineer a reliable architecture, you need to balance cost versus reliability in an economically constrained way.
3 min
How to Manage Your Operational Data Efficiently
"How long should we keep operational data?"