PagerDuty Operations Cloud Reviews

The two major use cases were alerts for events and scheduling of engineers to get pages based on incidents.

Alert deduplication and noise reduction for alerts are the major features that I found useful.

It is a very non-customizable product, so you cannot add things like root cause analysis or the classification of incidents based on the area where you are getting more incidents. For example, if you're getting a lot of database issues, that may be an are you want to probe.

There aren't any capabilities to integrate with any problem management issues, like repetitive or high impact issues to deep dive and track them in the PagerDuty system. That is, I would like to see integration of problem management with incident management. That would be one nice feature to have.

It is a stable product.

It's scalable. We had 120 users.

We used Evanios and switched to PagerDuty because deduplication of the alerts was not occurring in Evanios.

The initial setup was not very difficult. It took us about four months to set it up because we were trying to make PagerDuty fit to the best possible use cases that we had. We also had quite a number of alerts to move.

I'd rate the initial setup process at three out of five.

Set your objectives and have a plan regarding your goals, timelines, and what you want to achieve. Figure these out in terms of the implementation of the tool and whether your objectives will be met by the tool.

Overall, I give PagerDuty a rating of eight on a scale from one to ten. 

I use PagerDuty for incidents, event orchestration, alerts, and creating services.

The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances.

PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration.

I have been using PagerDuty for approximately six months.

PagerDuty is stable.

We have 20 people that are using PagerDuty.

I have contacted the support from PagerDuty and they were very good.

I rate the support of PagerDuty a five out of five.

Positive

The initial setup of PagerDuty is easy. It only takes one day to set up.

There is a license needed to use PagerDuty.

My advice to others is for them to use API reserves and API rest to test the payloads before putting them in production. To understand better the PagerDuty communication. For example, they can use Postman to create APIs and then create a payload. It's a useful tool to test with PagerDuty.

I would recommend this solution to others.

I rate PagerDuty a nine out of ten.

Whenever we have a server that goes down, we get notified immediately which helps out our clients and all the developers, so we know when we have to log on to bring it back up.

We never found out about the problems with the server unless we had the developers that would call us up saying, "Server's down. Bring it back up." Now we get the phone calls. If we don't answer a text message or an email right away, they'll even call our house phone, the computer will, and tell us the server is down and what server it is. It's helped out a great deal because then we can bring it up right away and then figure out what the problem is after we bring it up.

It handles everything that we do now so if I can avoid the 2 AM phone calls that would be perfect but I know that's not possible. Other than that, nothing else.

It's very stable. We don't have any issues with it.

It is meeting our needs because we have followed between 1,500 - 2,000 servers, so it does meet our needs that we can actually maintain them and make sure everything is up and running.

We've never had a problem with the technical support. We have one person in our office who mainly does a lot of the setting up of it and anytime she has a problem, she can call them and they handle the problem.

We were mainly relying on the clients and stuff telling us when something went down or if we happened to catch it. There really wasn't a solid tool that we were using before.

It wasn't that difficult to set everything up. It's pretty straightforward. You put in the servers, the names, who are the people we're contacting.

We have to look at other vendors. Yes, we did look at other vendors. I don't know which ones they were but they did stay with PagerDuty.

I'd probably give it a 9/10. You just have to be prepared for the early morning calls, but it does give you three ways to be notified. You don't have to worry about being missed. It will take one and go to the next and go to the next and the last one, of course, is it will call up not only your cell phone but your home phone. Good and bad but it does handle what you need it to do.

Most important criteria when selecting a vendor: does it handle all the needs? If it handles everything that we need it, the price is something but it's more that it actually does the job that we need it to do.

I tie alerts from our GCP tenants to PagerDuty.

PagerDuty's best features are the dedicated application that allows me to reach my engineers immediately and the ability to directly assign specific tasks to individuals and have them report back.

PagerDuty's webhooks need some improvement. In the next release, PagerDuty should include the ability to get raw data about usage and put it on a dashboard.

