My main use case for New Relic is to monitor application health on a daily basis. Starting with my day, I go to the dashboards to check how the application health is and any alerts already triggered for the application, whether it concerns disk, memory, CPU, or how the applications are running. Recently, we had a slow query running for the application, which was really the bottleneck as it took a long time for the application to respond, and we found it out by using New Relic to identify the slow query, which really helped me.

To troubleshoot and resolve the slow query issue once New Relic points it out, I generally go to the Application Performance Monitoring, which is APM, and then I check in APM for the query where there are different tabs, including one for the database. After that, I go and check the database, which shows what query is taking how much time. Since we are using Java applications, we can see how much time the queries take. We are also using some Cassandra for caching purposes, which can show that query. I checked with the developer about a simple select query that took a long time, and after I spoke with them, they fine-tuned that query, resolving the issue. New Relic proved really helpful in finding out the slow query.

New Relic is easy to use even for someone with no knowledge; by seeing the dashboard, they can easily find out the application's health and notice what is happening. This is a significant advantage compared to other APM monitoring tools, and another aspect I appreciate is its good alerting mechanism, which can throw alerts and can be configured with PagerDuty or Slack, allowing easy checks on triggers and troubleshooting using New Relic.

The best features New Relic offers include APM, which stands out most prominently, along with Synthetic monitoring, which also really helps. Infrastructure can be checked too, but since our organization is using these modules, through APM, I can see the heap memory, application CPU, and memory, which are crucial from the application's perspective. Multiple alerts can also be configured using APM, making it extremely interesting.

Synthetic monitoring is similar to a mix of APM and other tools. I can create multiple dashboards using Synthetics, allowing me to view synthetic monitoring in a single shot, which gives good confidence in checking my day-to-day work.

New Relic features customized monitoring, which allows us to customize and distribute dashboards, and it really helps us. New Relic has positively impacted my organization by providing faster detection capabilities, allowing us to easily find issues, which is the best advantage. We can also improve application performance by finding the actual root cause of issues, which I find really beneficial.

Regarding faster detection and improved performance, there are instances where, when the application specifies its heap memory around 20 GB, and it tries to reach about 90%, New Relic immediately detects the heap memory alert, sends it over Slack, and even calls us using Slack. This lets us easily detect the issue and delve into what Java is causing that high heap memory usage, allowing us to investigate further.

New Relic can get pricey for larger organizations.

Specifically, it's the pricing for larger scale deployments that could be improved.

I have been working in my current field for almost six years, and I have been using New Relic for almost five years.

New Relic is 100% stable in my experience.

The scalability of New Relic is very high, as I have never seen any downtime issues or similar problems.

I have reached out to customer support multiple times for various cases, particularly for customization such as creating dashboards, and my experience has been good.

Positive

I would advise others looking into using New Relic that it is friendly, easy to use, and distributed, with NRQL queries that you can easily write to check for issues.

New Relic is a very good product in the market compared to others; it is really helpful for beginners as they learn about this product, and it proves beneficial when performing longevity tests to find latency issues, making it very interesting to identify where actual latencies occur, resulting in it being an excellent product from my perspective.

On a scale of 1-10, I rate New Relic a 10 out of 10.

I have worked with New Relic for approximately three to four years.

The best features in New Relic include its numerous API integrations and a good source of support. The support is excellent, and they provide blogs and forums. There is something called NRQL, New Relic Query Language, which can be used to query many things and retrieve data. Using API calls allows you to automate and pull a dashboard out of it, making manipulation easily done. These are some things I have done with New Relic as an end customer.

It reduces the operational overhead. Your data is monitored end to end, which could be directly linked with the SLA and SLO. That is the main thing.

New Relic can be improved by incorporating an automated incident analysis solution. They have comprehensive enterprise data, and based on that, they could generate and forecast things. They can predict anomalies, and even though anomaly prediction is already there, it can be improved.

Using real-time data, if there are any malicious patterns or something happening, they can identify those. They really need to stream the data and have something important running, such as predicting or identifying any suspicious activity. If they could develop these features, it would be very beneficial.

In my opinion, New Relic is a stable solution.

I would rate the technical support from New Relic as nine out of ten.

Positive

The initial setup of New Relic is pretty easy. It is very well documented.

The deployment of New Relic was done in-house.

I am not sure about ROI as I have not gone over that. However, it reduces the operational overhead. Your data is monitored end to end, which could be directly linked with the SLA and SLO. That is the main thing.

