I wouldn't say that the initial setup for New Relic APM is easy, but it's comparable to other tools because of the comprehensive documentation you can use as a guide. My company also has very knowledgeable engineers who set up the tool.

It took about six weeks to deploy New Relic APM completely.

The product is pretty straightforward with every product that is out there - even with Datadog. New data integrations are seamless. The initial setup is pretty simple and straightforward.

I'm not sure how long the deployment takes. 

It's easy to maintain. We integrate it with our CI/CD pipeline, so any changes go through the same process. We don't have a dedicated team to maintain it.

It's not as straightforward a setup as Azure Monitor. Then again, we have admins, and they were managing that part. It's not a big deal.

We have two admins that can handle deployment and maintenance. 

The initial setup isn't complex. I haven't deployed it, but my colleagues say it is easy.

My impression is that the initial setup process is straightforward. The solution is SaaS so all it takes for deployment is just signing up for the service. Our model of deployment is the cloud.

The setup is straightforward. We have complete and concise instructions on enabling the APM on a particular application platform. We work on different application stacks. New Relic has different instructions for different types of technology stacks. We follow their instruction.

For job applications, JAR files need to be installed. The APM provides it. For other applications, we have to put the necessary IP address or domain links on the application. Then, New Relic automatically scans the specified server, and it appears on the New Relic console. The solution is cloud-based.

New Relic is deployed on the cloud. The ease or complexity of deploying the solution depends on the piece that you're deploying. The app pieces are pretty standard when the infrastructure is more complex.

We got professional services from New Relic to help with the setup, and they were very helpful. In 2018, we went with their professional services, and their pricing was better at the time and comparatively lower than Dynatrace's. We were shelling out almost a million dollars per year for Dynatrace, but we saved some money once we moved to New Relic. Their professional services were about 60K when we used their support. I recently moved to a new team after a long time, and we have weekly connects with the New Relic team, and there has been a complete restructuring of the teams. So previously, the professional services were topnotch, but it is not as good now.

It was straightforward. We didn't see any complexity because the setup of New Relic on the client side or the application side is more of the agent configuration.

Once your agents are configured in the pre-prod or production environment, the feed used to be taken automatically. The only thing is you have to open the proxy to the New Relic system. If that is done, the rest is taken care of automatically. I don't see any challenge.

Setup was pretty smooth. I wasn't involved in initial setup, but for newer customers and installations, setup wasn't very cumbersome.

I did not install New Relic. By the time I was put on the project, it had already been installed.

They just let me know the ID and password, and I just logged in, and that was it.

The initial setup of New Relic is easy. I do not have to use the documentation a lot of the time because it has a guided installation method. We have automated a lot of the tasks needed with other tools such as Ansible and ServerNow catalog tasks.

The deployment of 20 or 30 servers without automation would take a lot of time. There are many different agents and components. There are other solutions that are not as difficult, such as Dynatrace. However, they only have one module.

I used to handle the New Relic APM setup process more for algorithms, mainly writing algorithms to define the rules for better tracking. I focused on the time travel, traceability, and other valuable features of the solution, primarily monitoring and not the initial setup for New Relic APM because the IT team took care of that process.

On the part I handled, the process was seamless, and there was nothing complex about it, but it could be because I asked for help from the IT team. The process was average. It wasn't very smooth and wasn't very complex either, so neutral.

The initial setup for New Relic APM, which was done by the IT team, took more than a day.

It's a straightforward setup. It's not overly difficult or complex. 

I'd rate the solution four out of five in terms of ease of setup. 

Mainly the setup was done by the box team, so they were using it for their purposes and for the log activity. I'm just part of testing team, so I'm focusing more on the reporting side. The setup was not done from my end; the DevOps team managed the process.

We have mostly one person handling the setup and it took about two to three weeks.

We have a third party that manages the maintenance. There might be four to five people maintaining everything. 

Other teams handle the installation and configuration for New Relic APM.

The initial setup was straightforward. 

I don't think any of these tools are tools that anyone can pick up and install. 

I wouldn't say it was any more difficult to configure than some of the other solutions. It is definitely not more difficult to configure than AppDynamics. 

It was quite hard to integrate, if you weren't technically skilled. 

A lot of people who consume this product may not be technically skilled, but if you are, it is easy to use. From this perspective, it is really good, but this is an important aspect as well.

The initial setup was done by our London team. I wasn't involved in the process and don't have any real details about how it went. 

I'm not sure if any ongoing maintenance is needed.

The setup is moderate. 

The configuration and installation were good. New Relic has some very good documentation. Everything in their API is some of the best that I have seen. It wasn't without issues because it's a piece of technology, and we had to figure out how to use it, but everything has worked well.

The issues were working through the documentation and figuring out exactly how to implement on some of the technology.

New Relic's deployment was easy. They had good documentation. 

The initial setup is straightforward for this solution.

