New Relic is a SaaS-based web and mobile application performance management provider for the cloud and the datacenter. They provide code-level diagnostics for dedicated infrastructures, the cloud, or hybrid environments and real time monitoring.
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
PagerDuty
Score 8.6 out of 10
N/A
PagerDuty is an IT alert and incident management application from the company of the same name in San Francisco.
$25
per month per user
Pricing
New Relic
PagerDuty
Editions & Modules
Free (Forever)
$0
No credit card required; 100 GB free ingest per month, 1 free full user + unlimited basic users, 8 days retention, 100 Synthetics Checks
Telemetry Data Platform
$0.25
per month per extra GB data ingest (after first free 100GB per month)
Incident Intelligence
$0.50
per month per event (after first 1000 free events per month)
Standard
$99
per month per full user (after first free full user - unlimited free basic users)
Along with New Relic, our engineering and SRE teams also use PagerDuty for setting up alerts, Datadog for APM and AWS CloudWatch for infrastructure level monitoring on AWS.
AWS CloudWatch is available as a service if you use AWS. We use Datadog for things similar to New Relic. A …
There's nothing like New Relic. pingdom has an APM module but it lacks the detail of New Relic. Datadog's strength is measuring the hosting infrastructure rather than the app itself. Sometime you need APM to see what your app is doing.
New Relic is more affordable for infrastructure monitoring and had a more mature app monitoring suite (but data dog is catching up). Data dog has better predictive analytics and DB monitoring.
PagerDuty seemed to have a much more flexible setup that allowed the organization to build and manage how we respond to alerts and incidents. The ServiceNow product seemed to be a bit more rigid.
When compared to VictorOps and OpsGenie, PagerDuty is clearly the best of the breed. It provides a more polished UI, more integrations, and more features than the others, but it's priced at a premium. Smaller teams will probably get more value out of another alternative that …
We also use CloudWatch for certain apps, but since it's locked in to AWS and its UI is much inferior to PagerDuty's, we prefer to have everything go to PagerDuty. It's really the only solution worth considering that I've come across for monitoring and alerting for production …
I did an evaluation of OpsGenie and found PagerDuty to be more intuitive and at the time PagerDuty had more integrations. I also really believe in PagerDuty's ability to keep an extremely high uptime for their application. Over the last 5 years very few issues and 0 lengthy …
CloudWatch and New Relic are not exactly comparable, but it is possible to use them to create some alert. PagerDuty has more features, including on-call schedules and escalation policies.
I have used New Relic in different scenarios like monitoring my production infrastructure and applications which helps us to reduce the downtime of my applications and websites and also I have used the synthetic monitoring feature which helps to proactively monitor our websites availability. Along with this I have also used New Relic for cloud resources cost monitoring which helps to reduce my cloud cost. Also I have used mobile application monitoring which helps me to trace the sessions easily and I can easily reduce my RCA through the help of that.
I think PagerDuty works great for medical practices. I have used other platforms through other companies, and PagerDuty is by far the best platform. It is because of the different features it has to communicate to other staff members how the call is being handled. It is easy to learn how to use.
New Relic APM allows us to follow up transactions across services and trace performance bottlenecks in real-time, crucial when monitoring the processing of energy loads or predictive maintenance algorithms.
It gives us deep visibility into our cloud servers, containers and IOT gateways, so we can catch CPU spikes or memory leaks which can impact the data we ingest from the field devices.
We develop custom dashboards for monitoring trends of power consumption, abnormality in sensors and API health. In conjunction with alerting, it makes sure we are fixing issues before customers even see them.
When getting a phone call, PagerDuty doesn't seem to allow acknowledgments of alerts through the phone, which it says it does. I constantly receive a message that it was updated by another person - when in reality, it wasn't.
Smarter notifications. If an alert was snoozed for a time, when it comes back, it sends out another alert. It should, I think, send a message asking if the alert is still an issue and give the option to close.
The only issue that we have had with New Relic is that the price might be a little expensive for smaller companies. The amount of data you store in New Relic impacts the cost, and can get away from you if you don't work closely with the vendor. Overall though the application is top notch.
I have given this much rating as I am used New Relic in different sectors and for different use cases like its K8s monitoring, infra monitoring, full stack monitoring as compare to other tools New Relic gives data in a formatted and connected way, and also it is giving us value for money. It also launches new features day by day which helps users to track the issue very quickly. It also supports OTel integrations which is the latest trend of observability tools. thats why I had given this much rating to New Relic.
The UI is more complex than I would like. Part of the challenge is that most users use PagerDuty infrequently; I don't remember how I changed a policy last time. Another part of the challenge is that some users expect alerting to be a trivial feature, and are reluctant to invest any time in reading the documentation.
The support team has been really helpful and resolved most of the issues on time. However, for a couple of issues, several follow-ups were needed to elicit a reasonable response. The issue was deeply technical and could have been investigated only by their Architects, and bringing them into the ticket took longer than needed
PagerDuty is reliable and easy to set up. It gives an effective way to notify the team about critical incidents which results in a faster turnaround time on issues. users can customize their alerts rules based on their preferences. Overall it's effective and easy to use which adds great business value.
It's better to start by implementing New Relic in one project and test everything. Try to follow best recommended practices and read all the official documentation. Everything seems well tested. Then, start by installing agents to the rest of your projects and keep a close look to all logs and metrics New Relic gives you.
New Relic has full stack visibility and gives us all options for observability like one stop shop. It gives you front end, backend as well synthetic monitoring capabilities. Every other feature built into one cost model (usually) which ties to data that you send, it helps you leverage all features without having to pay additional charge for feature
I have not use the 2 technologies for as long as I have used PagerDuty but in my opinion PagerDuty makes things a lot easier. The other tools got the job done and got alerts out but PagerDuty just seemed to make the setup for on-call alert schedules and integrations easier than the others. This isn't to say the others are difficult, just that PagerDuty was slightly better. I also have noticed that more tools have options to integrate to PagerDuty over the other tools.
![Screenshot of Similar Incidents [Apple iPad], Open Incidents [iPhone 8], On-Call Schedule Menu [Apple Watch])](https://media.trustradius.com/product-screenshots/kf/M5/L6SIK3HGD31M.png)