I have experience with various Amazon solutions, but I am not really involved in the data-related role. My scope is that I work within some specific services. In my organization, I am part of an engineering team where I work only with these specific things. I love to explore these things, but I do not have much hands-on experience, and I am not a subject matter expert.

I have worked with Zabbix and Grafana. Grafana is a visualization tool that allows you to ingest existing data and visualize it while taking a report out of it. It is a great monitoring dashboard tool. Currently, in my company, they are using other solutions DataDog and New Relic. However, I would choose Grafana. It is open-source, and the enterprise edition is also available. The open-source version is more than enough for an enterprise to have their data visualized.

New Relic is suitable for banking domains, investment brokerage products, or anything related to high-security data. Organizations might use New Relic because they want their data stored and they want the support. It works as a whole monitoring solution, including logging, monitoring, and application profiling tools. It has a good set of API for managing alerts, and many automations can be done in New Relic. It is an enterprise solution that requires payment.

I rate New Relic eight out of ten.

Our main focus is APM-related functionality, so we were looking for a convenient way to get all the details, as some of them are missing from New Relic and Grafana. Currently, we are working with Site24x7, where we are getting the information we are looking for in our comfort zone.

We used the Docker container as the agent in our server, which was split into one agent to collect the client's logs and metrics to see the web vitals, and another metric to collect the server metrics and APM-related traces.

The main benefit we found was the Error Inbox, and having all features available at a single point was very useful for us. The API functionality allows us to get hit counts from external sources, such as APIs or databases, and everything is mapped very clearly. We can overview which components are experiencing response delays, which ones are getting correct responses, and identify any unknown external APIs inside the application. We can investigate why we are getting 400 responses and similar issues.

I reviewed another observability tool, DataDog, and we moved away from New Relic because the pricing was not convenient and didn't fit our budget. With DataDog, some of the APM features we were looking for were not available, so we discontinued using both solutions.

Grafana is helpful, but it requires significant work in adding agents and configuring applications and server metrics. We implemented open-source Grafana, which wasn't convenient regarding APM, and most of the logs and traces related to APM were not what we needed, so we moved to Site24x7.

The Grafana Open Source implementation was done through their vendor. While they provided certain features, when compared to Grafana Cloud, the customized Open Source version wasn't really convenient for us. The only helpful aspect was that we could get server metrics on Grafana Open Source from our servers.

I have been working with New Relic for approximately six months.

New Relic was stable enough, and there were no downtimes or issues.

New Relic offers 400 GB per month free, but that quota was completely used within two weeks for a single server. We have substantial data in our server as our company is a trading financial company. For a single server, it takes around one and a half to two weeks to reach the limit. Additionally, we need to store logs for over five years based on SEBI regulations.

I didn't seek any support help from New Relic, but when I tried to get information regarding the plans, the response was delayed for a week. Other than that, everything was fine.

Positive

We reviewed Grafana and moved to another observability tool. We also evaluated DataDog, but we ultimately moved away from New Relic because the pricing wasn't convenient and didn't fit our budget. We are now using Site24x7 in production.

Implementing the New Relic agent is quite simple, and we were very comfortable with New Relic overall. However, it wasn't convenient based on our budget, which is why we discontinued using it.

The Grafana Open Source implementation wasn't done by ourselves; we worked with their vendor. They explained the features available in Grafana Open Source, and we implemented those solutions. However, compared to Grafana Cloud, the customized Open Source version wasn't really convenient for us.

The Error Inbox and consolidated features at a single point were very useful features. We could get hit counts from external sources, APIs, and databases, with clear mapping of all components. We could monitor response delays, correct responses, and identify unknown external APIs within the application.

We also reviewed DataDog as an observability tool, but we moved away from New Relic due to pricing concerns that didn't fit our budget. With DataDog, some of the APM features we were seeking weren't available, so we discontinued using both solutions.

We had everything in hand with New Relic initially. However, the pricing wasn't convenient for us, so we had to step back from using it.

I primarily focused on the data we were getting from New Relic, without exploring custom dashboards and other features. We were mainly focusing on the metrics and logs needed to trace our applications effectively.

On a scale of one to ten, I would rate New Relic an eight. It's overwhelming from my point of view, and we needed to do some organizing in our New Relic account based on our preferences.

I use New Relic for the creation of dashboards, alerts, and any type of observability resources that are relevant for my company.

The most valuable features of New Relic are the ease of creating dashboards and its integration capabilities with many external tools. It enhances operational response by providing analytics and alerts that help us address issues quicker. 

