New Relic APM is a scalable tool.

It is scalable. We have a scalable infrastructure. Their API calls and everything help us scale the monitoring and the use of New Relic itself. We scale the solution according to our requirements.

The developers use it to test and look at the logs, and the SRE team uses it for reliability. 

We have another system admins team that reuses it for monitoring of services that are running. Even our stakeholders use it for various dashboards and look at the SLA reports and other stuff. The user base is not very large, yet we have different teams who use New Relic in different ways.

We have a few different teams on the solution right now, including an admins team, and an SRI team, and they depend on this solution very much.

The solution is scalable. It's not a problem to expand as necessary. 

We have two or three users on the product right now. 

I rate New Relic eight out of 10 for scalability. We have around 150 users, including nine or 10 DevOps people acting as admins. 

It is a cloud-based solution, so the platforms automatically scale. 

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

The tool is pretty scalable. We did not have any problem using it on multiple nodes or instances. We have a report server. The report server would have more than two instances. Sometimes, the application node would have more than two instances, one database, and a proxy. The tool can handle 12 or 16 instances at the same time in one single application.

Our largest customers had around 800,000 users. The task of monitoring the tool and identifying the issues depends on the specific assignments that the technical person receives. One person does the deployment and configuration.

It is a very scalable product.

Regarding scalability, we recently extended our contract with New Relic for the next two years.

We never had any challenges because our servers were scaled based on the load. When our load increased, we used to keep adding our servers to New Relic. We didn't see any challenges. It just required the agent configuration on the server. The only thing is that you have to put in more money when you are adding servers.

It was scalable.

We have eight or ten people using the solution at this time. It is used occasionally, once or twice a month, just to pull out the data for the server monitoring and for the reports.

The solution can scale well. 

New Relic is scalable. I have not seen an issue with the scalability. We have over 600 applications and a very high number of users using the solution and there has not ever been a performance issue.

You can scale New Relic APM, but I expected it to be more scalable.

The scalability is good. I'd rate it five out of five. It is easy to expand. 

New Relic APM is a scalable solution.

We have not yet explored the scalability, it's too early for us.

There are approximately 15 of us using it altogether. We are called infrastructure engineers, who are third line infrastructure support and architecture people. 

Some of the lead developers have access, but there are 15 of us and we are all pretty similar.

So far, I haven't hit any scaling issues with them, and the environments that I have come from have thousands of servers being monitored.

The solution scales well. 

The scalability is very good. We have a large real-time environment for processing payments.

Scalability is good. We are using it at an enterprise level and have 20 companies in our corporation.

The solution is scalable.

I've never had an issue with scalability. They have been able to scale and handle everything that we've sent them.

My company has around ten users for the product. 

On a scale from one to ten, with one being low and ten being high, I would give scalability a rating of eight.

The solution is both scalable and fast. We have no complaints about it at all in that regard.

It's multitenant on the cloud which helps make it very easy to expand as needed.

The solution is scalable. The deployment is not done by us; however, when we have to add new services or new components, it is pretty easy. The turnaround is also pretty quick.

Our team just accesses the client's New Relic tool. It's typically just used by performance testers and engineers. It also sometimes gets used by architects as well the development team. From our side, we have three people working on the solution. 

Almost all of the developers are using this solution in our organization. We have approximately 60 users.

It is used on a day-to-day basis.

Scalability is good, and there are no limitations. Once we add our users to our account, they can access it anywhere in the browser. We have never experienced any technical problems.

We have more than 30 users that are already configured in our system. The pricing depends on the number of users we have, and we currently have only about five or ten active users out of the 30. Only our operations team typically accesses the browser.

We have four to five people who maintain and manage the day-to-day operations. They have other tasks at the company and are not dedicated solely to the maintenance of this solution. They monitor how the servers are performing and get alerts to their emails.

We had agents on servers delivering service from 11 different data centers worldwide. We never experienced a problem. Once the agents were installed, we forgot about them. We've never needed any special maintenance or anything. It scaled really well.

The solution is scalable and has been used for both small and big projects that scaled over time with no issues. 

It's a scalable, reliable solution. 

We have 30 to 40 people working on the solution generally.

We run 20 web servers, 500 Lambdas, and 50 DynamoDB tables. We also have an enterprise SQL Server with different instances along with MySQL databases and mobile applications.

Given that New Relic is a SaaS model we haven’t had any negative impact utilizing their UI to view given applications or do analytics with Insights.

It’s scaled for us. We’re still relatively small with just 16 servers.

It is a scalable solution. I rate it eight out of ten.

We have approximately five managers using this solution.

I rate the scalability of New Relic a nine out of ten.

We have found the cloud-based version of this product to be scalable.

The scalability of New Relic APM is good.

There are two types of users, one is the basic user which is free and has limitations. We have approximately 40 basic users. The second type of user is pro which does not have the limitations of the basic user. We have 10 pro users.

There have been no issues with scalability.

I would like more than 1000 views.

Scalability has not been a problem.

I think we're finding more and more ways to use it. Because of plug-ins, we are pushing as much information in front of the app to the developers. I think too many companies end up with too many tools, but with New Relic, we want to keep in front of our developers all the time.

We've not had any issues scaling it. We work with Java, and the agent is easily implemented.

New Relic is a scalable solution. I have between 10 and 15 large customers who use it.

The solution is scalable. We have about 15 people using it currently. They're mostly developers and managers and we all use the product daily.

We haven't seen any issue that affect us personally.

No issues encountered.

