New Relic

If you have technical resources on staff, then New Relic might be a good choice depending on what you're looking for. If you're looking to do one simple thing (like track JS errors), then there might be a better solution out there. New Relic is for highly technical users who are looking to do a wide variety of things.

New - relic is well suited if you want to analyse the performance of your services and you want to improve it. Integration with multiple services with same account gives a clear picture of flow of your APIs if you have micro-service architecture.
New-relic is less appropriate when you want to do logging of your system. As it does not emits every single calls.

Our product is used by vast amount of users and also users are getting increased also we have large numbers of infrastructure involved to run this giant system we have manny servers, 4 to 5 kubernetes clusters, databases, 2 public clouds so in order to achieve the excellence in infrastructure side new relic has helped us in many ways we don’t have to open the public cloud console and along with it 2 or 3 other tabs to view the resource utilisation by new relic we can view our entire infrastructure under one hood, also their utilisation, alerts, logs, uptime control all can be done from the same tool only.

Wanting to have a developer friendly application that is highly extensible to help monitor and ensure high application availability, I believe New Relic is the best in class. As teams grow and if you want all engineers to have access to New Relic the pricing can get very expensive and would require working with your account rep to try and get a contract in place that fits business needs.

When you need automated alerts and good traffic data, New Relic is a great tool. You definitely get what you pay for, and while New Relic is priced competitively, it gives a lot more than the free or cheaper solutions.

From my perspective, NewRelic can help when you need to met SLAs within your organization. In our use case, having a multi-tenant infrastructure, we monitor the apdex score metric and we have configured some thresholds for that metric and alerts when its value is under those defined thresholds. There were sometimes where the infrastructure was not alerting, but an application was (with a low adpex score). In those cases, it was nothing related with databases, servers, or any other resource, but it was a specific client configuration.
On the other hand, from our point of view, it wouldn't be suitable for monitoring infrastructure. In our case we use many built-in AWS services to monitor several components of our AWS resources, among with CloudWatch custom metrics.

Anything related to application monitoring, alerting, logging, dashboarding, feature rich instrumentation and querying.

New Relic is well suited for gathering the logs from all of our servers, later on enabling [us] to query them (also in real-time) for debugging purposes. It's also built for helping [to monitor] our servers and comparing stats backward in order to see the trends in our servers' performance.

New Relic is well suited for eyes on monitoring of live systems, in our case a high transaction eCommerce platform giving across the board metrics on throughput, errors, infrastructure performance, and distributed system performance. Its log ingestion and presentation is not as good as saying Splunk is, particularly for querying but could have more potential if it could be tied to its error analytics and alerting, that would be game-changing.

Great for quickly and easily setting up server-side, client-side monitoring of node/.net applications; could use some improvements in the Alert policy management feature-set, especially with the integrations of third-party vendors such as OpsGenie

New Relic has so many great features that would be helpful but it come with an expensive price tag. If your company only needs some part of it, I do recommend choosing the less pricey one or just building your monitoring system using open source. But if your company growth is doing great and you want to improve by having visibility in each aspect of your system and integrating with business needs, New Relic is the way.

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.

We use New Relic vary widely from monitoring to alerts for our APM AWS Lambda instances have a limitation with New Relic and we are scratching our heads to learn how NR can be used when App is hosted on AWS Lambda.

For monitoring specific URLs for response time, tracking performance of an application over time, and being able to drill down to the function level where an app component might be experiencing an issue, it seems to be well suited.
Also, the overall NR suite seems to experience rapid changes, which could potentially be somewhat unsettling to users who are trying to get familiar with a feature area. I'm unsure also, how consistently these are documented.

It seems to have less ability them some other products, to be able to see what low-level procedures on the code or DB side could be bottlenecks.

It's a good tool but it requires a lot of customization. Some alerts we have to create I thought should be more obvious or out of the box. I also feel I don't get a deep insight into my Pod > Containers > services. I see my pod memory, how's my actual node service using memory? Are my java processes garbage collecting well? Another big complaint is the lack of availability/observability into GraphQL requests (should be a very popular api). I really had to dig to find anything that was telling me how my pod CPU and memory are doing "in relation to their request and limits." Are my limits too high, too low? Why am I not getting an alert when I'm sitting at 100% of my limit. Instead the default graph shows my pod is at 60% CPU, that sounds good until you figure out 60% is the limit and NOTHING is telling me I'm hitting my limit. I probably need to adjust my resources, why NR isn't my tool making this easy to see? Where is the report for this? The other big concern is COST. I don't want to be told by IT/Ops that we can't add something or monitor something because the tool is so dang expensive.

New Relic is a fantastic tool to gain insights into how well your application is performing. If you have the budget, it is one of the best tools I've used of its class. However, if your organization is operating on a budget, there are now relatively mature open source APM offerings on the market.

For back-end application and for front end with SSR, New Relic is very well suited. All the metric and monitoring tools are very good to keep the application up and to see that everything is working fine. For SPA front end application (browser) our team prefer other tools to monitore erros and file download time.

I can't think of any scenario where New Relic would not be appropriate. I am not so sure I would even be confident enough to deploy code in my current job without New Relic. One thing to mention though is: it can send a lot of data and it can become quite expensive as New Relic is charging for the ingested data amount.

New Relic works great for monitoring a complex piece of software where performance matters most. It's great at identifying bottlenecks in your application and database queries. New Relic is also great for any DevOps team, as it allows quick visual access to complex systems.

[New Relic] will automatically track and monitor the number of DB queries and can easily show the paths that are not performing well. You can easily identify the paths that are not performing and fix them. Once fixed, we can very easily check whether the fix has improved or worsened it.

I think it is well suited for anyone needing to monitor a production software environment. It's suitable for both operations-focused engineers as well as normal developers. I believe that every technical organization should empower its members to take part in monitoring and tuning production systems. New Relic is easy enough to use, yet has enough advanced features that it can provide value to both of those groups.

New Relic is well suited for a complex enterprise application. Less suited for a side project.

Well suited to find the processes that cause the bulk of CPU load, network load, memory load etc., etc. Find very detailed logging on unhandled errors that you wouldn't have found out without New Relic. You can drill down into the function tree to get to that single database call that caused the website 6 seconds to load.