PagerDuty Operations Cloud Reviews

The primary use case of the solution is to alert the on-call person when there are any critical errors or when the servers are down. It is also used for the on-call scheduling of personnel.

The most valuable feature is the phone app that allows us to send notifications without additional fees when sending by SMS or phone calls. There is also an escalation metric that allows any alert that goes unanswered to automatically move on to the next person on the list.

The product can be improved by including out-of-the-box integration with other standard tools used in our fields such as Confluence and Jira.

I have been using the solution for five years.

The solution is stable and we haven't had any missed alerts in the five years of use.

The initial setup is straightforward.

The implementation was completed in-house.

The cost is based on the package you select.

I rate this solution seven out of ten.

I recommend anyone looking for an alert solution to try out other similar products such as Opsgenie. Opsgenie is more user-friendly out of the box and is available at a lower cost.

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 the solution as for log aggregation, scheduling, and filtering out false positives. 

The solution's most valuable features are that it adds each alert as a service, has good scheduling capabilities, and includes the ability to write logic based on texts. 

The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue. 

More adaptive machine-learning logic would help to correlate incidents. 

I have been using the solution for four years. 

The solution is stable with no issues. 

The solution is scalable. 

We currently have 300 users in our company and plan to increase usage. 

Technical support has been good.

I rate support an eight out of ten. 

Positive

I previously used OpStream without the tariffs. 

The setup is straightforward and there is no real deployment because the solution is ready to operate immediately. 

We only need to manage integration to the solution. 

I implemented the solution in-house. 

Our company has already achieved ROI because different tools can alert to a single system and that is very efficient. 

The solution removes the need for multiple systems and handling alerts at each phase. 

The solution is paid on a monthly basis and represents about 1% of the platform's budget. 

If you are considering the solution, it is important to have a clear idea of the services you want it to report, a defined service schedule with registration policies, and a filtering plan in place to decrease false positives. 

I rate the solution a seven out of 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.

We use PagerDuty for incident managment. We're looking at integrating PagerDuty with Rundeck in the future.

PagerDuty has allowed us to identify issues and incidents within the infrastructure that we wouldn't have noticed otherwise.

PagerDuty's notification process is the most valuable feature.

I would like the UI to be more intuitive. I would like to be able to group or color-code the discoveries. When you create a system, you have a listing of all the different configurations. You can list them by teams, but some additional color coding would be helpful. I would break it down by incident controls. In other words, it should be broken down it into response teams and engineering divisions.

We have been using PagerDuty for about five years.

I rate PagerDuty support 10 out of 10. 

PagerDuty was deployed before I joined the company. Finding the information about what I wanted to do was complex, but it was straightforward once I found what I needed. Overall, it has been a fairly easy solution to use and maintain. 

We have seen a return.

I think the license costs around $30 per person.

I rate PagerDuty nine out of 10. 

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.

I interact with customers and then see the use cases and how they would use the PagerDuty tool and the integrations that come with it. I basically see how the customers will use the product. I then have conversations with the higher members or the stakeholders in the company on what ROIs they would get from this tool and the measurements of metrics, etc.

The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable. 

It's an incident management tool. So, its main functionality is to integrate with monitoring tools. There is a flexible and easy way of integrating with monitoring tools. That's what I have observed in most of the scenarios. It allows us to configure the integration with APIs and plugins as well.

The On-Call Teams feature could be better in terms of levels of conditions related to which team or member should get the responsibility of handling a matter or incident.

PagerDuty can introduce machine-learning concepts for detecting incidents earlier. They haven't implemented that, but that might be on the roadmap.

It has been one year.

It is stable. It is rapidly growing, and all the features are being built in a stable way for the users to work with. I don't see any difficulties in handling any of the functionalities in PagerDuty.

It is scalable. It is used by enterprise customers. Only good planning is required in the initial stages for us to implement it fully.

So far, we have not reached out to their support team. We were able to support the customers with the solution that they needed when they reached out to us.

Most companies these days are partner-led companies. The first hand that goes into support is from a partner. Partners like us support the customers in any P3 or P4 issues. We also help with the P1 issues if they're finding it difficult to manage the application, and in turn, if the partners need support from the PagerDuty support team itself, they get support within one or two hours. So, it is easier for customers to go through a partner.

It depends on the complexity of the environment a customer has. If a customer only wants to track one application, then it's just a straightforward integration. If a customer wants to set up the tool at an enterprise level, there should be a real plan that requires having discussions with all the teams. We need to build a plan and then methodically integrate all the tools one by one. It's not always complex, but better planning helps in configuring these tools properly. In most of the scenarios, it provides us the integrations that are readily built, and we have successfully configured it in most of the customer environments. Overall, I would rate its setup a 4 out of 5.

It's not only the budget that goes into the product. We see all the other factors as well, such as the services that they buy and investments they make in the resources for configuring, working, training, etc. It could help an organization not only financially but also performance-wise in the long term.

I would rate it a 10 out of 10.

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.