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."It is stable and scalable."
"The most important thing is that it tells us where the latency in throughput and response time are."
"We have done the New Relic integration with Serverless AWS, which has helped us with monitoring, and keeping our monitoring from our on-premise part with the cloud part."
"The most valuable feature is the New Relic APM module to deep-dive into the application, to get bottlenecks to the surface, and to improve application performance. Also, the New Relic Insights module creates a real-time dashboard on application performance to create awareness for the DevOps team."
"It does everything we wanted it to do."
"It gives insights to non-technical people about what technical issues are most important, how much it impacts customers, and potentially, where we should be targeting our development teams when they have time."
"The solution is quite stable."
"The solution is good for sending alerts, drawing graphs about system usage, and creating plug-ins."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"It has scaled well for us."
"PagerDuty is very stable and very reliable."
"The SMS pages and the mobile application are pretty much the top two features."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"Notification is the most valuable feature."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"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 UX/UI design of New Relic APM could be improved. The solution currently has some slow pages in terms of loading and viewing the pages, for example, the reports. The reports and other pages take a long time to load."
"The solution is quite expensive."
"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."
"I would like a feature where I can turn off alerting at a policy level. Thus, when a policy is inactive, I can shut down all of my alerts within the policy."
"Documentation is one of the biggest things that I have a problem with since its documentation is not clear sometimes."
"It is very difficult to award the service level cycles at an endpoint level."
"The APIs could be better. I would also like more APIs and features to integrate with streaming solutions, like Kinesis or Kafka."
"The price needs improvement."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"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."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"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."
"It cannot be integrated with our upgraded Jira system."
"PagerDuty should be integrated with other tools, so it can import the IT roster automatically. Our other rules continue to work once they're configured, but the roster must be added manually."
"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."
"PagerDuty can improve the integration with Terraform."
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, Splunk On-Call and Everbridge IT Alerting. 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.
