We used Splunk, AppDynamics, and Datadog, apart from New Relic APM, but New Relic APM was the best in terms of MVP (Minimum Viable Product).

I'm also familiar with Datadog, which offers excellent RUM in comparison to New Relic. 

Previously, we did not use other application performance management products.

We also use Azure Monitor. They are very much the same. However, we've since moved over to Azure Monitor.

I previously used AppDynamics. I liked it a lot. Since the acquisition, we've mostly used New Relic. I prefer AppDynamics because I'm familiar with it, and it's easy to use. I don't remember the specifics about features, but I liked the overall feel of AppDynamics.

We are currently using Dynatrace. We have moved away from New Relic because of its shortcomings – the user data schema. They had two versions, and we couldn't group different entities under version one. For example, our enterprise applications are numerous, including activation, OSS, BSS applications, and so forth.

We have previously used a different solution, and we switched only because our current customer was already using it.

We were using Dynatrace before, and then we switched to New Relic.

I have also used AppDynamics to show us the time that the APIs were at a certain level, like the database level or application level. I think New Relic has started implementing the ability to trace transactions to that level, but I don't know if that feature was well developed because I didn't use it a lot in New Relic. 

In Apigee, for example, they monitor a certain percentage of the transactions to show where the bottlenecks are.

The supportability in AppDynamics is good.

I'm also aware of Dynatrace. In Dynatrace, they have an integration with LoadRunner. You just have to add one or two lines of code in LoadRunner, and it will integrate with that, which is really good. 

New Relic doesn't have the option of integration with LoadRunner.

I have used AppDynamics previously and New Relic is easier to use and user-friendly. 

I have also used Dyatrace and prefer New Relic because of its license and usability. However, if I look at the features I then would choose Dynatrace, it has more features.

I used Dynatrace before using New Relic APM, but that was in my past organization. I switched to New Relic APM because I moved to another organization. I also use Datadog, but mostly, it's New Relic APM that I'm using.

In my current organization, I did some POCs, but not effectively, so I've only used New Relic APM and no other solutions, at least in the organization I belong to now.

There were no other tools being used previously. This was the first we were recommended, and we deployed it.

My company also uses AppDynamics and Datadog for some of the applications, but those will be moved entirely to New Relic APM, as the tool is very user-friendly and has no lags. AppDynamics, on the other hand, has some delay, and you have to inject some methods in writing applications to gather the metrics. Performance-wise, New Relic APM is better and doesn't cause a high response time compared to other solutions.

We have two custom in-house processes that do our application data flow monitoring. We have manually and in a custom nature, built out a performance monitoring platform in Splunk using our knowledge of the system over the years.

I have used App Dynamics in the past with another company. There really is nothing that stands out with New Relic. It is similar to AppDynamics and Dynatrace.

I've used Stackdriver in the past. However, it doesn't work well, with, for example, virtual machines.

We used to use AppDynamics, which is one of their big competitors. I don't exactly know why the switch. We were told to go to New Relic. I think a lot of it had to do with the cost. Possibly, they found New Relic to be a cheaper alternative to AppDynamics.

I kind of have worked on different tools, but then no one has provided a unified solution. I've worked on ELK, Sumologic for centralize logging specifically. I've also worked with Splunk.

AppDynamics also provides these features, but I have not explored AppDynamics so much.

I'm more familiar with the likes of Dynatrace, AppDynamics, and New Relic.

We are just getting into a scenario where we might end up using AppDynamics. Otherwise, I haven't used anything before New Relic in a similar way.

Previously, almost four years ago, I used AppDynamics. I think that it is a very good tool. I would rate AppDymanmics an eight out of ten.

We changed to another solution because of the cost. All of the developers loved the AppDynamics dashboard. It was very clear.

We migrated from AppNeta because the solution is more stable and cost effective. 

We were previously using Datadog. At the time of the switch, both companies were closely related product-wise, and some of our company was already using New Relic. We also chose it because the monitoring tool and alerting system fit our needs.

We previously used HP Diagnostics and CA Introscope. We switched for several reasons -

• UI interface required more training of the support teams to utilize the product because it wasn't as intuitive.
• Large infrastructure to support and administer the environment.
• Requires RUM appliance to tap the network so that we can gain insight into the end-user response.

I was the one who recommended Insights. We implemented a trial for 60 days and we ended up saying yes. We love it. We do a lot of dashboard stuff. Especially the executive management, they just want to see what happened in a given week or time. What did the vendors do? What did the customers do? Who’s working on what?

We are mainly using Tomcat, but we use New Relic simultaneously. New Relic works as well Tomcat.

We were previously using a different, comparable solution. However, we decided to switch to this product as it provided lower response times.

