PagerDuty Operations Cloud Reviews

Obviously, scheduling the calls is a valuable feature. We have a feature where there were three calls: primary one, primary two and primary three. If this guy doesn't pick up, it will respond a certain way; that's the most valuable feature. We use it on the weekends. If some customer escalates, I'll get a page, if my manager doesn't pick up. That's one of the great features; I love it.

I would like to see them increase the content base and add integrations with different systems, for example, with ZenDesk or Slack; if it could integrate more with those types of systems. We use ZenDesk; I’d like to link this to ZenDesk. I’d like more integration points.

There has been some downtime, but it did not impact the business. It's pretty stable. It's reliable.

It's scalable. They have a very flexible billing system. There is a minimum of 15 or 20 numbers or users. If you add more money, you can add more users. It's pretty scalable. We haven’t experienced any scalability issues up until this point.

Their technical support has excellent notes. When you get notified, you can instantly see all of the details, organized on a timeline. That is very good technical support.

When I joined the company, it was already there; they were already using it.

Upgrades are straightforward; there are no major hassles.

Evaluate your requirements first. Determine the number of users. What is your user base? Are you going to grow more? That's what I would decide.

When I select working with vendors, I look for a more reliable solution. I want something that meets my requirements. I don't worry about the UI and stuff like that, as long as it's reliable; as long as it meets the SLAs.

The outbound calling feature is a feature that I find a lot of value from.

We use this in conjunction with SolarWinds so that the on call and backup get paged if something is down. Before with just SolarWinds native alerts, we missed some critical alerts.

I would defiantly like to see more integration with other systems. This would really add some value for us.

1 year.

We haven't had any issues with stability.

So far the product has scaled as we have needed it to.

As we haven't had any issues we have not had to call customer service yet.

SolarWinds.

Set up was straightforward as it integrated with SolarWinds right out of the box.

In-house.

Because of this product we have less business critical applications being down for lengthy periods, which is invaluable.

The price just increased, so the value to dollar went down a little bit. The previous price was about the sweet spot per person.

There are several valuable features that we use, among them are the escalation policy, integration of email, telephone, and mobile app.

• Because of the alert mechanism, our support technicians are prompted about support cases at risk.
• The escalation policies make it possible for managers to catch issues before missing SLA targets.
• We are able to better manage the 24/7 offering with a smaller support team.

The assigning and editing of the escalation policies could be improved. It works, but it's just a bit confusing at times.

I've used it for three years.

I didn't have any issues with deployment, but this was handled by a different team. We had just some licensing issues at the start, but that was addressed.

We've never had any issues with stability since we started using it.

The only scalability issue was just the licensing issues mentioned earlier.

N/A. Our support contact is internal, and we have never encountered any issues.

N/A. Our support contact is internal, and we have never encountered any issues.

We used an external monitoring service. We switched to PagerDuty because of:

a) Control

b) Flexibility

c) Cost.

The initial setup was handled by our Ops team. We had no issues.

We implemented it with our in-house team.

We are a cost center, so ROI is measured through savings rather than revenue. However, we measure the ROI through SLA targets and customer service.

Define your escalation policies first before rolling out. It will save time.

Notification is the most valuable feature.

It allows us to provide better customer support.

I would like to see more content in the notification messages; although, that might be a configuration on our end.

We have never had any stability issues.

It has scaled well for our needs.

I've opened one support ticket. They were very responsive; answered within a few hours.

I can't help with this. I wasn't involved in the selection.

I would say look at PagerDuty. Look around, because I didn't. But it is definitely a good option.

We didn't really do any training and it was pretty well accepted. I regret not doing training. They had a booth at a recent conference. I walked up to them to specifically find out a few things and I did find out a few things that I know our team hadn’t been aware of. Do a bit of training.

It has a very limited scope, but it's very good at what it does.

Push notifications to mobile devices combined with the in-app ability to override the system volume allows for flexibility in managing other device notifications, while high-level notifications can be alerted without worrying if your device's notification level is sufficient.

All of our on-call hand-offs are now fully automated with the scheduling system inside PagerDuty. All we need to do is define the rotation and it takes care of everything else.

Some of the UX needs some help for better flow of actions - however I can understand the reasoning behind how some of the UI is laid and how you need to go an extra step to trigger actions.

2 years.

Not that I can remember - it's been two years without any issues.

The most instability we've found was delayed messages - but PagerDuty support is always good with updating Twitter and their support outlets.

Pretty good up there. I've never had to wait over 24 hours to get support.

Technical support has always been up there. From the Twitter updates to their helpdesk - the experience is great throughout.

It was very straightforward. We had integrated the system with Zabbix. In fact, it was more complex on the Zabbix side of things to set it up.

In-house.

Implement PagerDuty. Right now. Go. Are you still here?