DEV Community

Discussion on: Have you ever been on-call? What was it like?

Collapse
 
sqlrob profile image
Robert Myers

Yes, in multiple places, and it can be incredibly annoying, depending on how good the instrumentation is.

One place I talked them out of it, at least for nights. I calculated how much it cost for me to deal with the page, and also calculated how much business could be lost. There was several orders of magnitude difference, hundreds of dollars vs pennies, so the pager stayed off at night. So always make sure there's an ROI.

Far too common, happened just about everywhere I've ever been on call , is getting pages for events you can't do anything about. Either something that self resolved by the time it was looked at, or something I couldn't deal with. Site being down because of a hardware failure that IT was looking at, or someone doing a late deploy. Waste of time and sleep.

I agree, make sure you get paid, and also communicate that your daytime tasks might be affected by interrupted sleep, either by a page or concern of a page.

Collapse
 
ajvondrak profile image
Alex Vondrak

Far too common, happened just about everywhere I've ever been on call , is getting pages for events you can't do anything about.

Right in the feels. 💔 This is the problem with most alerts I've been through. Either it's just a noisy signal that doesn't indicate an actual issue, or the issue just isn't actionable.

Collapse
 
sqlrob profile image
Robert Myers

What's even more annoying is the times you DON'T get paged.

At one place where you'd a page if the wind blew wrong, got a call from Customer Service "Did you know the site was down?" Nary a peep from the pager.