For our deployment, we did the first 40 in less than an hour. That required a part of one guy, and he maintains it all now. We have close to 200 nodes with OneAgent on them and four ActiveGates, synthetic monitoring, and plugins for MQ and Citrix, among other things. That takes three-fourths of a person on my team. I've federated the support for a lot of the stuff on our portal side. Our portal team developers fell in love with it so much that I just let them run with it and install it as needed. I give them more and more administrative rights. If you add their time, it works out to the equivalent of about a person.

We have close to 100 users. Some of them are just management who use the reports. Some of them are the portal team who are administrators, just like my team, and the majority are in IT. We're starting to take it out to our sales organization, as they're interested in the response time and other things.

I would say that five years ago when we did the initial setup, we had some issues. However, I think that this process has changed since then.

The initial setup is straightforward. You just install it, then automatically put it on. We did this in one big bang overnight, taking probably five hours.

The initial setup and implementation are almost too easy. With real-user monitoring and all the application monitoring, you are introducing change into the environment. It is so easy to set up, configure, and implement that you can get way ahead of your organization technically from where they are from a usability standpoint. We have run into virtually no technical limitations in implementing the product. It has purely been from the ability to get users to adapt, understand, and leverage the value of the product.

We implemented and installed the Dynatrace platform (and everything) within a couple of days. We deployed the product in certain environments within overnight of instrumentation. Onboarding of teams and the training required, that took months. Even though we were able to technically implement the product from non-production into production within a month of deploying everything, having it there, and instrumented. It took us another eight to nine months to onboard individual teams into adopting and leveraging the product. From there, the rolling out is really limited more by organizational change, communication, and facilitating training with teams and their technical capabilities. Key teams have adopted the product and used it very quickly. Therefore, we are seeing value within four weeks of deployment from our centralized critical incident teams, but the product adoption from application and development teams has lagged.

If you are implementing Dynatrace, the first thing is to not underestimate your users and their experience, providing them personal service to onboard and consume the information, then leverage the product on the front-end. Technically the product makes it so easy to implement and deploy, this makes it difficult to stay in front of the rest of the organization when adopting the product. You need to ensure the data starts presenting itself before they are ready and able to consume it. You need to focus that into your implementation.

I rate the ease of setup a seven out of ten.

The setup is really not much different, whether you're an on-prem organization or a cloud or even a hybrid. It's still the one agent. I have no experience with their AppMon product, so I can't tell you how much easier the new product is versus the old. But I can tell you that this product that we have been using is the easiest thing we've ever had. The only comment I got from my systems team is, "Why didn't we get this sooner?"

I am not the norm when it comes to policy and procedure. I tend to buck the trends a little bit. If I have a new product that I feel is going to be advantageous to the company and my team as a whole, then once we've done our due diligence, we will just deploy it. I know that larger companies with different criteria and regulations have to follow different channels and paths, through security and infrastructure and storage, etc. But ultimately, as long as you have "air-cover," and by that I mean an executive sponsor who believes in what you're doing, then you really should be able to get it done with minimal effort.

We were fully up and running in a week. It took me longer to remove New Relic than it did to deploy Dynatrace. We only needed one person to deploy Dynatrace. One of my systems people took care of it. I took care of the administrative stuff, creating the initial dashboards and getting the payments set up and so forth, but my systems people took care of the actual deployment of the one agent.

The initial setup is actually really easy to install. It's a quick process. You can turn it on and load the SaaS Dynatrace solution in just five minutes. 

However, there is additional configuration and tweaking that may take years to optimize fully. The interface configuration is not easy; given the tool's complexity, it requires time to become familiar with it.

There is maintenance involved. Dynatrace releases patches every two to four weeks. The only painful part there is the agents we run on-prem and on our servers, it needs the agent the application needs to restart.

So, sometimes you delay the update to minimize disruption but the patches are sent to us every month.

From the infrastructure perspective, what we have installed is the user agent on our API servers. So, we have six API servers set up in an Azure load balancing pool. There are three active at any given time. It was super neat when we installed the agent, because we actually went out and had lunch after the installation. When we came back, Dynatrace had generated the Smartscape view of not just the API and the different services they connect to, but it had crawled our entire network and found everything that it recognized from SQL Server databases to .NET Servers and API services. All of that stuff showed up in a sidenav automatically without our having hands on anything whatsoever. It provides a good quick view in the morning when you come in and just flip to that view right away, because it will flash in "red" for any given service or platform that is having a problem, then you can zoom to that problem and look into it right away.

The setup is very straightforward and it is easy to onboard. 

I rate setup an eight out of ten. 

The initial setup is straightforward. I'll be up and monitoring in four hours. The on-premises installation was a little more difficult due to network firewalls and so on. Overall, it went well.

This solution can be deployed and maintained by four people.

