In my day-to-day activity, I check the configurations of the pod, for example, the CPU or memory utilization of the pods that are deployed in the Kubernetes cluster, by going to New Relic and checking the CPU and memory utilization. When I want to check the application logs, I use New Relic for checking the logs.

Using New Relic, we are able to monitor the cluster. In each namespace, we can see what pods are deployed, what the deployment sets are, and every other resource that is deployed in Kubernetes, which we can monitor using New Relic.

Recently we have implemented cost optimization in each and every environment. We pulled down all the CPU and RAM utilization of the pods, and later we came to know that the majority of the resources that are deployed are over-provisioned. We took those metrics and scaled down a couple of resources for the pods.

We were able to save $1,000 per month.

The resources that are created on the Kubernetes cluster can be seen on the dashboards in New Relic dashboard, which is the best feature.

If I want to make any customization, for example, if I want to see the last six months' CPU and RAM utilization of the pod, I can create a custom dashboard and check the utilization.

By using New Relic, I can check quickly the utilization of the CPU and memory of the Kubernetes nodes and the pods.

The logs in New Relic are not showing the full logs. When I go and check the logs, they are not complete. There are some missing things in the logs, and if that can be added, that would be very good.

If someone can provide the official documentation on how to update New Relic and in case I want to increase anything, those features and documentation would be very good.

From the past three years, I have been using New Relic tool, which is used for monitoring purposes. For example, if I want to check what the CPU or memory utilization is of a particular pod, I go and check in New Relic. If there are any logs, I go and check the application logs in New Relic.

New Relic is stable.

New Relic has handled changes in the environment very well.

In case I lose any access or something, there is customer support available for me. If I drop an email to them, they will respond quickly to my email.

We were using Sumo Logic for the logs. Later, the management decided to move from Sumo Logic to New Relic.

We did not evaluate other options.

I would suggest using the dashboards in New Relic for resource utilization of Kubernetes deployments, pods, or nodes. I have rated this product an 8.

My main use case for New Relic is monitoring all the servers which are hosted in my environment. The agents installed on the servers keep sending the details to the dashboard. Whenever the server is not available or online, we immediately receive an alert to our email indicating that the host is not available along with the reasons. This helps us to come to know whether the server is actually unavailable or not, and enables us to take necessary action. Apart from that, CPU utilization, disk utilization, and everything else is monitored by New Relic. If any threshold value is crossed, we immediately receive an alert and take the needed action for those situations.

Real-time monitoring is the best feature New Relic offers. What stands out to me about the real-time monitoring is the speed of the alert being the major aspect. When a server goes offline, we immediately receive an alert. The dashboard is very much interactive and we receive all the information from there. Monitoring is a crucial thing for every work, and New Relic is doing a very good job in this part. We are getting real-time alerts, and many of the issues are being resolved with timely alerts helping a lot to remediate those things. If something happened and we got to know about it lately, so much disruption would happen. New Relic is helping a lot in these scenarios.

I would not say downtime decreased, but whenever a server goes down, we are able to take immediate actions in those scenarios. That helped a lot. I would not say the downtime is reduced, but the time period during which the server goes down has decreased so much. That helped a lot.

In the dashboard, if they could show a little more metrics regarding the application and related things, that would be how New Relic could be improved. Currently, there are things showing from the server level and application level, but it can be improved. That is what I felt.

Regarding user interface, I do not feel much concern, but for some kind of issues when we are trying to get support from the New Relic team, their SLA seems to be long. They are taking seven to ten working days for resolving some kind of scenario or issue. That is a bit difficult for us. If they could improve the customer support by reducing their SLA within three to five days, if they could remediate everything, that will be so much helpful.

When it comes to the customer support part, I felt they need to be a little more improved on that part. The support overall is good, but they can improve. That is the reason I have given it eight out of ten.

For the last four years, I have been using New Relic in my current organization.

New Relic is stable.

It is very much scalable.

When it comes to the customer support part, I felt they need to be a little more improved on that part. The support overall is good, but they can improve. That is the reason I have given it eight out of ten.

Previously we were using a tool called Eggplant monitoring tool. There were a lot of issues with that. That is how we decided to change the monitoring in my environment, and a lot of research happened before New Relic came into the picture.

There is return on investment because since we reduced the downtime, we can definitely save a lot of money within that period. The tool also helps the employees in their work.

There were options like Dynatrace and SolarWinds that we explored, but New Relic is the closest one which aligns with our needs and uses.

Monitoring is a crucial thing for every work, and New Relic is doing a very good job in this part. The major concern from my side is that they should be a little more faster with the resolution part regarding customer support.

It is a great platform for monitoring. If you have a lot of servers in your environment and you need real-time monitoring, I would definitely suggest New Relic. It is a great tool to explore.

We are just consumers of this tool and do not have any other relationship with this vendor. I have given this review an overall rating of 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.

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 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.

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.

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.

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.

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.

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.

We use New Relic as an infrastructure management tool.

The tool's most valuable features were APM and core reliability. We get alerts whenever an anomaly is detected. The solution is very friendly.

The solution needs to have staging.

New Relic is stable.

My company has around ten users for the product.

The tool has good support. They have big communities and forums apart from the tech support.

New Relic's deployment was easy. They had good documentation.

The solution is cheap, but prices can go up when users grow.

I rate the product an eight out of ten.