Our use cases include generating alerts from our site 24/7. We are managing the cloud infrastructure there.
PagerDuty Operations Cloud
PagerDutyExternal reviews
918 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Thoughtful, thorough, friendly, clear, and concise!
What do you like best about the product?
Jeli gets people excited about learning from incidents. It's thoughtfully designed to maximize the limited time most orgs are willing to spend on post-incident work, and the incident response features match my team's needs. Our rep Chloe is amazing and extremely helpful - providing training, gathering feedback, and all this made our launch very smooth. Jeli is easy to set up and configure on your own, but the support from Chloe and the team were above and beyond. I also really appreciated the data/metrics-driven approach and goals when we launched.
What do you dislike about the product?
Learning from incidents isn't the same as the root cause analysis process that most people are familiar with. Jeli definitely makes the learning approach much simpler, but I think they rely heavily on an internal sponsor to help show the true value. Your org might need to be "ready" for Jeli and the learning from incidents approach, although they make this so easy from the start.
What problems is the product solving and how is that benefiting you?
Getting the most learning and value from incidents (opportunities!) in the limited amount of time we're willing to spend on post-incident work. Additionally, helping us clearly and easily coordinate during incidents.
An incident management platform that does it all..
What do you like best about the product?
Jeli allows me to deeply analyze every incident without spending a lot of time on it. I gain time back, can prioritize other projects without compromising on quality. It allows all stakeholders to get what they need and without being in tech, Jeli, is broadly applicable to my industry.
What do you dislike about the product?
We haven't run into any major downsides so far. The team and the product are very helpful. We're looking forward to what they come out with next.
What problems is the product solving and how is that benefiting you?
Jeli is allowing me to perform a diligent incident management process, keep people aligned in my org. And allows me to resolve my incidents so I can maintain customer trust.
Best tool to resolve experience incidents.
What do you like best about the product?
PagerDuty is an easy to use tool and thanks to its user-friendly interface, we were able to start using it immediately after implementation. We got excellent customer support services from the customer team. It was easy to integrate PagerDuty with other of our products like Servicenow, GitHub, Datadog anf others. PagerDuty helps us identify incidents and respond to them automatically. It offers powerful analytical tools which help us analyze incidents so as to understand their root causes and take actions to prevent similar incidents from happening in future. It is very secure and always keeps all data safe from any cyber security threats.
What do you dislike about the product?
I have no dislikes for PagerDuty. The tool has been outstanding since day one and has met all our expectations. Everything in it works superbly and all features are easy to use.
What problems is the product solving and how is that benefiting you?
PagerDuty is helping us manage incidents more effectively. It allows us to automatically identify and respond to incidents with minimal human dependency. Since we started using PagerDuty, we have been able to ensure that incidents are identified at the early stages as soon as they begin and this gives us ample time to respond to them. This has helped us ensure very simple and effective user experiences to our customers.
Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure
What is our primary use case?
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.
"A pleasure to work with"
What do you like best about the product?
We decided to use the Jeli incident bot to replace our homegrown tools for incident response and engaged in a trial of the full product as part of that -- we were honestly kind of bowled over by how everyone at Jeli was very engaged with us on switching to using the bot and eager to take feedback. We got great advice that really helped us smooth the transition, and almost everyone who has touched the Jeli tools has talked about how much easier things are with them and how they've really helped smooth out communications and data gathering.
What do you dislike about the product?
I honestly can't think of anything right at the moment -- the biggest issue for us is the cost of the full product for an organization of our size right at the moment, especially when it can be hard to articulate the benefit in the short term.
What problems is the product solving and how is that benefiting you?
Our previous incident managment process used a bunch of hacked-together Slack workflows that had a lot of friction when it came to opening incidents, keeping the rest of the organization updated, and taking notes for future use. This led to a lot of stress around incidents, especially for coordinators, and added an implicit level of resistance to even opening incidents. Using Jeli has made this entire process pretty seamless -- incidents are easy to start, it's easy to add updates to incidents (without cluttering Slack channels!) and now that we automatically open separate channels for every incident, it's easy to have one place to collect the communications around an incident. It's also making it easier for people to see the benefit of doing our communication in Slack rather than a voice or video call, where we tended to lose a lot of context before.
Jeli is a great addition to the Incident Learning toolbox
What do you like best about the product?
Jeli is easy to understand for engineers new to incident reviews. It allows for those engineers to quickly come up to speed on how to create an informative and engaging narrative.
What do you dislike about the product?
There is little to dislike. As an early adopter we've seen quick development and rolling out of new features that address pain points.
What problems is the product solving and how is that benefiting you?
Jeli is being used to improve our quality and efficiency around Learning from Incidents. It allows our teams to have a consistent experience across reviews.
Great Product With Useful Functions
What do you like best about the product?
keep our systems running smoothly. It's like having an extra pair of eyes that never sleep, always ready to alert us to issues so we can act quickly and efficiently. The level of organization and control it provides us with is simply unparalleled."
What do you dislike about the product?
PagerDuty's interface can be complex and overwhelming to new users. Plus, it can be expensive for small teams.
What problems is the product solving and how is that benefiting you?
PagerDuty helps us quickly identify and resolve system incidents, ensuring minimum downtime and enhancing customer satisfaction
review of PagerDuty alerting tool
What do you like best about the product?
useful tool for alerting . Quck responded as soon as as alert triggered
What do you dislike about the product?
it does not provide proper reporting and costly
What problems is the product solving and how is that benefiting you?
alerting to enginners once critical alerts popups
Perfect product for oncall
What do you like best about the product?
Well... Pagerduty is almost perfect for oncall in terms of a product. It has all the features for on-call and incident management, alerting and escalations with good reporting. It has great integrations with almost all the monitoring tools as well as with communication tools like Slack and Teams. It provides a rich API which can be used for further customization if anyone is interested.
What do you dislike about the product?
Pricing would be the primary dislike for me. They increased cost for us without even informing. Eventually we had to switch off the service although we liked the product. Billing customer support has been pathetic. We have been working with them for over 8 months now just to close our account and no one there has a clue.
What problems is the product solving and how is that benefiting you?
Setting up on-call schedules is a breeze. The team knows when their schedule is, who is on call for the service and whom to contact for the specific services.
Ability to open incidents and contact respective teams is possible with their great slack integration.
Ability to open incidents and contact respective teams is possible with their great slack integration.
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.
showing 101 - 110