Comments for PagerDuty Blog http://blog.pagerduty.com Tue, 06 Dec 2011 23:42:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on New PagerDuty Feature: Alarm Groups by Anonymous http://blog.pagerduty.com/2009/09/09/new-pagerduty-feature-alarm-groups/comment-page-1/#comment-398 Anonymous Tue, 06 Dec 2011 23:42:00 +0000 http://blog.pagerduty.com/?p=16#comment-398 Hi Philipp, Yes, this feature is still available. It is now called Escalation policies (http://www.pagerduty.com/tour/escalation-policies) Hi Philipp,

Yes, this feature is still available. It is now called Escalation policies (http://www.pagerduty.com/tour/escalation-policies)

]]> Comment on New PagerDuty Feature: Alarm Groups by Philipp Schneider http://blog.pagerduty.com/2009/09/09/new-pagerduty-feature-alarm-groups/comment-page-1/#comment-397 Philipp Schneider Mon, 05 Dec 2011 14:18:00 +0000 http://blog.pagerduty.com/?p=16#comment-397 The link to the page alarm groups does not exist: http://www.pagerduty.com/tour/alarm-groups Is this feature still available? The link to the page alarm groups does not exist:
http://www.pagerduty.com/tour/alarm-groups

Is this feature still available?

]]> Comment on The ups and downs of Availability by A Standard Operating Procedure for when s*IT hits the fan | PagerDuty Blog http://blog.pagerduty.com/2011/04/18/the-ups-and-downs-of-availability/comment-page-1/#comment-393 A Standard Operating Procedure for when s*IT hits the fan | PagerDuty Blog Tue, 08 Nov 2011 19:36:19 +0000 http://blog.pagerduty.com/?p=505#comment-393 [...] the first post of this series, we defined and introduced some concepts of system availability, including mean [...] [...] the first post of this series, we defined and introduced some concepts of system availability, including mean [...]

]]> Comment on iCal Integration and Hand-off Notification by Anonymous http://blog.pagerduty.com/2011/10/25/ical-integration-and-hand-off-notification/comment-page-1/#comment-391 Anonymous Wed, 26 Oct 2011 02:24:00 +0000 http://blog.pagerduty.com/?p=1437#comment-391 Oops, I forgot to mention it was still in beta, I'll pass your name along to the support team. Oops, I forgot to mention it was still in beta, I’ll pass your name along to the support team.

]]> Comment on iCal Integration and Hand-off Notification by jelder http://blog.pagerduty.com/2011/10/25/ical-integration-and-hand-off-notification/comment-page-1/#comment-390 jelder Wed, 26 Oct 2011 02:01:00 +0000 http://blog.pagerduty.com/?p=1437#comment-390 Great news! I've been looking forward to this for ages. One problem: it's not enabled for my account yet. (locamoda.pagerduty.com) Great news! I’ve been looking forward to this for ages. One problem: it’s not enabled for my account yet. (locamoda.pagerduty.com)

]]> Comment on The ups and downs of Availability by Reducing MTTR – Lessons from Nike and Sun Tzu | PagerDuty Blog http://blog.pagerduty.com/2011/04/18/the-ups-and-downs-of-availability/comment-page-1/#comment-384 Reducing MTTR – Lessons from Nike and Sun Tzu | PagerDuty Blog Mon, 03 Oct 2011 22:01:53 +0000 http://blog.pagerduty.com/?p=505#comment-384 [...] the first post of this series, we defined and introduced some concepts of system availability, including mean time [...] [...] the first post of this series, we defined and introduced some concepts of system availability, including mean time [...]

]]> Comment on PagerDuty at HostingCon 2011 by Taka http://blog.pagerduty.com/2011/08/05/pagerduty-at-hostingcon-2011/comment-page-1/#comment-378 Taka Wed, 10 Aug 2011 21:22:00 +0000 http://blog.pagerduty.com/?p=965#comment-378 hey nice seeing you at hostingcon. thanks for the pen and t-shirts ^^ hey nice seeing you at hostingcon. thanks for the pen and t-shirts ^^

]]> Comment on Outage Post-Mortem by Wes Winham http://blog.pagerduty.com/2011/08/10/outage-post-mortem/comment-page-1/#comment-377 Wes Winham Wed, 10 Aug 2011 20:38:00 +0000 http://blog.pagerduty.com/?p=1110#comment-377 Thanks for the thorough post-mortem. I appreciate the openness. Thanks for the thorough post-mortem. I appreciate the openness.

]]> Comment on New APIs Available Now by John Laban http://blog.pagerduty.com/2011/06/20/new-apis-available-now/comment-page-1/#comment-374 John Laban Wed, 03 Aug 2011 20:22:00 +0000 http://blog.pagerduty.com/?p=757#comment-374 Hi Neil, You bring up a lot of good points.  We could definitely use more generic reporting functionality in PagerDuty, and it's on our roadmap, but probably won't be tackled in the short term (i.e. 2011).  We didn't want to block our users though, so it's one of the reasons we opened up the API for you guys. That being said, you can already do *one* of your (many) above wishes, so I figured I'd point that out, as a meager peace offering: > I can't choose to just look at one of the dozen services we have set up. If you click on the service in question in the Services tab, you should be see only the incidents that have been opened against that service in the past.  It's pre-filtered, but in other respects the incident view there is the same. Hi Neil,