We started with AppMon, which was more of an on-premise version, where we were installing it, although it still was a one-agent. Then we moved to the SaaS solution, and it was very easy for us to migrate from AppMon to the SaaS solution, and it's been extremely easy to instrument new hosts with the agent.

We were up and running within 30 days when we were first engaged with AppMon. When we migrated to the SaaS solution, it maybe took another 30 days and might have even been less. I wasn't involved with that migration, but I worked closely with the guy who was. I don't remember it taking much longer than 30 days to migrate.

We had an implementation strategy. We knew specifically which application we wanted to monitor, and all of the hardware and services and APIs that that application was dependent on. We went in with a strategy to make sure that all of those things were monitored. And now we've progressed that strategy to start monitoring more of our internal back-end systems as well — the systems that support our stores, not just our e-commerce channel — to see if we can't get more value and maybe even realize more cost savings on our brick and mortar side using Dynatrace.

The initial setup of the product is a relatively easy process since it is a SaaS-based platform. Previously, with Dynatrace, my company had it deployed on an on-premises model. Currently, when my company deals with the setup processes of the product, it is really easy since you just install the agents on your server or on your hosts, after which the product starts to do what it needs to do, and then you can just create your dashboards and alert systems. If you understand the application, the setup phase is a really simple process.

The solution's deployment and maintenance processes are handled by a team consisting of four members for both South Africa and the UK, and they also readily function as a support team. In terms of deployment and product administration, you can know how to utilize the tool from a much broader base.

It is pretty easy to integrate it into the AWS environment. You give it a username and password and it asks some basic permission. It can pull a lot of information very quickly. We are able to correlate more and provide more data for it. So, it was easy to integrate it into that environment.

We have it running on AWS. It integrates pretty well there. We have it on Red Hat Linux servers, as well as Windows servers. We have it running on VMware where it integrates very well. It understands these productions and understands our platform. It is able to read into Docker containers and all the databases that we run. However, it is limited as far as how many of a certain type of database that we can have, but for the most part, it runs pretty well and integrates very well.

I was not involved with the initial setup. But since I've been there we've upgraded from 6.3 and 6.5, and we're currently rolling out, I'd say, 90% of our environment is at 7, we're just missing one server. I would say the upgrading is fairly straightforward. It was just a lot of work, due to the size of our environment.

The initial setup was straightforward.

It is easy to get the basics, but more complex when you want more complex metrics and dashboards. E.g., we mapped IP addresses so we knew which corporate campus end users were connecting through it.

I was only loosely involved in the initial setup. At the time we brought Dynatrace in, it was one of my peers in the same larger group that was doing the evaluation. I was in the background, watching it. I then ended up inheriting the whole thing about a year later, so it was kind of good that I did have some visibility into it.

Overall, the initial setup was pretty straightforward.

The deployment process was easy as the vendor just had to give us access.

Setup is very easy, and it's easy to implement. I would rate setup 5 out of 5.

Since I'm representing different use cases and different customers, we see different needs. For all of them, including having a SaaS-based approach or having on-prem deployment, it's always a matter of minutes to get some results. The amount of servers is always changing. But we are mostly targeting SaaS customers who have hundreds or thousands of servers for their application stack.

I'm the business development manager and also the pre-sales of the solution in our company. I'm mostly doing the POCs and also leading the implementation since it's very easy. Mostly, I'm in front of our sales and also including the implementation timeframe as the customer success manager for the customers. 

The amount of people needed for deployment and maintenance depends on the size of your environment. If your environment is not up-to-date, your environment is not handled by the operations team. This is not the case for Dynatrace.

The initial setup is very straightforward. It's nice and easy. A company shouldn't have any issues with the implementation process.

While it depends on the use case, in four to six hours we can typically do a deployment.

Typically, staff or three or four resources is enough in order to handle the deployment and maintenance of Dynatrace.

The feedback that I get from people is that the initial setup was very straightforward and easy. It was amazing what information we got in such little time after deploying the agent.

In most cases, the deployment is quick. It takes a couple of hours.

For high-risk applications, which are business critical or high complexity, we would deploy Dynatrace. For medium-risk applications, we would consider using Dynatrace. It comes down to cost qualification for medium-risk applications.

It is very easy to use and set up. It did take some customization to get it working for our sites, but after that, it's been pretty easy and straightforward.

The initial setup is complicated, but it's much less complicated than similar systems that I have used in the past. For Dynatrace's setup, maybe there were problems with how our web application was initially developed before I joined Rack Room, because there were a lot of features related to error reporting. It would report errors for things that weren't actual problems, etc. You have to configure it to get around those types of problems, but it's usually fine afterwards.

Over the past year, we've been tweaking Dynatrace. It's been a slow phase-in rollout as far as how much we rely on the data it's giving us back. 

The initial setup for Dynatrace was easy, though it was the client who installed it, and I only accessed the URL. Deploying the tool took two to three hours.

