If you’ve ever been on call, you know that the incidents don’t stop because you have the flu. Or when you’re attending your child’s high school graduation. Or, as I found out firsthand, even when you’re at your own wedding. Confucius once said, “If you have never had a major occasion happen while you are on call, then you may not have ever lived.” (Okay, I totally made that one up.)
There are a number of reasons why email is predominately used to manage an incident. Everyone usually has access to email and the email technology has already been “paid for”. Therefore it’s easy to think of email as being a cheap resource that’s easy for MSPs to use. But easy isn’t always best…or even appropriate.
What’s A Flat On-Call Structure? A flat on-call structure is an on-call schedule that has multiple people getting notified of the same incident at the same time. There’s no escalations, no hierarchy, no layers.
Antiquated pieces of technology create setbacks in every industry, and in healthcare – it’s the pager! Pagers are still being used even though they’re not HIPAA compliant and the infrastructure supporting them is dying out. That’s why doctors and healthcare personnel alike need an advanced way to communicate and protect patient information. Here are six reasons to think of pager replacement options.
Over the past decade, multiple scientific studies have confirmed what we in DevOps have known for ages: Being on-call is a pain! But just how bad is it?
