Initially, I started using it for managing on-call schedules. As the tech stack developed, we began using it for service alerts and event routing, and then transitioned to operational views and dashboarding. It eventually became central to our alerting systems, where all monitoring tools would send information to PagerDuty, enabling event management and routing to whoever was on call.
PagerDuty Operations Cloud
PagerDutyExternal reviews
11 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Centralized alert management with customizable routing and superior scheduling
What is our primary use case?
What is most valuable?
The product used to be unique in getting the message to the right person to fix the job. It integrates with multiple applications and is highly customizable, with policies, escalation procedures, and an event routing tool that ensures contacting the right person. A significant advantage is that it includes a metrics overlay, which provides an overview of what is happening in the environment, and its scheduling capabilities are superior to other operations.
What needs improvement?
Everything can always be better. Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in. The ability to build customized modules would be advantageous, allowing organizations to define their own integration modules. It would be useful to have a way to define all configurations in code that is similar to how Terraform operates.
What do I think about the stability of the solution?
The solution has been 100% stable with no issues due to PagerDuty.
What do I think about the scalability of the solution?
The product was highly scalable, with no limits on the number of applications or event routing rules. However, managing a large number of these became cumbersome, suggesting a need for a way to define everything in code.
How are customer service and support?
The customer service was amazingly good. They helped us build our event routing.
How would you rate customer service and support?
Positive
How was the initial setup?
The setup is very straightforward, allowing users to be up and running within minutes. Usually, one knowledgeable person is enough to manage it.
What's my experience with pricing, setup cost, and licensing?
The solution was expensive, but if all its features were utilized, it was considered worth the cost. The tier-based pricing model was cumbersome, and there was a desire for a service-based catalog to better customize purchases.
What other advice do I have?
I'd rate the solution ten out of ten.
Enables us to bifurcate teams and redirect alerts
What is our primary use case?
We use the solution for incident management.
What is most valuable?
PagerDuty helps you bifurcate teams and redirect alerts to specific teams. It has good user management and is easy to plug in. It has good APIs to integrate with our apps and send alerts, making it compatible with most applications. It becomes a powerful infrastructure when handling priority applications, so we use it during the critical phase of our engineering development.
What needs improvement?
It is difficult to send underlying trace files or statuses using PagerDuty. You can set up email alerts, but you cannot build any triggers using those email alerts. There are limitations; you cannot extend it to send alerts to other teams. You can escalate it within the team but not redirect the alert to different teams.
How are customer service and support?
It has a good API for integrating with apps and good documentation. We seldom ask the support team for help. The app can call the on-call person even when the system is offline. It helps you handle alerts quickly, ensuring a fast turnover.
How was the initial setup?
It's straightforward to set up for an organization. It is easy to integrate with our apps.
What other advice do I have?
Overall, I rate the solution a nine out of ten.
Has valuable intrusion management and an easy setup process
What is our primary use case?
We use the product for intrusion management.
What is most valuable?
The product has valuable on-call scheduling, escalation, and incident workflow management features.
What needs improvement?
They could include incident merging and alert grouping features in the product. It would be efficient for businesses or professional clients to manage multiple incidents instead of notifying all the users.
For how long have I used the solution?
We have been using PagerDuty Operations Cloud for a month.
What do I think about the stability of the solution?
I rate the product's stability an eight out of ten.
What do I think about the scalability of the solution?
I rate the product's scalability a nine out of ten.
How was the initial setup?
The initial setup is easy.
Which other solutions did I evaluate?
We evaluated a few products earlier. We switched to PagerDuty Operations Cloud for ease of use and services.
What other advice do I have?
I rate PagerDuty Operations Cloud an eight out of ten. It requires a technical knowledge to understand the features.
A stable solution that saves time and easily integrates with other solutions
What is our primary use case?
The solution is used to alert the on-call users if we have priority-one or business-critical issues.
What is most valuable?
The product easily integrates with other solutions. We can do automation. The product is used for alerting.
What needs improvement?
It’s quite hard to reach the support team.
For how long have I used the solution?
I have been using the solution for more than two years.
What do I think about the stability of the solution?
I haven’t faced any problems with the tool’s stability. I rate the stability an eight out of ten.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
I have used AlertFind and Opsgenie. It is easy to integrate PagerDuty with other applications like Jira, AWS, and Microsoft Teams.
How was the initial setup?
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.
What was our ROI?
The tool saves at least 20% of our time.
What's my experience with pricing, setup cost, and licensing?
The price is very high. I rate the pricing a six out of ten. The license for stakeholders is very limited.
What other advice do I have?
Overall, I rate the product an eight out of ten.
Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure
What is our primary use case?
Our use cases include generating alerts from our site 24/7. We are managing the cloud infrastructure there.
What is most valuable?
We found that the interface of PagerDuty is more friendly. It was easy to use and easy to set up. It integrated easily with our critical server and our Jira project console. It also had better features than Opsgenie. We were impressed with PagerDuty, so we decided to give it a try.
What needs improvement?
We were exploring ManageEngine ServiceDesk. So, we need a feature where we can, like, when an alert triggers, we should alert the recipient by on-call. So, when an alert is detected, a ticket is generated in the management team, and we want to notify them on-call. Like, this ticket has been generated and stuff. So, I would like to see a similar feature in this solution.
This is why we want an alternative to PagerDuty. We want an alternative to PagerDuty. So we are getting on-call notifications using PagerDuty, but now we want to replace PagerDuty with ManageEngine ServiceDesk.
So whenever some incident happens in the cloud infrastructure, we get data alerts from cloud security. We want to integrate a service that will provide us with notifications on-call. That this server is down, or this website is down, or this thing is going wrong.
Another area of improvement is integration. It cannot be integrated with our upgraded Jira system. That's why we are dropping PagerDuty. We won't continue using it due to integration issues.
For how long have I used the solution?
I have been using this solution for a few months. We are in the testing and evaluation phase, so we are comparing some tools online. So, we have purchased the paid version of PagerDuty, but now we want to explore some other products.
What do I think about the stability of the solution?
It's stable. We haven't encountered any issues with PagerDuty.
What do I think about the scalability of the solution?
It's a scalable solution. It worked well for us. We have around ten people using PagerDuty because we have a team of ten, split into two teams.
How was the initial setup?
The initial setup is a simple process. We just want to integrate our ticketing tool with the alerting tool, like PagerDuty, as an alerting tool. From PagerDuty, we would like to generate alerts in some ticketing tools, like Jira or ServiceNow. So we were looking for that solution, so we opted for PagerDuty.
What about the implementation team?
We operate our services 24/7, generating alerts as we monitor our infrastructure around the clock. There are three products involved in this process. The first one is Site Twenty-One, responsible for monitoring our cloud infrastructure. If anything goes wrong in the cloud or on our infrastructure, Site Twenty-Four by Seven generates an alert. This alert is then sent to PagerDuty, which processes the alert and notifies someone from our IT team, cloud team, or application support team.
Simultaneously, it creates a ticket in a ticketing tool like Freshdesk, Jira, or ServiceNow. However, we are migrating from Jira to Freshdesk, and PagerDuty cannot integrate with Freshdesk. So, we want to replace PagerDuty with an alternative.
We have two technical staff and two administrators for the deployment and maintenance of the solution.
What's my experience with pricing, setup cost, and licensing?
We paid for the license. It was a little bit expensive, but it was worth it.
What other advice do I have?
Overall, I would rate the solution a nine out of ten. I would definitely recommend using this solution. It is a user-friendly solution. It has a good interface.
Which deployment model are you using for this solution?
Public Cloud
Till now I am now able to use it
I have subscribe pager duty for more than a week till now I still not able to connect to it. Requested help from support, gave me confusing answer. Even their regional customer success is not contactable.
It helps us track alerts in our cloud environment, but the user interface could be more intuitive
What is our primary use case?
We primarily use this solution to track alerts from our cloud environment and monitor and respond to alerts on our cloud platform.
What is most valuable?
The ease of having it on a mobile phone is valuable. We can always track incidents wherever we are, even away from our computers. Additionally, the escalation feature for incidents to senior engineers or other people is very useful.
What needs improvement?
The user interface could be more intuitive. Initially, when we started using it, we had issues viewing some options because we had information issues in my role as an observer, not the responder. Therefore, I couldn't view buttons like acknowledgements because they were not showing up.
For how long have I used the solution?
We have been using this solution for approximately three years.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is scalable.
How are customer service and support?
Our technical support is not directly from PagerDuty. Instead, it involves us rotating within the teams within the organization.
Which solution did I use previously and why did I switch?
We previously used Dynamic which is similar to PagerDuty but with more Microsoft resources.
How was the initial setup?
The initial setup is straightforward.
What was our ROI?
With the number of features we get, I believe it's a handy tool that is worth the money, so it's a great return on investment.
What other advice do I have?
I rate this solution a seven out of ten. The solution is good, but the user interface could be improved. I advise new users to spend time reading documentation or about the type of features to understand how it works and how to set it up.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Implement complex solution using built-in add-ons.
What do you like best about the product?
The opportunity to consistently implement complex or simple solutions. Additionally, it provides you with the capability to enhance the optimization of yours with your tuning and environment at different levels. Interacts nicely along with other kinds of offerings from the provisioning of VM/Server guides to the remediation play publications.
What do you dislike about the product?
Greater proof and regulations set examples. More bodily JVM/App management tools. Data logging filesystem on GC cycles, other metadata and active heap. More executive review, the power to effortlessly search through a number of tasks for most executions of a certain user or node. To figure out the achievements of an implementation, IE is going to show ninety-nine percent success rather than zero percent success in case the job functions at a hundred nodes but fails one, respectively. Further runs might equate to aggregate percentages.
What problems is the product solving and how is that benefiting you?
For a variety of purposes, Rundeck is really a utility that we utilize across our company. It is an excellent add-on to run scripts without logging onto a server. Moreover, we have a very great VM feed utility for executing PowerShell and combining with PowerCLI. It's employed for applying software, be it bundles, configurations, or perhaps kernel patches.
Recommendations to others considering the product:
Enhance the features compared to Jenkins.
Rundeck Enterprise Review
What do you like best about the product?
Ease of Automation, Super friendly UI and hundreds of Plugins. Easy to deploy,
What do you dislike about the product?
Default authentication mechanism for servers
What problems is the product solving and how is that benefiting you?
Using it as an orchestrating tool to automate daily Business As Usual (BAU) tasks. Run ad-hoc commands on servers. Run cron jobs. Run Infrastructure as Code jobs via Rundeck. Run Python scripts. Run PowerShell scripts for user creation. Run PowerShell scripts for creating A and C records in Active Directory.
great experience
What do you like best about the product?
the ease of its contents and applicability
What do you dislike about the product?
do not have tutorials, update courses
What problems is the product solving and how is that benefiting you?
automation of services
Recommendations to others considering the product:
yes, since its implementation with a little knowledge reduces the work time
showing 1 - 10