The solution is straightforward to set up. It's not a complex implementation. They are more compatible on Linux side of things, however. 

They need to provide more documentation for Windows. For example, I was trying the New Relic logs feature yesterday, and they have very good documentation for Linux, and can explain quite well how to do log forwarding on Linux. Then, for Windows, they do not have that specific documentation. I was stuck and I haven't worked on it today due to this lack of documentation. 

From a documentation standpoint, it is pretty straightforward to set up New Relic assets. The infrastructure isn't that complex. To be honest, we haven't been involved in setting it up from an infrastructure setup standpoint. We have more consumers from which we use a setup that has been done to identify bottlenecks.

There's no specific maintenance that's been required unless they've changed endpoints which would need to be configured. It is something that's natural. When we do changes to the application and change endpoints, we'll have to configure the right endpoint. Otherwise, from a maintenance standpoint, given it's cloud and it's a storage medium, it doesn't need any major maintenance activity.

I was not a part of the team for the setup but my impression is that the documentation could have been better. It didn't make much sense. 

For beginners using New Relic, the setup can be difficult and should be simplified. 

We have a DevOps team to maintain this solution, but it doesn't require a lot of maintenance.

The initial setup was straightforward and didn't require much work on the browser configuration. The user administration is also good if there is an existing New Relic account. It allows the restriction of privileges and control of users accessing complete information. In addition, it provides for a bucket of developers, stakeholders and operations and restrictions of certain access to view dashboards or features.

Browser implementation is also simple when an account and servers are added to the New Relic system. Those servers are automatically reflected on the New Relic account, and we don't need to do much. It is straightforward, and once we configure the agent, all our servers are under our account.

Not involved in the initial implementation, but I was involved in agent deploys and bootstrapping data centers. It was super easy.

The setup is easy and plug-ins can be written for any differences required. 

I rate setup a ten out of ten. 

The solution is very simple to set up. I'd rate the entire implementation and deployment experience a five out of five. 

The integration and configuration of this product in our AWS environment needs improvement on the filtering part. I would like it to go more granular on accounts. There is also some room for improvement on the integration with Serverless AWS.

We deployed the agent via simple manual steps or via in-house written scripts.

It was straightforward, but the issue was the unfamiliarity of our IT manager outside the Microsoft world.

It was pretty straightforward. We just put the DLLs into the solutions, make a couple of config changes for New Relic so it detects the name of the product or web app or whatever it’s trying to monitor, and just keep pushing customer attributes or whatever you want. It was very simple. Within 30 minutes you see customer attributes in the environment and it starts capturing.

APM was already in production when I joined the company.

The initial setup was simple, but it can be made easier. I rate it seven out of ten. I did not deploy it a hundred percent because I was testing it out. The solution was deployed on the cloud.

The initial setup of New Relic APM is simple.

We had no problems setting it up as it was very straightforward.

There were no problems.

It is really easy to onboard a new application with New Relic. There are a couple of things to be installed and configured. Overall, it is simple and straightforward and I don't see much of a challenge.

It was quick and simple. Always, whenever we look at a product, including ours, we've got in the back of our heads, what's the mean time to pretty graph? How quick is it to get data in front of you and that's usable? Within minutes we were able to get the information, and the first hour was great with New Relic.

The setup is really straightforward. Install a server agent on the operation system, and install an application agent in the application.

This is a cloud-based solution that doesn't need to be installed.

The initial setup is very straightforward. Deployment took about a week. It doesn't require more than three people to deploy and maintain the solution.

We are using AWS Cloud, and I integrated New Relic with our software, was very simple. It is easy to use the New Relic product, and it is not a hard connection between AWS Cloud and it.

The initial set-up was at the time the most straightforward and easy as imaginable. This really pushed us over the edge of giving it a go and loving it from day one.

I think this is one of the aspects in which New Relic shines. They designed the product to be easy to install and integrate, it's part of their guiding philosophy and probably what made me try it in the first place.

The initial ground level setup was very easy, very intuitive, and went very quickly. Some of the more advanced features did require a lot of review of their documentation and a few support tickets to figure out.

It was already in production, but I have done it in the past elsewhere. It’s so straightforward it’s ridiculous.

Straightforward. It would have been better to have more transparency to understand how New Relic actually slots onto your page, how it fits into your application.

Very straightforward – it was great that everything was packaged so we didn’t have to do too much customization. We changed maybe two lines in the config. The documentation was very straightforward. Once we installed it a couple of times manually, we were able to script it, which was very easy as well.

The installation was simple. We don't need to use a user interface to install it. We can use two or three commands in the PowerShell or three or two commands in the batch. One device can take 10 minutes, and 100 devices can take one hour depending on many factors.

The script takes the information for the device from the system information but if you are using an interface, such as a wizard, you need to modify files and put all the information regarding the devices and environment, such as the license and hostname. All the information should be put in there. It is very easy.