Using New Relic speeds up troubleshooting and resolution, giving us a clearer picture of where issues are, thus saving time and effort.

Email alert customization is limited; it cannot be tailored much, which makes the system more rigid than optimal. The handling of logs from integration tools is not as advanced compared to other tools. AI integration, including predictive analytics, is available for certain features but is not comprehensive.

I have been using New Relic for one year.

I find New Relic to be a stable tool. It is reliable in the aspects that I use.

While responsive, customer service does not always provide straightforward solutions immediately. Issues that could be solved quickly sometimes take longer because they go around in circles. However, they are helpful when direct interaction is initiated.

Neutral

The setup is easy for the part I'm responsible for. However, since I do not manage the complete product setup, I cannot comment on the entire process.

For our part, New Relic has provided value by speeding up issue troubleshooting and resolution, allowing for more efficient use of time.

I rate New Relic seven out of ten. 

For those looking to use New Relic, it is more suited for networking and infrastructure monitoring rather than application performance monitoring, integration, or API log handling.

I use New Relic for monitoring and observing the entire environment. It offers end-to-end monitoring and observability to predict potential impacts in the coming weeks. For instance, it can detect if two endpoints start consuming more bandwidth than usual, thereby providing more insights about potential impacts on the environment.

New Relic helps us maintain and shape the environment from a network perspective by providing end-to-end monitoring and observability. It offers insights into normal and peak behaviors, alerts us to any issues, and assists with remediation plans.

The APM feature is highly valuable as it can record session hosts, usage, and diagnose customer behaviors. Additionally, we can simulate user actions to assess the user experience. The alerting capabilities are also efficient, sending emails and desktop notifications, and providing remediation options.

The pricing could be improved as it is quite high relative to what is offered. The cost versus performance efficiency could be better. Apart from that, I don't need any specific improvements to the features themselves.

I have been working with New Relic for over one and a half years.

New Relic is highly stable. I have never experienced an outage or any misbehavior with this solution.

New Relic offers high scalability. It is quite flexible and can scale according to our needs.

The technical support team for New Relic is good. I would rate them a nine out of ten.

Positive

Before New Relic, we did not use any specific solution for observability. We used normal monitoring tools.

The initial setup of New Relic is super easy and straightforward. It involves proposing the solution to the client, activating administrative users, and customizing dashboards and alerts based on customer needs. Training and preparation made the process smooth and efficient.

The deployment typically requires two to three tier-one or tier-two team members from the technical team.

The pricing is relatively high. It can be quite costly compared to the performance efficiency, making it not very value for money, especially for smaller businesses.

We evaluated several other options like Datadog. However, after comparing prices and support, we chose New Relic.

Do not implement New Relic until you have identified your needs and ensured that it meets your specific requirements. Proper assessment and planning are crucial.

I'd rate the solution eight out of ten.

A typical use case with New Relic, it’s an APM tool. We basically put the agent in, the agent discovers, and then we feed it onto predefined monitors with a controlled baseline. That baseline will then feed the problems that New Relic is detecting into PagerDuty. PagerDuty is our incident management tool. PagerDuty has something called Event Orchestration.

The incident that comes down from New Relic has a payload. We look at the payload, the attributes, and define rules in Event Orchestration. Let’s say the team wants to implement suppressions on alerts, some mutations, delays. They want to actually cross-engage a different team. So there are a lot of use cases that come about once we get the incident into PagerDuty from New Relic. New Relic obviously has the conditional baseline, which can be adjusted as we go along. So, that’s basically a staple activity that we perform with New Relic. Among other advanced use cases, which will take me a bit to explain here.

It’s like any other APM tool. One of the most outstanding features of any APM tool is the anomaly detection part. If there is logic that is going to detect the anomaly, with a predefined baseline that the system will produce over a period of time, for instance, a week, then keep adjusting it as you go along. That is one of the most useful cases of any APM tool that I feel.

One of the things that our enterprise actually had a challenge with was the licensing structure for New Relic. I remember there are two things that I feel are different in New Relic from Dynatrace. You have a user model version, and you wanted your clients to be on user model version two. But that’s not easy. You have to build that user structure from scratch. That was one of the downers we felt in Nutanix. And the other thing was the licensing.

The licensing structure was slightly different from Dynatrace. Dynatrace gave us a better deal, to be honest. Apart from that, I don’t feel they’re two different tools. These are the same tools.

I have been using it for about four years. 

