General on UserVoice

search notes

2012-02-01T11:22:17-08:00

Evans Fernandes suggested:
Ability to search notes. This way I know what the previous on call person did to resolve a recurring incident. This also ends up as a valuable knowledge repository.

add websitepulse integration

2012-02-01T06:21:32-08:00

Pawel suggested:
They support (among other) email, URL, instant messenger and SNMP trap alerting methods. We use email for sending alerts to PagerDuty, but that way PD will obviously not resolve the alert after it receives "resolved" email from websitepulse. That sucks.

Randomize ACK and RESOLVE buttons

2012-02-01T05:26:36-08:00

RJ Miguel suggested:
There are cases where the engineer oncall is accidentally pressing "4" when he is half-awake. I suggest that we create a feature to randomize the number to ensure that the engineer is fully awake. Better yet, instead of entering one number, why not enter 3 random numbers? ie 335 for ACK 452 to RESOLVE. In this way, we are sure that the on-call is fully awake.

Act as an LDAP slave, use data set as source for Users and Escalations

2012-01-31T15:30:51-08:00

Phillip Heller suggested:
Provide a mechanism to allow a user to replicate (possibly filtered) ldap data to you. The schema may include things like group memberships, contact mechanisms, and supervisor / subordinate relationships. Allow for some custom mapping within your web interface so that an admin may map ldap schema fields to things like next level escalation. Allow for an LDAP defined group to be placed into on-call (but, perhaps with exceptions configured within your product directly). Allow the individual users to login and manipulate attributes associated with the contact mechanisms which are defined within LDAP such as order, action, etc - and optionally augment those mechanisms, define new ones, etc.

Integrate grove.io

2012-01-31T15:24:56-08:00

Phillip Heller suggested:
Would be great to have an integration with Grove.io hosted web-based IRC, where upon being paged, a user might visit their dashboard and join the hosted grove.io chat specifically for the incident.

Integrate a Conference Bridge

2012-01-31T15:23:29-08:00

Phillip Heller suggested:
For those times when all hell is breaking loose, would be convenient to open a reservationless conference bridge directly within the interface, or see that one has already been opened. Would be great to just click a button to have the conference bridge call you, or even select the on-call users from other groups and have the conference bridge dial-out to them. Naturally, it'd offer them an opportunity to decline being joined into the bridge, or perhaps prompt them to select another one of their configured alert destinations to be dialed-in to the bridge or even provide a new number entirely.

Allow schedules with times, useful for out-of-business-hours only usage. [is now completed]

2012-01-30T14:37:44-08:00

We're a managed operations team and we're all on duty during business hours. Although we can of course config Nagios to only send email to PagerDuty out of business hours, it would be convenient if we could set those times up in PagerDuty. Also think of the situation where we want someone on duty during business hours, but the customer no longer wants to pay for our 24x7 support.

Auto Refresh for the "Home » Incidents" Page

2012-01-30T13:55:49-08:00

Edward M. Goldberg suggested:
I like to see the information very fast when I change tabs. If the page did an auto-refresh the information would show up faster.

Notify me when my duty is about to start [updated]

2012-01-27T20:20:25-08:00

I want to receive an e-mail 30 minutes before my duty is about to start. Otherwise it's really hard to keep track of when I should really be paying attention.

Nicolas Marchildon said:

I pretty satisfied by the calendar export function, which I imported into Google Calendar, which I configured to send me a daily summary of my agenda at the beginning of the day.

Notifications methods in escalation policies

2012-01-24T13:26:37-08:00

Andy Fletcher suggested:
Ability to configure method of contact used as part of an escalation policy. Example: Create a policy that contacts person 1 by email, person 2 by SMS and person 3 by phone. This allows for raising the importance by defining a more direct method of contact as the escalation policy proceeds.

Embeddable on-call schedule/escalation calendar

2012-01-23T07:24:49-08:00

