The most valuable features for us are:
- Application performance index score
- Error rate
- Transaction traces
The most valuable features for us are:
When an app goes down, we can get insights into the issue with New Relic. It tells us what the problem is. For example, if there is an issue in the code, we see a spike in the error rate in the applications. The load environment lets us stress test our application to find the bottlenecks in the code.
They already have everything we need, so I can't suggest an improvement.
I was not involved with deployment.
Very stable. No problems.
No problems.
One issue – there is no option for live chat or phone support. We can go to the community forum to post a question and wait for the answer.
The solution was already in production when I got to the company.
New Relic is the right solution in my opinion. The light version of server monitoring is free with New Relic, and application performance index and error rate are the key features to look into.
I find the error monitoring of IIS web applications to be extremely useful. Being able to filter errors by URL, server, and period of time has been extremely helpful in quickly isolating and fixing problems. Being able to see a list of slow transactions is also very helpful in identifying the root cause of application performance problems.
In one case, a developer had an end-user report a recurring issue with a web application after a new release. I was able to use New Relic to find the error and provide the developer with the exact line of code that was causing the error within minutes of the issues being reported.
I can't say as I haven't used all of the features.
I've used it for one year.
No issues encountered.
No issues encountered.
No issues encountered.
I haven't had to contact customer service.
Technical Support:I haven't had to contact technical support.
We didn't have a solution in place prior to deploying New Relic.
It was straightforward.
We didn't install it through a vendor.
This tool has really helped us in monitoring our production apps and also to diagnose the errors coming in using APM and synthetics modules.
I have logged a bug in their Ping Monitor within Synthetics and I need more improvement in this area.
I've used it for two years.
No issues encountered.
No issues encountered.
No issues encountered.
9/10.
Technical Support:9/10.
No previous solution used,
It was quite simple.
We implemented it in-house.
We are getting a very good ROI as out production quality has gone up with more issues getting detected on local environments.
It is very simple to implement and it adds great value.
New Relic shows how much time each SQL transaction (SQL query) is taking to execute. By this, client can pinpoint the query and modify so that it takes less time to execute.
New Relic has detailed analysis of various parameters such as Web Server, Database server, Application Server etc. so we were able to provide the client with more productive reports.
Additional functionalities and application up time.
No major issues.
Yes, sometimes.
Yes, sometimes.
Used rarely, was average.
Technical Support:Used rarely, was average.
Cost effectiveness.
Straight-forward, though not completely.
In-house.
Good.
Check for scalability and application up time.
Over the years I’ve come to rely on information radiators during testing to get immediate (or as quick as possible) feedback from the systems I’m testing.
Firebug, log files, event logs and many other sources of information are all very useful to a tester. They can give you insights in to what is happening in the system under test.
We’ve just taken this a step further by rolling out NewRelic on our test servers.
NewRelic is what’s termed a “Application Management Solution”.
I’ve been talking about this internally as a system that can give us three distinct insights:
I’ve probably over simplified the tool and doing an injustice but it allows me to clearly explain the value we’re seeing from it.
User Experience Information
NewRelic gives us all sorts of data around how the experience is for end users when they use our product.
We can use this to ascertain how our product is being experienced by our customers, but we can also use it to understand how the experience is stacking up for our testers.
If we are testing and we observe a slow down we can check whether it really was a product slow down using NewRelic and more importantly; what’s actually happening on the stack.
We can use NewRelic to work out what browsers are being used across all of our environments. We can see the test coverage we have across browsers and we can also see what browsers our own business use from our pre-production test environments (where we test all kits before live deploy).
We can also then see which browsers are faster than others. We can see which versions are used and which browser is our most heavily used. Interesting stuff to help guide and tune our testing.
Server Information
NewRelic monitors the actual servers giving all sorts of information such as memory, CPU, process usage etc etc. This is great information on our test servers, especially during perceived slow downs or during a load test.
We have other mechanisms for measuring this also so this is the least used function in NewRelic when testing.
Product Performance Information
For me, this is the greatest information tools like NewRelic offer; they show you what the product is actually doing.
It includes what pages are being dished, how fast are they being dished, where they may be slow (in the DOM? Network?), what queries are being run, what part of the code is running them and how often they are being called.
When we dig around in the data we can find traces that NewRelic stores which give an amazing level of detail about what the product is/was doing when the trace was run.
It’s going to become a testers best friend.
In a nutshell what it allows us to do is provide an accurate picture of what the product is doing when we are testing. This means we can now log supremely accurate defect reports including traces and metrics about the product at the moment any bugs were foud.
The programmers can also dig straight in to any errors and be given the exact code that is generating the error.
We can see which queries are running meaning that if we encounter an error, a slow down or something worth digging in to we have the details to hand.
It’s still early days using the tool but already we’ve had deep insight in to how the product runs in our environments which I’ve never been able to get from just one place.
It’s immediate also. Test – check NewRelic – move on.
Imagine how powerful this could be on your live systems too.
Imagine the richness of information you could retrieve and imagine how fast you could get to the root cause of any problems. It’s powerful stuff. Expect to hear further posts on how tools like this can inform tests, provide a depth of supporting information and provide help to performance testing.
Some notes:
Our primary use case is for application performance management (APM. We use New Relic to monitor API performance on the servers. It is a safety monitor for the performance.
New Relic is now the leader in efficiency improvement. We are able to configure our own specific dashboards so that we can monitor the things which we want to monitor.
Some of the parameters in our deployment, which we already know and we want to monitor constantly, can be selected on our own custom dashboard.
The most valuable feature of New Relic APM is the dashboard, New Relic Insights. I configured my own dashboard to monitor certain parameters.
I would like to see the company implement the AI auto-baseline feature which Dynatrace has.
New Relic APM is more stable than Dynatrace. I don't have to upgrade that often. I'll need to upgrade Dynatrece after every few months for any of the new releases.
Sometimes, with Dynatrece after an upgrade to the new release, i.e. if I need to upgrade every half a year, it's not compatible or it has some compatibility issues.
I don't have any issues with the scalability of either New Relic or Dynatrace. They are both quite scalable.
New Relic doesn't have any offices in my country, so most of the time we have to use the web for resources or phone support for customer service.
New Relic APM was recommended by another vendor to our company. The software platform features and the local support of the agency were included in the package.
Those two factors sold us on New Relic APM as a solution.
New Relic APM installation is quite easy and very straightforward.
Pricing is better with New Relic APM than Dynatrace.
I recommend evaluating both New Relic APM and Dynatrace to see which features benefit your company specifically. Dynatrace is easier for getting started with no experience.
If you are a very experienced user and have intimate knowledge of your network architecture, then choose New Relic APM over Dynatrace.
The reason we chose New Relic is the pricing. I will rate New Relic APM an eight out of ten for review. Overall, New Relic is not as good as Dynatrace.
I have to understand my own system and I like the New Relic APM dashboard. The software could be faster and more automated.
APM products are something that needs to be well-tailored to your specific needs and environment. for the project i'm currently working on, we chose new relic after a bakeoff with another vendor. both products were great, but new relic came up on top and we've been very happy with the insights it provides.
This review assumes one is familiar with APM and will not cover the basic benefits of New Relic as an APM product.
Strong points:
New Relic was very easy to deploy and had minimal impact on our environments. Visibility was near-total out of the box and support was extremely helpful in adding the missing instrumentation into the product.
New Relic supports a good mix of environments which is important to us as we work with several languages.
Support for background tasks is also an important feature for us which is usually not as well-covered in other products.
It helps us organize the data from our clients and reason with it. Moreover, with the client JS API, we can report data to New Relic and query it with Insights. It is easy to use and has an understandable graph editor.
This is the real deal.
Tracking and monitoring production is mandatory, however, we did it for years only for the back-end side. As the client-side applications grow bigger and get more complex more responsibility gets to the client. Because of that we must be able to understand if our clients are "healthy". The term "healthy" is not clear to what it means.
Presently we report data to New Relic Insights, and we've built some really readable and understandable graphs. We monitor with those graphs every deploy to production, and we are advising the graphs to resolve current problems with our application, like errors and problems with the load and response times.
New Relic comes with some features out of the box, but not enough. There are some essential features that New Relic needs to implement that their competitors already support, like special treatment for AngularJS/React applications. We had to implement (with the JS API) the ability to query errors through Insights which is essential. Currently, we don't have a way to send alerts which is a real pain.
We are using it in conjunction with APM and Insights.
We've had no issues with deployment.
We've had no issues with stability.
We've had no issues with scalability.
We also looked at Raygun.io and TrackJs which are great products, but neither has the tri-factor, which is:
New Relic has a good separation between the data that you report and how you show it, along with data you get out of the box. My advice is about how to show the data in a way that it will be easy to reason with it.
You can build many different graphs, really try them all, and then decide what fits best for your organization. That's what we did. The way you handle data varies between organizations and even between teams in a organization, and the ability to show the data in different ways is very helpful with that.
New Relic always gets new things done. The system is always changing and in a good way. New features are always coming into the system and we are very happy with it.
I also liked the Dynatrace feature. I have noticed that NetScout has added the same mathematics for predictive and baseline and also anomaly detection for volume and number of transactions and transaction types like GET or PUT or whatever for HTTP and similar for databases and so on and so forth. I don't know how far reaching it is though.