I would rate the stability a nine out of ten. It is stable. Everyone uses SaaS platform. It never went out. There was no unplanned outage, at least that I experienced, apart from the regular maintenance windows or predefined windows by the vendor itself. 

So, it has been stable product.

It’s easily scalable because you deploy your agent. Our enterprise used to have a starter kit. The starter kit was basically an initialization of deploying the agents against our OpenShift. We had Kubernetes running under OpenShift. So there was a starter kit that deployed it. I didn’t feel anything really difficult with the implementation of the starter kit. So it was pretty okay.

I would rate the scalability a nine out of ten because nothing is perfect.

We regularly used to meet with the success manager, and there were technical people as well. We had at least once a month office hours with them. And then on an ad hoc basis, if we needed them, we used to engage them.

Positive

I have used Dyntrace, GCP and Prometheus. Dynatrace has a little bit more edge, not from the product technicality point of view, but purely from the way I think the licensing scheme is modeled. The product behaves a little more easily compared to New Relic.

The initial setup is easy and straightforward. 

Dynatrace is a little more complicated than New Relic, but New Relic was easier to deal with.

I would rate my experience with the initial setup an eight out of ten, with ten being easy and one being difficult. It is not that difficult to setup.

The licensing model was more expensive compared to competitors because of the way they were defining their user structure; there was full-stack observability and less than full-stack observability. 

There’s no advantage to having anything less than full stack observability because once you get people on board with an APM tool, they would like to know as much as possible about what the agent can discover. 

If the agent is able to discover and you’re not giving anybody full-stack observability, it’s like you’re treating your product like Lego. The more you buy, the more expensive it gets. If you want to make it into any bigger construction, you gotta pay more. So that was a downer.

Overall, I would rate it a seven out of ten because of the licensing issue. 

At this point, Dynatrace is doing better than New Relic.

It is used to monitor applications, error logs, and Azure Kubernetes. We have used this as a self-hosted service in Kubernetes. We are not using it as an agent-based service. We self-hosted this New Relic on Kubernetes and maintained it as a service.

It can be integrated with PagerDuty and ServiceNow, which can auto-generate alerts and incidents and assign them to the concerned team. The dashboards can also be customized. We can also check the trends over the past year or so.

It helps prevent issues but does not cause losses. The error messages and deep insights may help us find the root cause and resolve the issue.

It could be bit better. We are looking at sorting the error loss by date, keyword, or something similar and grouping the logs with some keywords, like error.

I have been using New Relic for two years.

I rate the stability an eight out of ten.

I rate the scalability an eight out of ten.

I haven't got any issues, so I should get support from a New Relic technical team. We hosted this on our own, and even though this is a self-hosted service, we are managing it. 

The initial setup is simple. We are using the Relic Chart deployment on Kubernetes, but it can be done in an hour and should not take longer.

We just got a license for self-hosting and have set it up to do this.

Some add-ons have been integrated. You can integrate with New Relic to get deeper insights into the logs.

I have worked on two monitoring tools: New Relic and OpeRant. In addition, I used Azure Monitor. It's completely different, monitoring only the infrastructure, not the applications. We need to know application insights about querying and everything, but it's more user-friendly.

Overall, I rate an eight out of ten.

It is for APM,  Application Performance Monitoring. And server monitoring.

There are two types of teams we have in every organization. One is for DevOps, and the second one is for performance testing. Those who are using these tools, like AppDynamics, Dynatrace, or whatever tool we have on the APM side. 

These tools are used by two teams: one is the performance team, and another one is the DevOps team. So, the setup and the alert system belong to the DevOps team, not for performance. So, I don't use any alerts in AppDynamics, Dynatrace, or any of the tools. 

There is room for improvement in the stability.

I have experience with this product. 

I would rate the stability a six out of ten. It can be improved.

Scalability is not that much available with the applications.

There are around 400 to 500 end users. 

Whenever it is needed, they have provided support from the New Relic side.

Whenever they get their customers, they'll go for approval, then they will assign someone, then that person will come and understand what issue we are facing and what we require. Then they will try to resolve the issue.

I prefer AppDynamics and Dynatrace. These two tools over New Relic.

So, integration is possible with LoadRunner and other tools in New Relic.

I would rate it a six out of ten. 

I use the solution in my company to monitor the applications' performance and do some stress tests on the application. In our company, we use the tool to monitor the core application inside the data center. In some cases, New Relic is used to monitor users' access to the applications.