Dynatrace is easy to deploy. It won't take more than two minutes to deploy one agent, but getting approval, summarizing the changes, and the change request concerning the service ticket getting approved is what's taking longer.

In my experience, the initial setup has been straightforward, but I've done it a few times. When I compare it to tools like Nagios, Zabbix, Grafana, and Prometheus, it is very straightforward. This is largely for two reasons.

First, they're not SaaS applications, whereas Dynatrace is, and second, the amount of backend configuration you have to do in preparation for those tools is much higher. That said, if we were to switch to Dynatrace Managed rather than Dynatrace SaaS, I imagine that the level of complexity for Dynatrace would rise significantly. As such, my answer is biased towards Dynatrace SaaS.

I was only pointing at people to do the initial setup. I don't come from the technical side, I just run the teams that do the stuff, the proper work. So I was involved in terms of helping to make sure it happens, but not at the level of touching it.

The deployment process is better than with AppDynamic. It requires one, knowledgable agent to handle the set up.

We kind of grew into Dynatrace. Our initial scope was quite small, so it was not that complex. Currently, our scope is a lot broader, but it is not complex for us because we have been working with the tool for such a long time. Overall, it's quite straightforward. If you're starting with this product from scratch and you have to find out everything, it can take some time to learn the product. But it's quite straightforward.

We started with the AppMon tool, which was the predecessor to the current tool. Implementing that went quite fast because it was a very small scope. When we changed to the Dynatrace Managed it took us half a year. And that's not including the contract negotiations. That was for the actual implementation: Finding out all business cases and all the use cases that we had, transforming them into the new tool, and launching it live for a big part of our company. That took half a year.

I think one of the vendors helped us. We didn’t have any hands-on, but I think we did some Dynatrace University, we’ve been through some videos. And the vendor gave us some training, so we’re fine with that.

There's always a learning curve in anything, thereafter things are fluid and you rely less and less on support.

Its deployment is really easy. It is one of the most easily deployed monitoring products.

Its maintenance is minimal. I worked with competitive products for more than 15 years. So, I can compare them. With Dynatrace, one agent is required. From time to time, there are issues that are typically very specific to the monitored environment. We have customers who have been using all the updates of all the agents for five years, and they have had no issues. Typically, when we have an issue in one of our environments, it is tied to the monitored application platform. We had no issues with Dynatrace.

I wasn't actually involved in the deployment itself. It was a case of just coming in and seeing it was available for various use cases.

However, looking back, it's a relatively straightforward process. It's often as simple as installing an agent with your deployment, and it takes off from there. My understanding is the deployment was very seamless and quite quick.

There's definitely a maintenance contract with it. It's a case where you subscribe to it, and they provide regular updates. You've actually subscribed to a service and there's regular maintenance happening organically.

I was not involved in the initial setup at my current company, but I was at a previous company.

For upgrading at my current company, that is in process. We are trying to figure out if it is better to blast it across the organization. We have five Dynatrace servers. They are all completely at capacity. They are all set at large. It is a really big deal for us to try to switch anything over. Right now, we are trying to figure out, do we just upgrade our collectors and hope for the best, or do we do it in QA and then in production? 

A lot of people do not run the right thing in QA. It is never the case that their QA is identical to production. So, is that a good indication? I have run into issues before when upgrading from 5.6 to 6.1 expecting that all the bugs were ironed out. That is when I took down that application. Now, I do not have confidence in this upgrade process.

For the Dynatrace Managed version, that setup process was incredibly easy. It took 15 minutes. 

I was hands on in the setup of the solution. Initially, it seemed a little daunting. Once we started working with it, it was a very easy solution to implement and put in place.

Dynatrace has so many different tools, so some of them are a bit complex, like AppMon. However, your OneAgent, your browser plugin, and so on are pretty simple setups. 

Initial setup is simple but it depends. In the server monitoring, it's only install and discovery. That is very quick. To install with a cloud like OpenShift, it requires some Sandcastle configuration about tokens and operators, but with old data, it's fast.

It was a straightforward installation.

It took two to three days to configure and do the proof of concept.

We had a team of two or three to deploy this solution.

I was involved in the initial setup, but I have done it before. I have done it on multiple different sites so probably done three stand ups so far: two at the prior company and one at this one. It is not bad. It was easiest with this company, because this company had a level of technical maturity that was not available in the other ones. If you have companies that are doing things like continuous delivery, having built pipelines and having the ability to do these things, it is a little bit easier. I have a feeling that the companies that are more technically challenged, the initial setup is going to be a little bit harder. 

Our main problems were around security and network, but those are hurdles that almost everybody has got to get over and build. It was not bad.

I wasn't involved directly in the setup. I oversaw the project that did. It didn't seem complicated, but honestly I can't say for sure.