To set up the metrics, you need to build the dashboard and after that, when you add a new device, it's automatically added.

To receive all the metrics for each system regarding its application, the user in the interface for all the dashboards can type the hostname and can see all the tools in that host, it is a very powerful view. You can modify some of the parameters to fit your needs.

Very straightforward. In this day and age, that’s what you expect from a service like that. Being able to set my alerts and the thresholds for those alerts is very intuitive.

It was straightforward. On each of our servers, we installed the agent, added our key to a config, and then within minute we were seeing metrics on our site.

The initial setup is straightforward. It is easy to track and easy to follow. It's somewhat like creating a graph where drag and drop features.

The installation is straightforward, and it only took approximately one month.

The integration and configuration of the product into our AWS environment was extremely easy.

It was easy and we documented all the steps that we took to make it easy for everyone. You need to be a server admin of course to do it, but you don't need much experience to install and run New Relic.

Incredibly straightforward. Procurement is the hard part.

It was straightforward. On each of our servers, we installed the agent, added our key to a config, and then within minutes we were seeing metrics on our site.

New Relic offers great tools to integrate your software stack with their tools, and everything worked like a charm.

I was not involved in the initial setup, but it was done in-house by one person. It took at least half a week to complete it. This included setting up the service, and Slack integration. It took a nice amount of time, in total.

The integration and configuration of this product in our AWS environment was quite easy.

We have it integrated mostly with our physical servers.

We had no problems setting it up.

No complexity. Just an API call.

The integration and configuration was good for our containers and LAN disks.

The integration and configuration of this product in our AWS environment was very easy.

We have plans to integrate with other products going forward.

We have to install an agent on each of our instances.

Very easy -- install the agent and reload the dashboard!

I wasn't involved in the setup.

It was already in production when I joined the company.

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.

It was very simple and took minimal effort and time.

Setting up New Relic is very easy and well documented. It's using the standard operating system packaging tools and is straightforward.

Once we overcame the challenges of implementing the early Java agent, the remainder of the implementation was effortless. We had 90% functionality within the first 12 hours of implementation.

It was already in place when I joined.

I was not involved as it was already set up when I came. At my previous company two years ago, I helped set up, and it was a little bit of a hassle, but it was a different platform (Java). Now it's nodes.

The deployment is easy, and it only takes one minute to install the package at the OS level for a server via RPM, and via agent for different applications where you integrate them in your application. It would be difficult to do make it simpler.

It was peanuts, and you install the agent/plugin on your OS or application, then you start your application or the agent on the OS, and it is automatically integrated in the dashboard on the cloud. It's impressive how it is so simple.

For the integration and configuration of New Relic in our AWS environment, we need to install an agent on all the EC2 instances to get the APM working. Also, it has an IAM user on the AWS Management Console, allowing for AWS metrics and for it to monitor other services.

I wasn't involved in the setup.

Deployment to our Windows, Ubuntu and .Net environments was very straightforward.

I am not an engineer but one of the pros for use of NR is the ease of implementation. Our engineers find it easy to implement this toolset.

Setup was very simple and straightforward.

I wasn't involved.

Very straightforward. Worked through our account manager.

It was already in production when I joined, but rarely used. Our group and our web assets decided to utilize it after a three month evaluation. We did it just for one application, but now have it installed across the board.

I had to read the instruction page but other than that, it's easy.

This was a simple setup. I never received training and I was able to get in to the admin console and set up the dashboards I wanted.

We didn't find the initial setup complex. The implementation was straightforward and simple.

The deployment was pretty quick as well. It might have taken us one to two hours to get everything done.

Very straightforward. I don’t recall how it went, that’s how easy it was.

It was already in production when I joined.

The initial setup was very straightforward.

The documentation is very complete and the procedure itself takes about five minutes, plus deployment time.

Yes, installation of the APM piece and Server piece is straightforward but the plugin may cause an issue.

No, simple setup process.

I wasn't involved in the setup.

So easy, very straightforward. Our developers, at the beginning, created some templates for data they wanted to track and that was it.

The solution was already in production when I got to the company.

It was straightforward.

Straight-forward, though not completely.

Easy.

The complexity of the installation depends on the environment. If the infrastructure is simple then it can discover all of the units in an hour or two. If on the other hand, the environment contains a gateway and a proxy then it might be complicated by having to open the proper ports and establish communication with the cloud portal.

The integration went smoothly with this product.

It was easy.

The setup is quite simple and there are plenty of online resources.

It was quite simple.

Straightforward - NuGet package.

It was a one minute setup and was straightforward.

It was already in the environment when I joined, but I can't imagine that setup would have been anything but straightforward.

Very simple setup.

New Relic APM installation is quite easy and very straightforward.

I wasn't involved in the initial setup.

I wasn’t on the implementation team.

We followed their documentation and it was good enough to set it up.

I wasn't involved in the setup.

I wasn't involved in the setup.

Straightforward