The most valuable feature of the solution is its ability to execute queries and analyze the data. For all the data, the tool has a specific function with which you can spot and mix the data or correlate the data wherever you want. It is easy to simulate and execute queries, and the availability of the data is very nice. The tool gives you a basic way to manage the data.

The product's initial setup phase is not straightforward to manage if you have no experience with installations, making it an area that can be improved.

I have been using New Relic for a year. My company is in partnership with New Relic.

I think the support of the tool is a good option. I think the support of the tool. I rate the tool's support an eight and a half out of ten.

Positive

I have experience with Catchpoint. With New Relic, you monitor the application from within. You monitor all the communication calls between the application and all the systems that the application needs to use, such as databases or servers. With Catchpoint, you can monitor user experience and how it interacts with the application, so we are monitoring from the outside, which is from the user to the application.

For the product's initial setup phase, you need to have a background of doing installations. It is not a straightforward process, as you need to have more skills to do the tool's setup. The tool's setup phase is a little bit more complex but with the correct knowledge, it can still be very easy. You have to have some prior knowledge in installation to start with the tool's setup phase.

For the product's deployment phase, you need around 20 people because you need the people who do the installation and connections, along with the owner of the platform or the database, for which there is a need to create some access using New Relic. You have to do some configurations or partitions to install the agent. You need to have an expert on New Relic, as well as the user or the administrator of the infrastructure where the tool will be installed, so customizations can be done if needed.

The time required to deploy the solution depends on the amount of installations required and the architecture where the solution will be used. One agent can be deployed in maybe 30 minutes. Depending on whether you have everything in place and people know what they are doing, it may take 30 minutes to deploy the tool.

The tool can not be related to productivity. The product helps the development team that develops and makes changes in the applications. The tool helps a lot and provides a lot of information to the development teams so they do not have to do simulations. With all the information that New Relic provides, the development teams can just make decisions about the changes within the applications during the development. The tool offers information about the business process. With the tool, you can have all the information related to all the purchases from the marketplace and understand why the purchases were okay or why not, why the people that are logging in are not making any purchases, along with all the information related to the business process that are very helpful for the business.

The product is neither cheap nor expensive, and I believe that it is a competitively-priced tool.

I don't know how the alerting mechanism in New Relic has improved our company's response time. I am more into the demo part, so I am not a user of the tool.

I rate the tool a nine out of ten.

I use the solution in my company for predominantly API response time. It is used to measure API response time.

New Relic is very slow, and the app is a bit frustrating to use, which is something that has been happening a lot in the past year. During the last six months, I have noticed that it has become extremely laggy. The irony stems from the fact that a tool used for performance measurement itself has so many performance issues. I think it has also become too crowded with too many features. I have been using New Relic for ten years, and over a period of time, it has added a lot of new tools and new profiles, which are great, but now the tool has become too crowded. Around 80 percent of the time, I use the tool only for basic use cases, which were all there even ten years ago. The tool has definitely improved the interface, which is good, but apart from the basic features that I need, there are all these features in the tool that crowd the tool's entire user interface, which becomes complex. I like Sentry because its main interface for error reporting and handling has always been very clean and focused while not being crowded with too many things, but I don't know about the solution's future. With New Relic, the tool seems crowded when it comes to its interface, which has too many features.

I have been using New Relic for ten years. I use the solution as an end customer.

It is a scalable solution. The product operates as a third-party or SaaS tool, so I believe that it has intra-scalability options.

The technical support for the solution is very good. I rate the technical support an eight out of ten.

Positive

My company has been using Sentry for error reporting, alerting, and monitoring.

The product's initial setup phase was very easy.

One person can manage the product's deployment phase. Once the product is installed, it doesn't require much maintenance.

The solution is deployed on a cloud-based infrastructure.

The solution can be deployed in less than a day.

I rate the product price a five on a scale of one to ten, where one means cheap, and ten means very expensive. I don't remember the product's exact price, but I know my company pays around 500 USD a month for two or three products.

For monitoring purposes, I would say that the product has a good interface for quickly finding performance bottlenecks.

The tool gives a detailed audit of every piece of code, like how much percentage of time it takes, making it very easy for me to first locate the APIs that offer the poorest performance and then go deep dive into those APIs to see which part of the code base of that API is causing performance bottlenecks. Instrumentation becomes quite straightforward and easy with the tool's features.

I don't use the alerting system in New Relic.

My company uses New Relic only when we want to instrument APIs and for performance improvements, but we don't use it for error handling and error reporting since we prefer Sentry for such areas.

I rate the tool an eight out of ten.