| In Reliability
This is the fourth in a series of posts on increasing overall availability of your service or system. Have you ever gotten paged, and known…
We support any monitoring tool that can send an email or make a JSON call, but we support tighter integration with some than others. We…
| In Reliability
This is the third in a series of posts on increasing overall availability of your service or system. In the first post of this series, we…
| In Reliability
Like pretty much everything else in Rails, optimistic locking is nice and easy to setup: you simply add a “lock_version” column to your ActiveRecord model…
| In Reliability
This is the second in a series of posts on increasing overall availability of your service or system. In the first post of this series,…
| In Reliability
As you may already know, PagerDuty suffered an outage of 30 minutes yesterday, followed by a period of increased alert delivery times. We’re taking the downtime…
| In Reliability
Updated on 9/21: We have replaced Twitter with our status page as a communication method. At PagerDuty we strive for 100% uptime, and it is a…
| In Reliability
Today, at around 1am Pacific Time, Amazon began having major problems with some of their cloud infrastructure: specifically with their EC2, EBS, and RDS offerings. We’d like to share some statistics on the alerts we sent out – via phone or SMS – during the outage.
| In Reliability
This post is meant as a quick introduction to some concepts of system availability, so that subsequent posts in this series make sense. I’ll go over concepts like availability, SLA, mean time between failure, mean time to recovery, etc.
| In Reliability
We’ve added deep linking to the incidents table. The browser will now remember all your interactions with the table as you move throughout your account or recall your bookmarks.
| In Reliability
We’ve been hosting PagerDuty on AWS for about the last year. One of the biggest draws to the platform for us was the promise of ready-built components…