We have an infrastructure group and I'm more on the business-unit side, but I was part of our PoC as we brought it in, and stood it up. Generally, it was very easy to get it set up and get going very quickly. It was pretty easy. We used some of the Dynatrace sales team and the engineers to help us get it set up, but in short order, we had it going.

Fairly complicated, but it is an in-depth product.

It was simple to implement.

The solution is very easy to implement and easy to administer. It's not overly complex.

Its installation is extremely easy. You just install an agent on the server. You can just follow the default installation. As long as you've got your system set up and your architecture set up to connect those agents into your Dynatrace cluster, everything is done within minutes.

I'm just a supervisor, so I sat with our technician during setup. I didn't do any of the actual work, but it seems seamless. It installed in about two minutes. I really wanted to see it. I have to go to the assistant director and, eventually, the director and try to explain why I think we need the new technology.

I was not involved in the initial setup or upgrades.

I helped my administration to do the initial setup. It was very easy.

I rate the product's deployment a ten out of ten. The installation and deployment process is brief, but configuring the entire environment, including the agent server and enterprise configuration, is more complex and time-consuming.

The initial setup was straightforward. We looked into Dynatrace and were able to roll it out to 12,000 hosts within four weeks. 

From the Managed version, you can have it installed and up and running in less than an hour. This is on the condition that you have the hardware to install it on and access to the systems/services that you want to monitor.

Initially, some people were skeptical about the one agent really working, so we did test it. Now, we have had so many good experiences that when we deploy, build new services, or spin up new instances, Dynatrace is one of the first things that is always there. We don't even even test the agents anymore. We completely rely on this mature product that is solid and stable when we deploy staging, development, QA environments, or playgrounds. There is no deployment without Dynatrace agents.

I was involved when we initially went through the PoC, worked with our sales engineer, and brought the product in. I'm on the business side of things, so not necessarily the configuration of the server, the deployment of the agents, but really the configuration aspect that we need to gain the visibility into our applications.

I don't have any complaints about the installation process. We were able to get it ramped up really quickly. From where we started, the scale that we went to in just a couple, three months, was really impressive to me.

I was not at the company three years ago for the initial setup.

I am in the development. We just instrumented it on my servers. 

We had major issues, and it was not Dynatrace. It was how Dynatrace and Voz garbage collection were interacting, so IBM got involved and had to upgrade us. Now, it is doing a real good job, but that is how I got pulled into Dynatrace. 

Initial setup is straightforward. I have stood it up at multiple companies. I did it at Verizon Wireless, PNC, and Merck Pharmaceuticals. I knew what to do, so it was easy. 

The initial setup was straightforward, very easy and nice. 

The initial setup is straightforward, although it depends on whether the application enrollment is heterogeneous or complex. The initial planning can take some time but the actual installation and setup is not a big process.

The number of staff required for deployment depends on how many applications we're going to configure. If it's only a few applications then you don't need many people. However, if a customer tells us they have a hundred applications that need to be installed in a month's time then obviously, we need more people to help with the deployment.

The initial setup was extremely straightforward and fast. The deployment function was also super fast, typically just a few hours at most, with the right tuning.

I was involved in one of the very first implementations, but I did rely on an infrastructure team that did the physical installation and acquisition of virtual servers, as far as the agents and the nodes. I was physically involved on a team that wrote one of the very first dashboards. This is three to four years ago. It was more about just learning the product, frankly. I look back now and I can close both eyes now. At that time, it took some time getting used to it, but I would not call it overly complex.

There may have been minor things, but that was more our own people trying to understand it. We may have had it, such as, "Let's install this agent on this server," then it didn't work. Then, "Oops." You have to back it out, then three days later, put it back in. A lot of that is teething. I do not see that as a product limitation. It is just sometimes you don't necessarily know what you don't know and kick the tires a couple times. Now, whether the product could have maybe been a little easier? It's hard to say in hindsight.

I don't want to bring up Apple, but you can think of the Apple example. Apple has this idea that you just take it out-of-the-box and turn it on. That's it. That's your extent of configuration. Dynatrace isn't quite like that, but probably for a reason, because the idea that it could just work as is doesn't make sense, because the individual customer environments are just so different. You couldn't possibly have one-size-fits-all. It is almost impossible.

I was not involved right at the beginning. It was not complex at all. We had the Dynatrace agent helping us in person with the issues.

The initial setup was straightforward.

The capacity planning was complex. Everything else was easy.

Our infrastructure setup has been there for quite a long time, then we already had JVMs who monitor our process. We needed to evaluate what options and what benefits were coming down on our plate, then what was a repetitive task which was already being done by other JVMs. We had to evaluate those on different boxes, different portfolios, etc. Then evaluating options were a little tough because we were already using some things and we had to do something new basically from scratch again. This took some time. After we had experience with the first three major applications, we knew what to do with the next 21. 