It’s been useful as we’ve grown our user base; we haven’t had any scalability issues. We’ve done tens of thousands rather than tens of millions of transactions.

It’s scaled to all our needs. We have apps for on-site and in-cloud, and it’s worked well for both. There’s no problem with scalability.

We use the APM scalability tools; more so in the past. Now we’re in the cloud we can see how the stack performs. We use some of the graphing to see at what point we’ll hit bottlenecks, and the in-depth reporting to identify weak points.

No problem at all.

It’s a very scalable solution. We have it on maybe a couple of hundred hosts today. We use an automation tool, Puppet, so we’re able to quickly install the New Relic agent across classes of servers easily. On their end as well, they’re collecting more data, so it seems like they’re scaling out very well too. There are no performance issues with scale.

The solution is scalable, and it is easy because all the documentation is available.

There were approximately 11 people using this solution in my organization.

Very extensible. Support and QA can look at the parts they care about and that allows for feedback and communication across the teams. It’s been great for our support team.

It's scaled for our needs. We haven't had any issues with scalability.

It’s scaled to all our needs. We have apps for on-site and in-cloud, and it’s worked well for both.

No issues encountered.

The scalability is good but can be improved.

The solution is scalable. We had a lot of infrastructure at the beginning and it worked well.

Size of the environment is 30 VMs which are instrumented with New Relic. 

I haven't had any scaling problems with it.

The solution is very sclable.

It's been able to scale for our needs.

Again, no problems, but I've never run it at a site that is truly a top-100 site. We know there is some overhead, but nothing Google-scale.

The cost of the solution is high on a per-node licensing scheme and that’s the prohibitive factor, but in terms of the actual scalability there are no issues.

The licensing fee for a single node can be comparable in price to running that node, certainly in the modern cloud world.

No issues encountered.

No, our website started with a small number of users and grew to hundreds. New Relic was always working as expected.

The scalability of New Relic APM is good. We have not had any issue with scalability when we use different types of loads, it worked very well.

The scalability is good. We have a few thousand servers, and it is up and down based on the traffic and need. We have New Relic on all of our servers.

Scaling has not been a problem.

It’s built to stay up. We starting sending a ton of data to them. They were able to deal with it on their end given their internal architecture. We had a marketing partnership with them.

The scalability is good because it is SaaS.

The scalability is good, because it is already running on AWS.

Our environment has 25 servers.

No.

It hasn’t scaled quite right now. We use another tool for out-of-gate view. Currently, we manage about 60,000 servers in total and we don’t have a good roll-up view of the entire system. The application on the server side is OK. We use other tools to monitor the environment.

Our use doesn’t really push the limits of New Relic, but it looks like it will scale just fine.

We have scaled up as well in terms of number of hosts. There is some perceivable difference in performance when you’re looking at a graph versus number of hosts, but so far it has been fine. It’s definitely not the same looking at a single host versus many hosts.

There were no issues with scalability.

None so far. However, the amount of servers and services connected is limited.

No issues encountered.

It scales, and I can't speak about this, but we are moving everything to AWS and it should be fine.

It's scalable, but it comes with a price.

No issues encountered.

We never had any issue with scalability. It is perfect. It currently monitors about 150 EC2 instances and several AWS services.

We are using APM to use capacity planning, and the info we get has been able to help us.

It’s been scaling along with our growth.

It’s been scaling along with our growth.

It’s been scaling along with our growth.

Haven't encountered as issues with scalability.

None

We've found the scaling to be good. If a company needs to expand it, it should be able to do so without any problems.

Currently, we have four or five people using the solution. Our company, however, works for my customers, and therefore we have a lot of ongoing projects.

We’ve been able to brainlessly scale.

There have been issues, but I do wonder whether we’ll have to tailor the user experience and whether we’ll reach bottlenecks with individual clients sending events up to the cloud.

It’s scalable – thumbs up. We turn on new servers and New Relic just works.

Super scalable. For us it scales for what we need. Scale means does it work as well if you have three nodes or 500, and it does. It doesn't break when you scale it up.

It's trivial.

No issues encountered.

No issues yet.

No issues with scalability.

We’ve been able to scale without issue. We’ve installed it and it works.

No problems.

No issues encountered.

Yes, sometimes.

No issues. It’s expected since they’re cloud based.

No.

We haven't faced any scalability issues.

We've had no issues with scalability.

It scaled well, as we just need to add a new agent onto the box when we add a server. Also, it's been helpful in determining when we need to scale up by looking at the metrics.

We're moving our infrastructure to AWS, as they are integrated with it.

The agents are updated quite frequently, but New Relic doesn't offer tools for doing the upgrade in large environments.

No issues encountered.

No issues with scalability.

No, didn't notice any scalability issues.

None. Our servers were small any which ways.

It seems scalable enough. We are always hitting the limit of the number of agents that we have, then we buy more and it works.

Seems to be pretty good on scalability and it’s easy to install into our applications.

Also good, no worries. Baked into the code a deploy time.

No issues.

I don't have any issues with the scalability of either New Relic or Dynatrace. They are both quite scalable.

No issues encountered with scalability.

Our stack is fixed, so we only scale within the set number of servers.

No issues encountered.

No performance issues when scaling. We don’t need to care about scaling it as it monitors our system. You just put an agent in the server and New Relic takes care of the scaling to provide you with the data.

We don't have much experience with scaling it, but we've been able to scale to a mobile platform.

It's no problem, we’ve gone through adding services and have had no issue scaling.

I haven't experienced any issues with scalability.