New Relic Solutions [Private Offer Only]

We use Java microservices, so we capture the events with the help of New Relic . Based on that, we add the alerting part inside New Relic .

We have enabled the New Relic Java agent inside our microservices, which observes the metrics from the microservice. We have created the dashboard inside New Relic, which captures the metrics and plots the weekly data inside New Relic. We can also add a timeframe in New Relic to observe the past trends and current analysis.

This is our main use case. We can observe the response time, Apdex score, error percentage, database queries, and web transactions inside New Relic.

New Relic has a great impact on our organization because without logging into the database and any other tool, you can directly capture the long-running queries and which APIs are taking a lot of time. You can filter them inside New Relic. You can also create custom dashboards inside New Relic, and based on your use case, you can create that particular dashboard. You can also set alerting based on the past trends of those metrics.

All of these metrics improve because we can say without any major outage, if we get the Apdex score alert or either response time or whatever alert we have set up inside New Relic, we timely get the alert. We can also proactively get the alert and proactively fix those things. Instead of getting a production down, you can analyze those things based on New Relic trends. You can fix and respond proactively without any minimal damage.

In my experience, New Relic is one of the best APM  tools. You can monitor your API's response. You can filter the APIs based on the response it is taking, and you can monitor the response times based on the multiple APMs related to respective environments. You can observe the Apdex score inside New Relic. In one single window, you can look for the multiple metrics, which is really useful for production.

You can also monitor heap parameters and memory of the JVM inside New Relic. You can also integrate it with your incident management tool so that based on the alert you have set up inside New Relic, you can get the alert over your incident management tool.

Sometimes the UI feels like it is not that much user-friendly for any new user who is using New Relic. The user interface could be more user-friendly for someone who is new to New Relic.

For alerting and dashboards, I still think there is some tuning and a user-friendly experience required because while creating, it is something complex.

There are some changes required from the UI side. If someone is new, the UI is not that overwhelming from the new user experience perspective.

I have been using New Relic for the last five years.

In my experience, New Relic is very much stable.

New Relic is very much scalable for our organization.

We have excellent customer support with New Relic.

From the start we are using New Relic and did not previously use a different solution.

I think there is nothing to improve in New Relic. It is having the best features. As we talk about setup, you can set it up very easily. It captures from the observability side, if we talk about it, metrics, logs, and you can visualize a dashboard based on those metrics. You can also integrate it with your incident management tool. So I think there is nothing required for the improvement as of now.

I have seen a return on investment because if you timely monitor the things and fix those things, and there is no such production outage, your production is running smoothly and there is no outage, that means you are saving. You are definitely getting ROI on whatever you are investing because if your production is down, then there is a loss of revenue from the customer side. It is a great tool to get ROI.

As we talk about pricing, it is not that much cheaper. It totally depends on your ingestion, how much ingestion it is taking. So, it is totally dependent on that.

We have tried Signoz and OTel, but they will not work for us because these are open-source, and you need to perform lots of tuning. Of course, New Relic is not open-source, and there are lots of features in New Relic. That is why we go for New Relic.

If someone is trying to monitor their applications which are built with Java, you should definitely go for New Relic because there are lots of features inside New Relic. You can integrate New Relic with cloud providers, and you can also integrate your incident management tools. If you are observing and capturing something, you can also set up alerting, and you can directly integrate it with your incident management tool. There are lots of integrations in New Relic, so you do not need to worry about it. Based on a single screen, you can capture multiple metrics including response time, Apdex, throughput, and you can track your APIs which are slow over time. You can also monitor your CPU, memory utilization, and apart from it, you can also visualize your logs and errors inside your microservices. You can also monitor database queries which are taking a lot of time. There are lots of things inside New Relic. I have given this review a rating of 9 out of 10.

I used New Relic  for instrumenting logs and designing different dashboards for a telecommunication company. During iPhone launches, I monitored all orders, how many orders were sold, what iPhone models had been sold, and the quantities. I used New Relic  to keep the status of all of this information, and I also used New Relic for synthetic monitoring.

New Relic provides a really good dashboard and view, allowing me to filter by different options and different New Relic models. Everything shows how one system connects to another, how orders go to logistics, and delivery on the same screen, which really stood out to me. For synthetic monitoring, I used different APIs, both scripted and browser-based, and monitored them. Whenever any API goes down, I get notified instantly, which is a great feature.