We were using another solution previously. New Relic APM was picked by the organization because they preferred it, and this is why we switched. New Relic APM is easier to configure.

I am using Dynatrace at the same time and I don't see much difference between the tools in terms of setup. In terms of usability, Dynatrace makes it easier to get the information that I want.

We've been using AppDynamics alongside New Relic. We had issues finding some problems, so we brought in AppDynamics and were able to dive further in, but after about six months, New Relic traces we're exactly as in-depth and usable. We were pretty confident with New Relic, and brought AppDynamics in to dive deeper, but their interface was Flash, which was slow and not nice.

Everything else about New Relic was nice. We could put different pieces of data in front of the developers, which is nice. They don't have as much information as we do in Ops from our other tools, but they get just the right amount of information to see where the bottlenecks are.

We have switched away from New Relic and have begun to use DataDog.

We didn't previously use a different solution.

There was no solution in place previously.

We've tried various other tools over the years, but after giving New Relic a try, we haven't looked back.

I don't think New Relic has a lot of competition. We also use Linode to monitor our servers (but not our app).

We were previously using nothing else. We were reading through logs trying to interpret our own data, which was challenging. Someone suggested New Relic and we went with it right after; they’re the only player in town for this sort of environment.

I was involved for another account, but it was very straightforward, couldn’t possibly be simpler. So easy.

This is our first APM. We were looking for a solution that helped us to improve our customer experience. It was borne out of database issues we were having at the time. We had no APM solution prior – it was all done manually.

Prior to New Relic, we did not have an APM solution. We had a lot of home-built tools but nothing like this with dashboards. Mainly the maintenance of the home-built tools was difficult. It was tribal knowledge with no documentation, so we were constrained by the engineers and their specific knowledge of the tools.

We knew that we were going to move into SaaS, and these are the kinds of tools we’re going to need to get there.

We didn’t use any other solutions prior to this.

The solution we were using before was cobbled together from a mixture of sources, various monitoring solutions. None of them really offered the visibility of the overall health of the application. They’re all sort of looking at unrelated data points and we were left to infer what was happening.

New Relic understands the common tools you’re using; they had the first player advantage, plus the kind of nailed everything else. When they first released APM for Ruby there was nothing else like it, and there was barely anything else like it for any other tech stack. When they first hit market they were fundamentally different and better.

New Relic “hides” all of the stuff that is less valuable and lets the good stuff bubble up which lets you focus on that rather than anything else. A huge part of it has been the lack of having to do any app configuration to get started.

We didn’t use any other solutions prior to this.

We previously tried some hosted solutions using a variety of tools to perform monitoring and reporting tasks. We decided to switch to New Relic for its simplicity on setup and maintenance. We are able to quickly deploy new servers using New Relic in zero time.

Prior to New Relic, we were using some Oracle tools such as AWR. Although they were useful, they were not really proactive. New Relic is a more proactive tool, as it were.

Our CTO came back from a conference last year and we were trying to solve a problem using DynamoDB, S3 and Redis (trying to solve the user segmentation question and analyze user behavior). Within a few hours of implementing the API, I was able to query for what we needed. You could do a lot with elastic search, but that needs a team of three people.

No.

It was already in production. I did deployments in the staging environment, but not the first deployment. We will be doing the first deployment for mobile as well.

We did not use any other solution.

We have tried different services in the past, which only offered part of the features, but again New Relic is very different - complete product that just works.

New Relic was an add-on to our existing operations analytics systems. We selected New Relic solely on the basis of the application monitoring feature which our existing systems did not provide.

I would just advise you to use the tool.

No previous solution was used.

We used to use Microsoft System Center Operations Manager but this is really not ideal for our cloud-based deployments

I had not used another solution. Others in the company have. Switch was due to feature set, ease of use, and less administrative overhead.

We had several solutions in-house.

This has always been our solution since we started.

We've always used New Relic.

No.

We didn't have a solution in place prior to deploying New Relic.

Cost effectiveness.

We looked into other solutions. SumoLogic does other kinds of log aggregation. Maybe Splunk. LogAnalytics. Rigor is a competitor to their Synthetic.

The closest alternative is AppDynamics and the best part its On-prem module is also available. the support is not as good as the product

New-relic is easy to use and the implementation support is awesome.

No previous solution was in place.

No previous solution used,

No.

Previous experiences with this tool made us choose this first, although we compared others.

The decision was why not to have it (cost?) not why to have it.

There was no previous solution in place and we realise that without it we were flying blind, so we needed it.

Yes, we switched because of the price.

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.

No but we are using Splunk and New Relic along with Stackdriver Simultaneously [Don't want to depend on one and use the features of all].

Yes, I switched because of the low cost