New Relic

There are many business use cases where New Relic can fit into the picture, it is considered as the observability platform, not merely a monitoring tool. Application performance monitoring and management are one of the core capabilities however it can do server monitoring, platform monitoring, database monitoring, and cloud services monitoring.

New Relic is suitable in the below scenarios -
1. If you are looking for an Application Performance Tool (APM).
2. If you are looking for a SaaS-based APM tool.
3. If you are looking for cloud services monitoring tool.
4. If you are looking for Application, Database, Servers, and Web services monitoring tool.

New Relic is well suited for organizations to identify and analyze performance issues. Performance can be compared between releases so regressions can be identified and performance gains can be confirmed. It also provides the ability to set up alerting so on-call teams can get notifications if something happens during off-hours.

New Relic is a powerful and useful monitoring system for front-end web services with RESTful APIs. The alert system allows the infrastructure team to discover and fix issues in [a] short span of time as they arrive on the system. This tool helps maintain the application's steadiness, security, and performance.

General Infrastructure monitoring is useful.
Would be nice to have some option to "de-aggregate" the servers with the same name.

Very well suited for modern complex application deployments, you can use features of New Relic like distributed transactions and easily identify the bottlenecks. Also for modern agile deployments, you can monitor each release and find out performance issues. Canary deployments can also be made easy with this sort of tooling.

It's very well suited for scenario-based alert setup, which in turn helps us to know anything wrong with system health in advance.
It also has a good logging system based on parameters that store the logged data that can be analyzed with NRQL.
It also helps to know the health state of the system infrastructure.

New Relic is very well suited for the modern application architecture where API and MicroServices takes the center stage.
It's very easy to identify and analyze performance bottlenecks. You can even compare API performance between a previous and the latest release and use strategies like Canary deployments. It can be setup along with PagerDuty as a great SRE toolset

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.

Brilliantly built tool for data analytics & insights generation. Creates error-free dashboards for data presentations. Could be a game-changer in the market over a period of time. The only recommendation would be to make a better & easy to understand/access UI for end user's purposes.

We were looking an analytics product which can help us in identifying issues and quickly fix them and provide effective result based on data collected.

I love using New Relic to help me get to the bottom of production incidents. New Relic APM is great, but I also use New Relic Infrastructure to help detect potential issues early, after a normal production deployment, by monitoring the health and vital statistics of my assets' stacks. New Relic even supports monitoring our serverless AWS Lambda and AWS Fargate assets.

New Relic is an excellent solution for organizations that have applications built using HTTP. New Relic's strengths are less apparent when deployed in environments that are not based on HTTP, such as message queue or RPC based solutions. If using New Relic, there is definitely a multiplicative advantage when using New Relic in more places and when leveraging more features. The risk of having vendor lock in for such a large dependency can be mitigated by New Relic's recent adoption and support for the Open Source community, especially Open Telemetry.

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.

New Relic seems like a great tool for general site ops. It's a little difficult to onboard a new front-end developer to use it quickly, since most of the tutorials are focused towards back-end developers and those familiar with site ops. I've noticed over the past few years, New Relic has definitely made moves to be more front-end developer friendly and added more out-of-the box tooling, so I expect it will continue to prove in this arena.

New Relic is a full-fledged solution that can serve practically anyone. There are however certain caveats for example in certain situations the only way to monitor and/or alert on issues is through the use of NRQL. Which can put certain users back because they have to learn the technology first. Worth mentioning that is not particularly hard to learn it just take a little more time. However once that learning curve is completed the power of the tool can be fully leveraged.

So it's a powerful tool, very much customisable and can serve to everyone's needs. But to use it to the full potential you may need to learn at least the basics of NRQL. Perhaps there are tools less powerful but easier to use. So it very much depends on the complexity of your business.

New Relic can still be considered the lead on APM and Synthetics, both have a lot of features and are way ahead of the other players. If you are planning on using these features, you will be well served.

The kubernetes integration is VERY expensive and limited on configuration. The whole thing is a black box and not very customizable. You will end up expending a lot of money not knowing why and will have limited alerting configurations which won't be as good as if you had your own monitoring stack.

New Relic can be super useful if you are struggling to improve your web performance and don't know where to start looking at.
New Relic would help you to identify the root cause of an issue with its powerful tools and the data correlation between them. It would help you saving time without having to login to individual server and analyze. It's super useful especially on containerized and server less architectures.

You might not need New Relic if your purpose is just to monitor a website uptime. It could be done by many other tools that are relatively cheap.

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 is well suited for the enterprise-wide application and microservice architecture environment. It is less appropriate for the development environment.

I think most of the APM tools are well-suited to monitor [the] production environment. what makes New Relic stand out is intuitive UI, easy Root cause analysis, better insight in data using NRQL and auto-correlation of connected dots is missing. New Relic is well suited to monitor enterprise-wide application and engineering can rely upon it.

This tool has some limitations when it comes to monitoring systems as [a] batch processors where transactions take a longer time to process.

Alert mechanism and Trace error is the best part of New Relic.