I use New Relic for webhooks, setting up notifications using webhooks and getting notified in the Teams channel directly.

Synthetic monitoring and reactive monitoring are the best features that I found in New Relic. Using a simple Node.js script, I can monitor different APIs in production every one minute, two minutes, or five minutes. I don't have to monitor reactively but proactively, and the agent makes a call to my API every five minutes, allowing me to know when my API is down and helping with production downtime.

Proactive monitoring definitely impacts my team's workflow and production reliability. There was an instance when we had a very critical API that I monitored using proactive monitoring and synthetic monitoring, and it went down for a few minutes. I got notified in my Outlook, so I notified the dedicated team for that, and they fixed the issue even before the customer noticed, saving us a lot.

New Relic has positively impacted my organization by helping with our observability goals. We had 20-25 goals to have observability in place, and New Relic was a great tool to achieve that goal through creating dashboards, setting up synthetic monitoring, and different kinds of alerts. New Relic helped us achieve those observability goals by significantly saving downtime. Whenever an API is down, we get notified instantly and take actions, which saves us from downtime, and alerts definitely help us to take action quicker, even before the real customer notices any issues.

New Relic can be improved in a few areas. I noticed that some things can be easily done through Splunk but not through New Relic. For example, creating dashboards in Splunk allows you to instrument different kinds of data and API logs and scrape the data to create a dashboard. For New Relic, you have to use different accounts, so when tracing any API call, you have to move from one system to another, which are all in different accounts. You would need different account access to see end-to-end tracing, whereas in Splunk, you can see everything in one place.

I used New Relic in my previous job for about a year.

New Relic is stable.

New Relic's scalability is good.

The customer support for New Relic is good. I would rate the customer support on a scale of one to ten as a nine.

Positive

We previously used Splunk and needed to explore New Relic for synthetic monitoring, so we moved to New Relic.

We did not purchase New Relic through the AWS Marketplace .

I have seen a return on investment, specifically in terms of time saved.

My experience with pricing, setup cost, and licensing for synthetic monitoring is that minions used to cost a lot and we cannot set an unlimited number of synthetic monitoring.

Before choosing New Relic, we evaluated OpenTelemetry , but we don't have the skills for using OpenTelemetry .

New Relic is a good tool that you should utilize for monitoring your front end, back end, and different APIs. If you have any critical APIs like payment, which you cannot afford to go down, you can definitely use synthetic monitoring to monitor it and get notified in your Teams channel, Outlook, or mail. I would rate this product an eight overall.

My main use case for New Relic  is monitoring the app performances from dashboards and tracing the API calls. For app performance, I monitor the four golden signals, the throughput, error rate, and the Apdex score. For tracing, I try to find out where there is latency and from which source the latency is coming, whether it is the network or the database call.

The best features New Relic  offers are end-to-end tracing of any calls and custom dashboards. Those features stand out for me in my daily work because, as an SRE and DevOps engineer, when I need to debug or find the root cause, especially when multiple teams are involved, end-to-end tracing is useful to identify the correct team and engage them further. Custom dashboards are useful to showcase high-level metrics to the leadership.

In multiple cases, I use New Relic to debug and find the root cause, especially where network calls are involved. It is also useful for alerting when the throughput is dropping or the error rate is spiking. Time is saved in debugging and finding root causes.

New Relic can be improved by providing auto-completion of New Relic Query Language queries. Custom dashboards may have more templates so that I can drag and drop and create my own monitoring dashboards.

I chose a rating of 8 out of 10 because the UI requires me to dig in and find the needed traces, and it can be more user-friendly.

I have been using New Relic for more than seven years.

New Relic is stable.

New Relic's scalability is good, and I can scale easily using the agents installed in my infrastructure.

The customer support for New Relic is excellent.

Positive

I did not previously use a different solution.

I have a long-standing relationship with New Relic, so dedicated sales teams engage with my leadership team and we finalize the costs.

Before choosing New Relic, I evaluated other options, specifically Datadog  and Splunk.

At the team level, New Relic is a good observability tool. My advice for others looking into using New Relic is that it is a great tool for monitoring your application, querying your logs, and visualizing various parameters. I would rate this product an 8 out of 10.