I was involved in the initial proof of concept, and setting up of the solution. The solution is very straightforward. Setting it up, and then getting it implemented, and then adoption are really complex.

We had our own shortcomings on the technology side. At the same time, I also felt like even Dynatrace has to mature in its offering. They are in the industry as an APM leader, so they should be able to come and say, "Hey, if you are in this vertical, these are the industry best practices. If you follow this, this would be the right path." 

I think that's something Dynatrace has to evolve. Rather than just concentrating on the solution side, they should focus more on the business side. For example, they should say, "For your retail, this is how your application performance monitoring happens. If you're in the manufacturing industrial segment, this is how the application performance monitoring happens, these are the key metrics you should look for."

The initial setup was very straightforward.

The initial setup isn't too straightforward. It's rather complex.

With Dynatrace, the installation and setup were a piece of cake. It could be accomplished usually within fifteen minutes, and definitely, within a half hour of deciding to do it. 

A big difference that we found between the two vendor is in setting the system up and getting them ready for production. With the latest version of Dynatrace, it took three days and we had it in production. We are still trying to get AppDynamics in production since last May.

I think with anything that's of a massive scale, there are complexities - even just trying to understand the product. Obviously it's a new product and you're trying to architect something you don't know. There are definitely challenges and hiccups that occur with that.

I think, overall, the implementation of actually installing was fairly easy. Most of the problems, really, were organizational problems on our end. You know, change-windows being very small, and the testing requirements that we've put in place, caused the implementation to take a while. But the tool itself was pretty easy to implement.

It was straightforward.

I was not involved in the initial setup. But I can imagine it was complex due to the high learning curve. There was also some complexity in the adoption rate of it because of how costly the licensing is. So getting application teams to spend the money to use it, I think was one of the biggest hurdles.

I was not directly involved but the complexity was more to do with our own environment than the vendor/tool, and the amount, and placement, of servers needed to support the Dynatrace components.

It was straightforward. The full deployment probably took a week.

I have only installed the basics. I know that it is easier than it was in the past, but it hasn't been that great.

The initial setup was really easy. We had the first testing environment in just two days. We tested how the agents work, and it was easy.

The integration and configuration of this product were very easy.

It works quickly with all of our servers, databases, and load balancers. We are now testing it in AWS with AWS features.

The initial setup started a year before I joined the team. I have been involved in the upgrade processes and they were straightforward.

I'm the primary Dynatrace admin, if you want to call me that, and it was pretty easy. But keep in mind, my skill sets are probably unique in the sense that I understand applications well, so I know how to insert the agent - because we use AppMon - how we insert agent into JVM.

But I believe the new Dynatrace product is probably the way to go, because you don't need to actually talk to the application folks, you just deploy it on the host and you're done. I believe it's definitely going in the right direction. It is complex, it wasn't for me, but I can imagine it being complex for some people.

It took a lot of time with the initial deployment, of the old solution, the AppMon. With this one we have to check it out. We are doing a PoC. The deployment is going to be smooth and it’s going to be quick, that’s what I hear, here at the Performance 2018 conference. I have yet to implement the install to see that.

The vendor team who did the setup was very good. They sent a very skillful resource for the setup. However, with the BizTalk side of it, they were less effective as they were with Hybris Commerce.

The initial setup was straightforward. The OneAgent technology does a brilliant job of simplifying what was earlier one of the pain points in enterprise monitoring.

There is absolutely no configuration that you need from any technical person. Our engineers are very junior, and they don't really know how to configure an agent or play with the configuration file. They're not familiar with that. We just deployed the agents, and these agents went and detected which is the application server, where are the logs, and what are the processes. 

Our environment is very complicated anyway, so the initial setup was a bit of a struggle, but only because we have so many applications and JVMs that we have been working on for long time. We had to move everything from CA APM to Dynatrace, so it was a big conversion process.

The initial setup went smoothly and it was straightforward. Though, my colleagues did the setup.

With nothing more than three commands, or a simple Docker container, we had everything running in minutes. Within one week, we had enough customizations to be production ready.

As mentioned before, we are a small startup. Implementing Dynatrace was a no-brainer. It would have taken us at least two months and hiring another SysOps person to get logging, monitoring, alerting, and APM implemented with cheaper or free open source solutions. It was far cheaper and faster to go with Dynatrace.

The implementation requires a few hours to make connectivity. New Relic is simpler to set up then Dynatrace.

The initial setup is quite easy. 

We have had several deployments that have been fast and on-premises. After the setup, it can almost be immediately used. 

The on-premises version can take up to three days.

I wasn't involved in the initial setup, but since then we've upgraded so many times. The upgrade is pretty easy. Complexity comes in when you have to schedule things. If I have a DevOps team that's in prod, once we were able to actually cookie cut the upgrade process, it was easier.