Andy Fletcher suggested:
It would be great to be able to export a schedule view that includes the escalation policy and scheduling combined into one 'on call' style rota display. This could then be embedded into whatever page required. A bit like the google calendar embedding feature.

change the colors for on-call schedule; two people have the same color. [updated]

2012-01-18T10:42:36-08:00

Melanie White said:

Agreed. Would be very nice if you could select each users color?

Import/Export on-call schedules via iCalendar format [updated]

2012-01-05T14:52:00-08:00

Import on-call schedules from existing calendaring software or export the on-call schedules from PagerDuty so it can be imported into another calendaring software via iCal

Eric Liaw said:

I like this idea a lot, would love to see it.

Android App for PagerDuty [updated]

2012-01-05T04:38:47-08:00

Would be a great feature for those with Smart Phone

beorn said:

Insanely needed here.

Allow a user to mark themselves as on vacation to immediately skip them in notifications [updated]

2012-01-04T11:48:46-08:00

I recently went on vacation and had to change several services/escalations to remove myself so things would immediately go to the next person. So it would be great to add a check-box to the user profile where someone can just mark themselves on vacation so they are skipped immediately. If it's in the user profile then we don't have to edit several things.

Troy said:

This is a major request that is needed. By marking that I'm on vacation on specific days should remove me from the schedule and let the scheduling rules automatically pick the on-call person to take my place. Combining 2 schedules for a primary vs backup plus the complex rules in each schedule makes this feature a piece-of-cake.

The scheduling exceptions in the existing system is alot of unnecessary manual overhead. I'm not going to manually figure out who should replace someone for vacation 2-3 weeks in advance. The system knows, let it figure it out.

