Well done New Relic!
Updated January 17, 2022
Well done New Relic!
Score 7 out of 10
Overall Satisfaction with New Relic
We mainly use Infrastructure Alerts, Synthetic Checks, and Logging in our department for our web services and websites. Other departments may use other tools, it is independent. I[New Relic] is used to catch infrastructure issues and production errors early. Also, [New Relic,] helps us understand how our services are used externally, and how they perform.
- Nice overview of Infrastructure and ability to see it from different angles.
- Logging system and search in the logs.
- Ability to use TraceIds that helps investigating where the issue comes from.
- Powerful Alerts system.
- Nice configurable widgets that provide good at-a-glance overview
- Search in Logs can be slow, sometimes [the] browser even gets stuck when you type a search query.
- When a policy is violated, it takes time to find the respective logs from the violation view.
- We are using it for a short time to evaluate ROI yet, but we can see that we found already many bugs thanks to [the] alert system and logging.
We have instant error and infrastructure issue detection with alerts, and we also can easily dive deep into a problem using logging, which provides us with capability to fix errors early.
We [have] not migrate[d] while using NewRelic yet, but rather added it to the running system.
We do watch how our systems perform, and it can already [give] us a couple of insights about the bottlenecks in our system.
Do you think New Relic delivers good value for the price?
Are you happy with New Relic's feature set?
Did New Relic live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of New Relic go as expected?
Would you buy New Relic again?
New Relic is well suited for complex applications with microservice architecture, this is where the Trace ID feature, dependency overview and APM can pay off. It might be less appropriate for simple or monolith applications. Client-side browser error logging is somewhat hard to integrate without much overhead on the client side.
Using New Relic
3 - Basic DevOps skills and good understanding of internal System Architecture
- Infrastructure Overview and Monitoring
- Error Logging
- Microservices Dependency Overview
- Dependency between microservices
- Database performance measurement
- Web Services performance
Evaluating New Relic and Competitors
Sentry lacks some features like infrastructure monitoring, APM and distributed tracing.
Kibana is more complex to set up, UI is pretty slow.
New Relic Implementation
Implementation details were handed over from another person, but as far as I can tell there were some moments where we needed support cause it was not very easy or straightforward.
New Relic Training
New Relic Support
No escalation required
Immediate help available
Support understands my problem
Support cares about my success
Quick Initial Response
Using New Relic
- The initial setup is quite complex.
- Some views are not so intuitive to use and one needs time to understand how to use them efficiently.
- Every page provides a lot of data, but sometimes it's not so easy to understand what exactly it represents.
- Navigation is also often not intuitive.
- Acknowledgement of log errors is very hard to do instantly - one needs to do a separate setup to filter out unwanted error logs, not possible directly from the Log window.
- A lot of data that helps to learn and improve your system better
- UI is quite responsive compared to competitors given the amount of data
Like to use
Requires technical support
Slow to learn
Feel nervous using
Lots to learn