semicolon

20 ms·

1.
Taking Back DevOps(opslevel.com)
5 points by semicolon 6y ago|0 comments
2.
by semicolon 8y ago
OpsLevel | Software Engineer | Toronto, Canada | Onsite | Full-time | https://www.opslevel.com ~About us~ OpsLevel is a very early stage startup based in Toronto, ON. We're an experienced team of ex-PagerDuty, ex-Amazon, a
3.
Pressure Release Valves(blog.pagerduty.com)
2 points by semicolon 15y ago|0 comments
4.
A Standard Operating Procedure for when s*IT hits the fan(blog.pagerduty.com)
1 points by semicolon 15y ago|0 comments
5.
Better Optimistic Locking control in Rails(blog.pagerduty.com)
1 points by semicolon 15y ago|0 comments
6.
Availability lessons from shoe companies and ancient warlords(blog.pagerduty.com)
3 points by semicolon 15y ago|0 comments
7.
The ups and downs of availability(blog.pagerduty.com)
16 points by semicolon 15y ago|0 comments
8.
by semicolon 16y ago
Yes, a good escalation policy would have a primary responder, a backup or secondary, and then one or managers, going up the hierarchy. PagerDuty supports that and my next post will be on that topic. Having a good device is important too th
9.
by semicolon 16y ago
Nice; it looks like that pager was an Amazon one too. There was a time when the sound of my pager (or even my cell phone's SMS ringtone) would get my heart beating faster. Maybe this would be a good ringtone for being on-call: http://www.
10.
Tips and Best Practices for being On-Call(blog.pagerduty.com)
25 points by semicolon 16y ago|5 comments
11.
by semicolon 17y ago
This is a good point... the first step is getting ahold of the right person, but after that there will probably need to be some sort of dialog or coordination as the on-call person tries to gather more data about the issue, reproduce the p