G2

Manish L.

Manager

Small-Business (50 or fewer emp.)

11/4/2026

"Clear, Unified Observability with Powerful Distributed Tracing"

5/5

What do you like best about New Relic?

It provides a clear, overall picture of what’s happening inside our applications. From a single place, we can monitor API response times, database queries, errors, server resources, and overall application performance. The distributed tracing feature is especially helpful when working across multiple services, since it makes it easier to pinpoint where requests are getting delayed. The dashboards are also quite flexible, and once everything is configured, it becomes much simpler to stay on top of production issues. Review collected by and hosted on G2.com.

What do you dislike about New Relic?

The initial setup and configuration can take a while, especially if you’re monitoring multiple services across different environments. Because there are so many features and options, the interface can feel overwhelming for someone who’s new to observability tools, and it takes time to learn where everything is. Pricing is another concern, since data ingestion can grow quickly as application logs and traces get larger. At times there can also be too many alerts, so you end up spending extra time tuning thresholds to cut down on unnecessary notifications. Review collected by and hosted on G2.com.

What problems is New Relic solving and how is that benefiting you?

New Relic helps us spot application performance issues and production errors before they turn into bigger problems. Previously, debugging something across multiple backend services meant manually checking different logs and servers. With New Relic, we can trace a request end to end, pinpoint slow database queries, review error rates, and quickly see which service is responsible. This cuts down debugging time and makes it easier for developers to investigate production issues without having to rely on multiple teams. Review collected by and hosted on G2.com.