allow incidents from a phone call (1.800.xxxx #123) [updated]

2012-01-04T11:42:36-08:00

Allow users / clients etc to call in to a phone number to create an alert. Ideally the recorded message would be stored as an attachment to the alert.

Troy said:

This would be great for after-hour support where we need the on-call person paged when a user/client detects an issue. This would then allow one true on-call schedule that anyone can call into and get directed to the right person without necessarily having to answer the call directly. It also allows the escalation rules to work better so that the user is not waiting on the phone but know that they have paged someone to get back to them quickly.

There is another request to do schedule based call forwarding which is similar to this one. Having both features would be ideal, but I think taking a voice mail and then paging immediately works best in the long run.

For example, we don't want to wake up and talk to the user but now that they alerted us to the issue, we can take a minute to take a look and respond back through email.

This is not something that is easily done in all PBX systems because not all of them can send voice mail through email.

Add the ability to set a maintenance window for a service [updated]

2012-01-04T08:46:35-08:00

Jessica Murray said:

with API please

Not bury event details

2011-12-21T09:30:22-08:00

rainier suggested:
I feel like you bury event details. For example, to get the body of an emailed incident, the incident body isn't in the email from pager-duty (even truncated at some length), so I go to PagerDuty.com, log in, and go to the incident details page. Still, no real details. Then, I can scan through the Incident Log and find the original email, open it in a new tab, and see the details. It would be great if a) more details were in the original PagerDuty email, b) they were displayed on the incident details page, or there was some AJAXY UX better than opening a new tab. Partly it's our fault for not using super descriptive email Subjects. I don't know what you do with the 'details' hash from API created incidents, so I'll look into that, but my feedback still holds that more details should be in the email, and on the incident details page. There is another idea here for shorter emails, so maybe this could be another option for even more verbose emails...

Add more per-user reporting [updated]

2011-12-20T00:39:27-08:00

Would be useful to know the distribution of incidents across the team within a timeframe. Especially who handled the most incidents? Also would be good to track average time to acknowledge and time to resolution on a per-user basis.

Claudiu Ivanescu said:

I subscribe to this development, it would be very useful a report with all the incidents, who took it, when will did they, how much was between the incident and resolve moment.

Add more per-incident reporting [updated]

2011-12-20T00:39:19-08:00

Would be good to have more reporting showing the number of incidents over some time period to track the amount of alert activity. Ideally would be good to track that activity broken down by service, and even the message subject to see "hot spots" in the infrastructure.

Claudiu Ivanescu said:

I subscribe to this development, it would be very useful a report with all the incidents, who took it, when will did they, how much was between the incident and resolve moment.

Create a daily report/Search for incident [updated]

2011-12-20T00:38:13-08:00

At a user-configurable time, send an email to the oncall (or, again, user-configurable target) with the previous day's incidents, including incident description, id, start time, resolve time and duration.

Claudiu Ivanescu said:

I subscribe to this development, it would be very useful a report with all the incidents, who took it, when will did they, how much was between the incident and resolve moment.

Allow selection of notification method by schedule/priority [updated]

2011-12-15T18:32:26-08:00

For some schedules/services email/SMS notification is fine, and there's no reason to place a phone call. For others, I want every phone within 10 feet of me to go off. At the moment there's no way to vary this based on the severity of the event.

Ken Sheppardson said:

Duplicate of http://feedback.pagerduty.com/forums/18293-general/suggestions/193476-create-severity-levels-to-apply-to-alarms

Allow selection of notification method by schedule/priority

2011-12-15T18:30:10-08:00

Ken Sheppardson suggested:
For some schedules/services email/SMS notification is fine, and there's no reason to place a phone call. For others, I want every phone within 10 feet of me to go off. At the moment there's no way to vary this based on the severity of the event.

Decouple notification and event assignment

2011-12-15T18:24:54-08:00

Ken Sheppardson suggested:
At the moment the only escalation rule option is "Assign the incidents to X". Could you add a "Notify X" rule, that could be inserted between assignment rules? For example, I'd like to be able to be notified when something rolls over from the first responder schedule to the backup, but don't want to be assigned the issue directly.

API for read access to Incidents [updated]

2011-12-15T18:15:50-08:00

It'd be pretty awesome to have API access to pulling down Incidents as JSON or XML or similar. The use case I'm thinking goes like: we're getting a lot of noise into our pager rotation, and would like to start generating reports about what happened over the course of someone's shift. Hopefully, we'll be able to identify particularly noisy and annoying incidents, and figure out how to eliminate them. I did this by hand for my last shift, and it took 15-30 minute to copy pasta from the web interface and start to group the incidents by hand. I'd imagine a pretty small script or a tiny webapp to help automate that scraping and categorizing. Another case would be I'd imagine would be tracking how many incidents per hour or per day or whatever, and dumping that into scoutapp.com so we can get pretty graphs to track the rate that incidents come in.

Ken Sheppardson said:

This exists now, and works pretty well! I've used it to pull down a few months worth of incidents for analysis. Could certainly be expanded to provide information about the individual steps taken for each event, but it's a start.

http://www.pagerduty.com/docs/rest-api/incidents

allow a group to be on call [updated]

2011-12-15T18:12:40-08:00

We'd like to be able to have an entire group of people opt into being on "backup" duty, so that if the primary on-call person is incapacitated, the message will go out to anyone/everyone who is willing to take it.

Ken Sheppardson said:

I'd hope this could be implemented simply by allowing any number of users to be added to a group, with the ability to then add that group to a schedule just as you would a user. We'd use this both to escalate things to "All Hands" and to put users in groups on another parallel/shadow schedule for training purposes.

change the colors for on-call schedule; two people have the same color. [updated]

2011-12-13T14:34:38-08:00

Gordon Dunham said:

Would prefer more colors for personnel when working with large teams

change the colors for on-call schedule; two people have the same color. [updated]

2011-12-13T14:31:59-08:00

Michael McNeil said:

More colors would be helpful as well.

change the colors for on-call schedule; two people have the same color. [updated]

2011-12-13T14:29:30-08:00

Paul Tinsley said:

Very confusing with layers and overlapping schedules.

Android App for PagerDuty [updated]

2011-12-12T08:41:37-08:00

Would be a great feature for those with Smart Phone

Nate G said:

GREATLY NEEDED!!!

Android App for PagerDuty [updated]

2011-12-09T05:06:30-08:00

Would be a great feature for those with Smart Phone

Ulf said:

This is a deal breaker for us

Android App for PagerDuty [updated]

2011-12-08T19:10:32-08:00

Would be a great feature for those with Smart Phone

Christian Lavoie said:

Widget to show status and configurable notifications. Must have.

Android App for PagerDuty [updated]

2011-12-08T18:58:56-08:00

Would be a great feature for those with Smart Phone

Nicolas Marchildon said:

Widget should show who is on duty, and how many incidents are unhandled and acknowledged.

Add more per-user reporting [updated]

2011-12-06T13:56:04-08:00

Paul Badcock said:

This would be fantastic for our timekeeping of after hours support. The total hours would be good too

Show when a user is on call next - this was shown previously - no longer shown [is now started]

2011-12-05T15:43:31-08:00

Show when a user is on call next - this was shown previously - no longer shown [updated]

2011-12-05T15:43:31-08:00

Baskar Puvanathasan (admin) responded:

We'll be turning on this widget this week.

Show when a user is on call next - this was shown previously - no longer shown

2011-12-05T11:19:44-08:00

Delay non-urgent notifications [updated]

2011-12-01T18:07:52-08:00

Queuing or delaying notifications until business hours would be nice for things like failed backups -- things that are important, but not urgent. Ideally this would tie in with the priority metadata asked for elsewhere.

Kuang said:

Ditto on this one.

Another way to look at it is to slip the notification that come in when no one's on call to alert the next on call when that time comes.

UK calls [is now completed]

2011-12-01T12:39:28-08:00

I am very interested in using your service but we are based in the UK and could really do with some clarification about your UK phone costs?

UK calls [updated]

2011-12-01T12:39:28-08:00

I am very interested in using your service but we are based in the UK and could really do with some clarification about your UK phone costs?

Alex Solomon (admin) responded:

We fully support phone call and SMS alerts to the UK. Also, we don't charge extra for this; our standard pricing (http://www.pagerduty.com/pricing) applies to international alerts as well.

If you already have an account with PagerDuty, you have to explicitly enable international phone alerts. This can be done from the dashboard; there is a box in the top right corner of the page that allows you to enable the feature.

change the colors for on-call schedule; two people have the same color.

2011-12-01T09:58:36-08:00

Add the ability to set a maintenance window for a service [updated]

2011-11-30T02:48:24-08:00

William Roe said:

Add the ability to set a maintenance window for a service [updated]

2011-11-30T02:34:21-08:00

Victor said:

Add the ability to set a maintenance window for a service [updated]

2011-11-30T02:32:58-08:00

Marco Campana said:

Add the ability to set a maintenance window for a service [updated]

2011-11-30T02:28:49-08:00

emson said:

Man this would be so useful... please add it!

Add the ability to set a maintenance window for a service [updated]

2011-11-30T02:19:21-08:00

Oguz Huner said:

This would be perfect. +1

Add the ability to set a maintenance window for a service [updated]

2011-11-30T02:09:52-08:00

Matthew Hutchinson said:

Add the ability to set a maintenance window for a service [updated]

2011-11-30T01:58:29-08:00

Paweł Kondzior said:

It would be very useful to have this feature.

Add the ability to set a maintenance window for a service [updated]

2011-11-30T01:58:28-08:00

Piotr Usewicz said:

Sometimes when we do a deploy, it's a given that our services will trigger alerts, so we should ignore them for a scheduled period of time.

Add the ability to set a maintenance window for a service [updated]

2011-11-30T01:53:20-08:00

Marcus Mitchell said:

this would be a really useful feature when deploying.
currently we can disable a service but when deploying in the small hours of the morning it's very easy to forget to re-enable.
timed, commented scheduled maintenance windows would perfectly solve this issue.