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.
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.
Introducing Curated Arial Non-Orbital Navigation System or CANON.
4 min read
This is Part 1 in a multi-part series dealing with tips for being on-call.
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.
We've added a feature to notify customers when they approach and go over their alert quota.
1 min read
We're pleased to announce that Server Density, a provider of hosted monitoring service, supports out-of-the-box integration with PagerDuty.
1 min read
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...
We're pleased to announce that Cloudkick is the first monitoring tool to include out-of-the-box integration capability with PagerDuty.
2 min read
Announcing Nagios plugin for PagerDuty.
2 min read
We are launching three new features: Integration API, Nagios Plugin and Cloudkick integration.
2 min read
Set of new features to improve PagerDuty.
3 min read
We're happy to announce that we've released the new version of PagerDuty with multi-incident support.
6 min read
Preview of multi-incident support in PagerDuty.
5 min read
Announcing Alarm Auto-resolution
2 min read