We performed a comparison between New Relic and PagerDuty Operations Cloud based on real PeerSpot user reviews.
Find out in this report how the two AIOps solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We appreciate the way that this solution allows us to monitor the ongoing status of the UI at any given time."
"You don't have to go through a list of 500 servers."
"It allows the restriction of privileges and control of users."
"The stability of New Relic APM is very good."
"The alert mechanism is quite accurate when something goes wrong in your system. For example, if you have hundreds of APIs on your server, and any of the APIs is not performing well, you get an alert. When there is a drop or change in the threshold value, the beauty of New Relic is that within a fraction of seconds, all the stakeholders who are configured in the New Relic system will get an alert. That's one good thing."
"It is a software solution as a service, so I don't have to manage it on-premise."
"New Relic's dashboard is nice, and it's reliable. It's also compatible with many services, especially Java and the Python ecosystem."
"One valuable feature is that the synthetic alert stays open until the issue is resolved. You can actually monitor whether your system is back up."
"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."
"It reduces the amount of white noise. If something comes through, then it will alert somebody. However, if it's a bit of white noise that comes through at night, then it gets dealt with the next day. Everything is visible to everybody. It's not just a single person getting an SMS, then going, "Oh, I'm not going to worry about that." The visibility to everybody on the team is one of the great things about it because it reduces the white noise."
"It has scaled well for us."
"PagerDuty is very stable and very reliable."
"The initial setup is a simple process."
"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."
"The initial setup is straightforward."
"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."
"There were some settings we had issues with."
"I would like to have storage monitoring. E.g., being able to monitor SANS, specifically protocols, like NFS and CIFS metrics."
"It is complicated, especially in how you interpret the data that it provides. If it had a bit more canned, out-of-the-box features, especially some of the reporting features, that would be more useful."
"They need to improve the alerting and dashboarding as these are the key features in DevOps."
"The product has good documentation for Linux, however, their documentation for Windows is lacking substantially. It's something they need to develop."
"The solution only supports the cloud platform and not on-premises."
"One thing I'd like to see in any APM, especially New Relic, is the ability to use distributed transactions. When one microservice calls another, it calls another database and microservice. The entire data visualization layer will not be able to correlate from one microservice from end to end and return on that path. Distributed transactions would be a great addition that would make life simpler. Unfortunately, no APM has that end-to-end capability."
"The APIs could be better. I would also like more APIs and features to integrate with streaming solutions, like Kinesis or Kafka."
"It’s quite hard to reach the support team."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"The user interface could be more intuitive."
"Something that needs to be improved, is adding multilingual support."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"PagerDuty can improve the integration with Terraform."
"They could include incident merging and alert grouping features in the product."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
New Relic is ranked 3rd in AIOps with 152 reviews while PagerDuty Operations Cloud is ranked 8th in AIOps with 35 reviews. New Relic is rated 8.6, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of New Relic writes "Has a simple user interface and end-to-end monitoring and self-healing features". 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". New Relic is most compared with Dynatrace, Datadog, Elastic Observability, Grafana and Prometheus, whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Everbridge IT Alerting and Splunk On-Call. See our New Relic vs. PagerDuty Operations Cloud report.
See our list of best AIOps vendors.
We monitor all AIOps 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.