It also depends on the different platforms you're dealing with. You're dealing with Windows versus Linux, and you have to inject code into certain places, that's an issue. 

I'm glad when Dynatrace says they have a different agent, because I wasn't crazy about the agent, the way we were deploying it. Not only me, but you have people who are quite protective of their code, and if you've got to inject an agent, they're not really comfortable with that. But with the new agent, that makes it easier for me too. That's another reason I was happy, that's one of the things I asked about: How are we doing the agent? Even though we were automated, there were still some configurations. But with this new product, it seems like deploying agents is going to be awesome.

Initial setup was very straightforward.

I was involved from the PoC to the setup, then roll out. I am not an admin, but I was part of all it.

It was pretty easy. Our middleware architect, he had no problems with it. We rolled out all our environments (QA and prod) in about three months.

It's a pretty straightforward setup. Once you've got your build out, you don't have to move things around too much, it's pretty straightforward. We did it on our own and then, for our first upgrades, we had support in there.

It is straightforward. The agents are pretty straightforward to set up. I would rate it a four out of five in terms of ease.

Dynatrace is quite easy to install. For an SaaS deployment, the customer can practically use it within the same day. If it's on-premise, I think it takes around three days, depending on the complexity. 

We have five customers using Dynatrace and the team size for deployment depends on the complexity. We have one customer with a big project, which was big in scope as well, so we can have as many as six to seven people for deployment. It ranges, so if a customer has a hundred servers—in terms of the time and resources required for the deployment, from start to finish—I think it could be done within a month by two people. It depends on the complexity. 

The integration and configuration of this product in our AWS environment is pretty seamless and easy to configure.

We don't really integrate it with anything else.

The initial setup was a bit technical. 

I was the architect, I designed from the very start. In terms of the setup, initially there was a little bit of a learning curve, but now, because the tool has been simplified, I think this learning curve is gone.

When you adapt a new tool, obviously the people and culture need to adopt it, so it will definitely be a challenge. We found it was quite challenging in terms of the learning curve. But now, after two or three years, it is quite mature.

I was not involved in the set up of the app. I remember they were doing it manually. They installed the agent, set up the server manually, on each server. So when I came in, we used Jenkins to write a script to automatically deploy to our server. There is still a lot of manual configuration. It's not straightforward.

It was not straightforward. Documentation is slightly in error as far as directory set ups and guidance. We came to our own solution for distributing the disk loads. However, there were two or three different components that worked off the same pathings. A couple of the teams were not aware that when people went outside a stock installation that their assumptions were incorrect across components, and they had to resolve some documentation issues. 

I think it was really, really straightforward. It's the second time around. Some of the things, we did them ourselves.

Set it up myself. It took 20 minutes. Put a piece of hardware in, run two scripts, done.

We ran into a bit of a technical issue where we had to engage the support guys. They identified the issue, fixed the scripts, and then the people after us didn't have to deal with it. I think we were one of the first Managed on-prem implementations; maybe, not the first, but one of the few. So we weren't doing a normal implantation I guess, so little hiccups, but they were quickly resolved.

It was very straightforward. We deployed it on our own.

The AppMon 6.5 is problematic in configuring. It is little finicky. When we configured the JVM, it did not work. 

Sometimes, people are making mistakes, typos, or even if you just sit down you need to be in the light, either in the beginning or in the end. So, this is always a little problematic for us. The issue is not super small, but it is okay.

I was not involved from the first phase. I got involved only in the middle of the project, so I really can't comment on this. But from when I got involved, I think it has been pretty good. I would have to ask colleagues who did the other parts to check how they were.

The deployment was simple, as well as the upgrade.

The first upgrade was little bit complex because you have a data you need to maintain. With an initial deployment, you are starting from scratch and have nothing to worry about. When you upgrade, you need to plan well in advance what you want see.

We needed to do see what was intact, because when we moved from 6.1 to 6.3, the migration tool that they had, it was not quite solid or sound. Now, they have a good migration tool whatever they developed.

The challenges that we face were not that big just minor challenges, since we did a PoC with the tool. Therefore, we could migrate easily with minimal impact on the end user.

I was involved in the initial setup. The funny is that I worked at Royal in 2014. I implemented the initial - we call it the "legacy" - Dynatrace environment, which is version 6.3. I did that implementation and then I left and went to work at Carnival, hated it there, and then came back to Royal Caribbean and then implemented the new version of Dynatrace.

Setting up the new Dynatrace was different because I was used to the level of complexity. One thing I’ve noticed is that everybody complains about the level of complexity with Dynatrace. Even with the surveys, what I said is, you have to know your infrastructure. That’s one of the things that Dynatrace really forces you to learn and know. They’re a monitoring company. They don’t know how we’ve written our applications, they don’t know how we’ve implemented our microservices, they don’t know what connections we have going into our database. We have to know those things in order to be successful with the set up.