You bring up a lot of good points.  We could definitely use more generic reporting functionality in PagerDuty, and it’s on our roadmap, but probably won’t be tackled in the short term (i.e. 2011).  We didn’t want to block our users though, so it’s one of the reasons we opened up the API for you guys.

That being said, you can already do *one* of your (many) above wishes, so I figured I’d point that out, as a meager peace offering:

> I can’t choose to just look at one of the dozen services we have set up.

If you click on the service in question in the Services tab, you should be see only the incidents that have been opened against that service in the past.  It’s pre-filtered, but in other respects the incident view there is the same.

]]> Comment on New APIs Available Now by Neil Silverman http://blog.pagerduty.com/2011/06/20/new-apis-available-now/comment-page-1/#comment-373 Neil Silverman Tue, 02 Aug 2011 21:34:00 +0000 http://blog.pagerduty.com/?p=757#comment-373  Um... please don't take this as a knock, because I really like your service, but your Incidents page is really only useful for looking at currently open/active incidents.  It's not much use in reporting on resolved incidents.  I'd like to be able to slice and dice the data - for example, show me all incidents, including times to resolution, opened between and from service Z, grouped by assignee.  In other words, I want a genuine report builder.  The incidents page has very little searchability or data filtering capabilities - sure I can look at Resolved issues ordered by open time, but we have over 100K resolved incidents, that I can't filter in any meaningful way.  I can't choose to just look at last month, or last week.  I can't choose to just look at one of the dozen services we have set up.  I can't look at issues resolved by a particular employee.  With your API, one can pass in "search parameters", and get back useful data sets, thus allowing much more useful and targeted reports to be generated.  This is definitely something we would like.  I'm a good enough Perl programmer that I can certainly do it myself, but it's a not-insignificant work effort on an already busy schedule, so I didn't want to start without double-checking whether or not you already have plans on your roadmap to introduce a report builder / beef up the incidents page with search/filter capabilities.  If you do, I'll just wait.  Um… please don’t take this as a knock, because I really like your service, but your Incidents page is really only useful for looking at currently open/active incidents.  It’s not much use in reporting on resolved incidents.  I’d like to be able to slice and dice the data – for example, show me all incidents, including times to resolution, opened between and from service Z, grouped by assignee.  In other words, I want a genuine report builder.  The incidents page has very little searchability or data filtering capabilities – sure I can look at Resolved issues ordered by open time, but we have over 100K resolved incidents, that I can’t filter in any meaningful way.  I can’t choose to just look at last month, or last week.  I can’t choose to just look at one of the dozen services we have set up.  I can’t look at issues resolved by a particular employee.  With your API, one can pass in “search parameters”, and get back useful data sets, thus allowing much more useful and targeted reports to be generated.  This is definitely something we would like.  I’m a good enough Perl programmer that I can certainly do it myself, but it’s a not-insignificant work effort on an already busy schedule, so I didn’t want to start without double-checking whether or not you already have plans on your roadmap to introduce a report builder / beef up the incidents page with search/filter capabilities.  If you do, I’ll just wait.

]]>