We performed a comparison between Everbridge IT Alerting and PagerDuty Operations Cloud based on real PeerSpot user reviews.
Find out in this report how the two IT Alerting and Incident Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The post mortem reports are descriptive, indicating who joined the call and when."
"The system has a lot of great features and they keep adding to it."
"The most important features are the scheduling capability and the integration with ServiceNow."
"Valuable features include having the Calendar built in. That allows for on-call rotation to be set once and left alone. Also, Slack Integration enables us to have all the information from an incident and discussions documented through Slack, without input."
"Even in the first few months, we realized some of those benefits around shortening the time to resolution."
"It's mainly for mass notification and pooling of contacts. Pooling of customers is valuable."
"The email integration, the ability to launch from other programs using email triggers, was the primary reason we got the solution and it's been really helpful"
"It's a lot easier to create and manage schedules, especially in comparison to the on-call scheduling creation in ServiceNow. That has always been something of a bear to operate. We've found it's a lot simpler in Everbridge."
"PagerDuty let us set up rosters based on our shifts. We could assign a hierarchy for how the calls should be escalated and the number of times the call will be transferred between people before it is answered. It makes it easy to access an agent via mobile phone."
"PagerDuty's notification process is the most valuable feature."
"The SMS pages and the mobile application are pretty much the top two features."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"The most valuable features of PagerDuty are customization, access, policies, and different rules regarding the path of escalation. Additionally, it's easy to use and create overrides. For example, if you all are on a call for one week each, but somebody wants to go on PTO, the team needs to swap shifts in PagerDuty. This is easy to do by creating overrides to switch up the set schedules. It's very user-friendly in that aspect. It works well for monitoring and alerting."
"Notification is the most valuable feature."
"With their templates, you can only have a maximum of three phases: new, updated, and resolved. It's not always that easy when we open up a call, that we identify who we need, page out, and we're good. A lot of time it requires multiple page-outs. Being restricted to those three phases, there's no way to say, "I want this variable to be persistent, and this one to not be." ...I would like to see a bit more flexibility and tighter control over the templates and the variables you can create."
"A key area for improvement - and I think they are working towards these things - is analytics. If I want to do sophisticated reporting and analysis of the data that's being captured in IT Alerting, at the moment, the reporting interface is immature."
"I swapped two people's weeks, and at least from what I saw, I had to do each day individually. It would be nice if I could swap two people's weeks without having to do it each day."
"You have to create schedules in Everbridge. It would be better if it could tie into an existing solution, such as Microsoft Exchange or Google Calendar, so that you don't have to create it in both places. That's one thing it lacks right now. You can't just say, "Hey, look at this Microsoft calendar. That's what we want to use." You have to create it in Everbridge."
"I would like to have a little bit more flexibility in the member portal."
"It could use more enhancement type integrations, but no improvements to functionality are needed."
"Explanations are limited to 500 characters in description fields."
"The company would like to have super detailed analytics, as we integrate this with our security software."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"There is room for improvement with the time schedule. The way the schedule currently works is you assign all the team members in one schedule and it automatically spreads them around throughout the schedule... It would be better to be able to edit the schedule and place my team members where I want, or at least to have that option in addition to the automatic process."
"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."
"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."
"Because of the way you have to structure the rosters, if an engineer has to go on leave (or something), you can't just go in and reassign/take this person out of all of the different rosters that they're in. You have to go into each of the rosters and take them out. There might be a roster for business hours, after hours rotation, and monitoring deployments. Each time we need to take an engineer out of the pool, e.g., if they're sick or on leave, then we have to go and touch all of those rosters, updating and replacing them. Whereas, if we could just take the person out and have it automatically fill in the rostering, then that would make life a lot easier for managing it."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"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."
Everbridge IT Alerting is ranked 9th in IT Alerting and Incident Management with 22 reviews while PagerDuty Operations Cloud is ranked 1st in IT Alerting and Incident Management with 35 reviews. Everbridge IT Alerting is rated 8.8, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of Everbridge IT Alerting writes "We have seen substantial savings with its usage as it drives down our MTTR". On the other hand, the top reviewer of PagerDuty Operations Cloud writes "Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure". Everbridge IT Alerting is most compared with ServiceNow, OnSolve Platform for Critical Event Management, Opsgenie, xMatters and Splunk On-Call, whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and xMatters . See our Everbridge IT Alerting vs. PagerDuty Operations Cloud report.
See our list of best IT Alerting and Incident Management vendors.
We monitor all IT Alerting and Incident Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.