Once you know those things... We’ve automated the entire install practice and we’ve automated the entire implementation process. That’s simply a matter of us or me saying, "Okay, we need architecture diagrams, we need service workflows." I need to know how these calls are being made so that way I can correlate them, and I can write the scripts to do the implementation and then we can get it done.

We are partially enrolled, but I have not done it 100%. Next week, I am setting up a lab environment in my organization. Then, I will be doing it completely.

Coming up from the OneAgent side deployment, it is basically a daily job and a 100% improvement. It is a lot better improvement from the agent side. Earlier, it used to be every tiny agent for each aspect.

Straightforward. We did it in-house.

It was pretty straightforward and quick. I was amazed by it. I deployed it in six servers in 40 minutes, and that is pretty good.

I was not involved, but did a comprehensive overhaul, and it was complex. The relationship between tests you create and those that you run is hazy. It’s not very apparent and there’s a disconnect. The configuration components are unclear.

The initial setup has improved over the years and is now quite straightforward. There's a lot of work involved to customize the entire environment.

Never seen anything so complex be so simple to install.

The initial setup was very straightforward, as it is a SaaS solution.

The initial setup was challenging for us. Initially, when we heard about Dynatrace, we knew why it was so good. However, it was complex until you grasped the nuances of the product and the building blocks: what makes what,  from where you can derive what, thresholds, goals, measures, etc. It took time for my team and me to get a grasp of what things are, so now we know what at least we have and have a good handle on it. Therefore, it is easier for us, so whenever there is a challenge, we have an idea of how to handle it. 

I was not involved in the initial setup, though I was involved with upgrades.

We're using Dynatrace Managed. Because of donor privacy concerns, the client wanted us to create our own on-premise, in our on private cloud, meaning a private tenant in a public cloud. We set up our own Dynatrace instance and completely managed by Dynatrace so we never touch it. We patched it due to some of those vulnerabilities, but other than that it's been really seamless for us.

The initial setup was straightforward. The documentation and the university helped on Dynatrace. 

It was complicated in the sense of teaching the support team how to do this because they were new. But once we showed them how to put the agents and how to administrate it, then it was easy for the ops team to take care of supporting, administrating, and putting all the applications into one stack.

I wasn't too directly involved. I worked with the team that was doing the setup, but I think it was pretty straightforward. It was pretty quick, actually. Without doing much, just installing the agents, it gives you so much automatic capability. And then you can always tweak that and configure that and make it better. But, right out of the box, I think it's really easy to install.

I was not involved in the Dynatrace initial setup. For the upgrade, we put it in, and it was done. It was not complex.

 The initial setup was difficult.

Easy.

The integration and configuration is very easy.

It was complex, but well-documented. Getting AppMon set up has a lot of moving parts, but they're all documented and it went relatively smoothly.

We stood up AppMon five years ago. It was not straightforward; it was complex. 

It's straightforward. Very simple. There is a lot of automation.

I was the sole person who set it up. There was complexity to AppMon and getting everything set, but more specifically getting the dashboard setup. It was reasonably complex. Some of the stuff was not super intuitive to me. Maybe I was approaching it from the wrong way, but I definitely had trouble. I especially struggled in the first couple of months trying to get everything set up the way we wanted it. 

With the Dynatrace solution, as this is still in PoC, I'm the first person involved in this. For AppMon, somebody else was doing that earlier, and I took that on on.

Setup with Dynatrace is much more simplistic. We've made a comparison matrix of other products, older products, and this one. That was one of the first items we were comparing. Ease of setup, of course, is great.

We deployed it quite fast. Managing to install AppMon was quite straightforward, but for the DC RUM, building the reports is a bit complex. It needs a lot of training and a partner to actually help out.

It was straightforward while implementing Java and .net, but complex in the case of C++.

Setup is super easy. The SaaS version is, of course, the easiest to deploy. You don't have to do anything except install the agents. And that's quite simple, you just go to a webpage, you download and you click and it automatically connects. And it does everything for you.

If you go for the managed version, then you have to first see about hardware, by doing your homework for hardware requirements and things like that. But even then, it's quite straightforward.

The initial setup was very easy for us. The installation and configuration of the application and the dashboard took around 31 hours. 

Installation of OneAgent is really easy. We have installed this solution in a short time on nearly one hundred hosts.

Deployment was usually straightforward, but at times it could be complicated by whether or not to add additional data base servers and configuration of making sure that everything talked to each other through firewalls, etc.

Initially getting set up and configured was some what complex and took a bit of a learning curve. Once you set everything up, the software runs itself practically, but takes continual monitoring and tweaking to ensure that you are getting the most out of the product.

It was very, very, very easy to set up.

It was straightforward. It was was easy to add up. It was not complex at all, while the other monitoring tools are more complex than Dynatrace. Dynatrace was not that bad.