I've been using PagerDuty for five or six years.

PagerDuty is stable for the most part.

The initial setup can be difficult for those without experience in onboarding.

PagerDuty has monthly and yearly licenses available, the costs of which can get quite high if you have a large number of users. There is also a free version available for a limited number of users.

I would advise trialing the free version before committing to paying for a license. I'd rate PagerDuty seven out of ten.

We use this solution to alert us to system errors.

The immediacy of the alerts allows us to provide a good user experience to our customers.

 The alerts are immediate in this solution, which allows us to respond to errors quickly.

We are also able to set the escalations level in this solution, which is useful.

This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations.

We have been using this solution for almost three years.

We have found this solution to be very stable.

This is a very scalable solution in our experience.

The initial set up of this solution is very straightforward. The product operates from a list of provided emails that are then included in error alerts. 

All of the configuration, including setting the level of escalations is done from the UI, and deployment only takes 10 to 15 minutes.

We would recommend that any organization looking to use this solution ensures that they have a good logging system in place. This will allow alerts to be set up and trigger properly.

I would rate this solution an eight out of ten.

The solution is used to alert the on-call users if we have priority-one or business-critical issues.

The product easily integrates with other solutions. We can do automation. The product is used for alerting.

It’s quite hard to reach the support team.

I have been using the solution for more than two years.

I haven’t faced any problems with the tool’s stability. I rate the stability an eight out of ten.

Around 20 people, including users and stakeholders, use the product in our organization. I rate the scalability an eight out of ten. The scalability is good.

I have used AlertFind and Opsgenie. It is easy to integrate PagerDuty with other applications like Jira, AWS, and Microsoft Teams.

I rate the ease of setup an eight out of ten. The product is deployed on the cloud. It took us a few hours to deploy the tool.

The tool saves at least 20% of our time.

The price is very high. I rate the pricing a six out of ten. The license for stakeholders is very limited.

Overall, I rate the product an eight out of ten.

Our primary use case of this solution is for alarming and to mitigate threats in our organization.

The feature I like the most is the alarming.

Something that needs to be improved is adding multilingual support.

PagerDuty is very stable and very reliable.

As far as we've used it with clients, it has been very scalable and we don't have time limits yet. We currently have 20 users, who are IT technicians, operators, and managers. We do have plans to increase our usage in the future, but right now we're mainly using the alarming functionality of the solution.

We haven't used the technical support yet.

The initial setup was straightforward and it took us a few months for deployment. We did everything ourselves and now we have one person responsible for deployment and maintenance. 

Licensing costs are around $700 a month and the only additional costs are phone costs in some instances.

We looked at some other options, including on-site servers, but decided to go with PagerDuty.

I would advise others to make sure it's a good fit for their organization and that you have your internal organization sketched out before you install the product. I rate this a solid nine out of ten.

In the next version I would like to see multilingual support.

We email in, and Pager Duty finds the person on-call, alerts and escalates.

Faster reaction times to respond to a set alert that we have designed to be classed as a Wake Up call.

They need to sort out the date / time function when the time zones switch over from Normal to Daylight savings, and vise versa.

NOT all countries swap at the same time, thus everything is off by 1 hour until everyone is back in the correct zone.

I did make them aware of this, but they simply did not understand, and after a week everything auto corrected when everyone was back in the correct zone.

5 years.

We very rarely encounter issues where an SMS is about to be received before the application push notification (connection to the internet did not fail on devices.)

Not currently.

8/10

Back in the day, it was very simple. Other added in functions started to make it odd, but overall for what we use it for is it still straightforward.

I set it up and the systems simply emails the alert in, and it does its magic as per the rota.

I suspect it has paid for itself.

Keep it simple. For the pooled users and what is allowed, we have yet to go over the allocated pool for the month.

For a corporate tool – it acts as a 3rd party for a simple wake up tool. Absolutely recommend it. Escalation policies can be set up so that the alert should get someone’s attention, and all from a simple email being sent out. I like it.