I was involved with the new setup process. We have Adobe Stack, so we are doing Adobe Stack.

It is pretty straightforward. You just go to the install Dynatrace UI. It gives you the command. You just need to run the command. It is pretty straightforward.

I have been involved in the upgrade process in the finishing of the initial implementation. It was pretty straightforward.

I did not have any issues setting it up. The documentation really helped. If I did run into a question, I received a pretty quick response from our support people. 

I wasn't involved in the initial setup, so I can't speak to whether it was complex or not. I did go through some initial training on OneAgent, and it looks extremely straightforward. I can't imagine it being too complicated.

It was difficult to initially use the solution, how to use it and where to navigate. After that, they said, "We should some course training for people." 

After people were trained, it is easy. The first time, however, was very difficult for us, not knowing how to get started.

We are more of the user community than the architecture or infrastructure, so I have people that are architects, experts, and guardians who have had to deal with this (not me).

At the time of the initial setup, I was a programmer analyst and our team was bringing in several tools. So initially, I assisted a little in the testing and rolling out.

This was probably more than five years ago. It was relatively complex because we were trying to implement into environments that they did not yet support. We wanted to try pushing the boundaries in making it compatible. Therefore, it was not as simple as some of their other setups would be.

Before, with AppMon, it was so complex, but you got used to it. Now, with Dynatrace, it's a breeze.

The initial setup was reasonably straightforward. It was pretty easy to get deployed, and again, getting the value in a reasonable time. 

A colleague of mine did the initial setup. Compared to Admon, it is much easier to get some of the information. The challenge now is that we have a lot information with Dynatrace. The main task will be to sort through all the information and make sense of it. That is the major difference.

Overall, it's very easy to setup on the client side.

It was quite straightforward to implement.

The initial setup is straightforward, it took approximately 12 hours.

We've found the initial setup to be quite straightforward. It's really easy. A company shouldn't have issues with implementing or deploying it.

Basically, we just have to assemble an environment, a QA or the development environment of a specific application. It usually takes two or three hours just to set up everything and keep it running.

We use about five to 10 users for an installation. Usually the IT Manager and the DBA security managers and also developers. We even have some product and marketing managers. They use it to identify users.

I was not involved in the initial setup. I was not there at the time.

During the initial implementation I was just there as a bystander. We had our infrastructure guys taking care of the implementation. I was just there afterwards to learn how to run it. And if there are upgrades, we hand that off to infrastructure.

Very straight forward to setup and get working almost immediately out of the box.

Setup is straightforward, but during implementation you need to work on the agent connectivity.

I was not really involved in the initial setup. I just coordinated the deployment. But it didn't need seem we needed to do too much for the setup of Dynatrace. We had to focus our efforts on group duplications, from a business perspective, but everything else was discovered and automatically set by the Dynatrace application itself. I don't think we had much trouble.

The real complexity that I've seen with Dynatrace is to learn how to navigate through all the options in the troubleshooting process. We have a lot of ways to evaluate the same problem. We had some difficulties in the beginning with the use of the product, but after some time and some experience we have overcome this problem.

Initial setup was pretty straightforward.

It was very user friendly.

The DevOps engineer worked extensively on it. I do the troubleshooting.

I was not involved in the initial setup. I took this over from my boss, and she was involved in the initial setup. I was kind of thrown into it, so I was a little worried about that. But it's been pretty easy.

I'm involved in the switch from AppMon to Dynatrace. To me, that's the biggest upgrade we've got. For AppMon, I did training courses. We did one-on-ones with our guardian from Dynatrace. Even with those, it was still a very complicated tool to learn. With Dynatrace, we picked it up in minutes. It was very intuitive. That's what I can't believe. I almost wish we didn't waste the time doing the training for AppMon. I would have just gone straight to Dynatrace.

Initial setup was very straightforward and easy to setup.

The initial setup is easy and pretty straightforward. It's not overly complex. 

The main issue is that, due to the fact that it covers so much space, the navigation can be long-winded. It can take a lot of clicks to get into where you want to go, however, it's covering a lot of information.

On the site that I'm on, on the Dynatrace site, there's really just me that's doing the technical side of Dynatrace. I'm the one that's keeping Dynatrace itself running and whatnot. That said, even in bigger environments, there's probably only one or two people that are looking after Dynatrace itself. It's really solid in that regard. 

Very straightforward.

Initial setup was quite easy and straightforward. The solution by itself assigns a place for sensors. You just need to properly set ports and IPs.

The initial setup of Dynatrace is quite easy.

The integration and configuration was easy.

Yes, it is simple and straightforward.

The initial setup is pretty straightforward. The agent installs and configures everything automatically. In the older one, you had to manually configure everything. Now, you install the agent and you may have to restart some processes, but then it just starts giving data.